That's an unfortunate naming convention, because rule to run an "embedded plugin" would be custom code or something like a powershell script that you execute. Please see the documentation here:
That's not the same as a workflow plugin, i.e. you can't choose to run a workflow plugin from a form button. The workflow plugin runs in the background, and again, you can use transition conditions to execute it or skip it, depending on whatever factors you have that would want you to add a user (or whatever plugin you choose to run).
Hope that helps clear things up a little.
Original Message:
Sent: 09-16-2024 08:59
From: Alexander Hutchinson
Subject: Syntax for Executing Embedded Plugin in Form
Sigrid,
Is the "Run Embedded Plugin" button behavior deprecated, then?
------------------------------
Alexander Hutchinson
Senior Analyst
Raytheon Co
CHESAPEAKE MA
Original Message:
Sent: 09-13-2024 13:06
From: Sigrid Kok
Subject: Syntax for Executing Embedded Plugin in Form
Hi Alexander
Plugins, by their nature, run in the background. So you'd have to specify it to run in the workflow and then check it afterwards.
I believe others want to be able to maintain users from a form, as it's come up in the past. You can go to the ideas portal and post your request here: https://ideas.precisely.com/?project=AUTM
Best Regards,
Sigrid
------------------------------
Sigrid Kok
Precisely Software Inc.
Original Message:
Sent: 09-13-2024 12:43
From: Alexander Hutchinson
Subject: Syntax for Executing Embedded Plugin in Form
Sigrid,
Yes, that plugin is what I'm after. How can I run the plugin from within the form, though? Like on a button or as a rule that triggers when a field changes? And not via a node in the workflow?
Furthermore, what is the syntax for adding the user to multiple app groups?
------------------------------
Alexander Hutchinson
Senior Analyst
Raytheon Co
CHESAPEAKE MA
Original Message:
Sent: 09-12-2024 18:00
From: Sigrid Kok
Subject: Syntax for Executing Embedded Plugin in Form
Hi Alexander
Are you talking about the Manage User plugin in the workflow? If so, here is an example
the above is an example for a non-employee, and includes a porta. You'll probably want to Enable System IDP and remove the portal, and of course use you own fields, app name and group name.
As for only running if it changes, you would want to flip some flag in your solution and use a Transition condition - like flagUpdate == 'true' -- or something like that.
If you request is for something else, please provide specifics.
Best Regards,
Sigrid
------------------------------
Sigrid Kok
Precisely Software Inc.
Original Message:
Sent: 09-11-2024 15:13
From: Alexander Hutchinson
Subject: Syntax for Executing Embedded Plugin in Form
I want to add a new user to my instance of Evolve using an Embedded plug-in on a form.
The form has fields for the User Name, Display Name, and Email:
These fields are set from a SQL database lookup when a person is selected from the "Person Lookup" pictured above.
Upon clicking the button, I want to execute the "Manage User" plugin with following arguments:
User Name = Person Username
Display Name = Person Name
Email = Person Email
App = Finance (that's the name of my app)
App Group = Originator AND Data reviewer
And have Enable System IDP to yes.
I cannot, however, find the correct syntax/documentation on executing this plugin from a button.
Is this the correct syntax below?
PluginName=Manage User,User Name=[/my:myFields/my:Person_Username],Display Name=[/my:myFields/my:Person_Name],Email=[/my:myFields/my:Email],App=Finance,Add App Group=Originator;Data Reviewer,Enable System IDP=Yes
Additionally, would it be possible to run this plugin when a certain field is changed, as opposed to on a button?
------------------------------
Alexander Hutchinson
Senior Analyst
Raytheon Co
CHESAPEAKE MA
------------------------------