Description:

We have developed a solution that utilizes the Winshuttle Update Plugin to automatically execute web services once the form is approved by the manager.

Both the mapping and Solution Variants are configured to run the web services using an Admin Account, rather than the account of the logged-in user.

When the web services are executed through a button, they correctly run with the specified admin account. However, when the web services are triggered using the Plugins, they utilize the details of the user to whom the swimlane was assigned, rather than the admin account. This behavior is incorrect.

Please provide guidance on how we can configure the plugin to utilize the correct admin account details when running the web services.

Works with 20x

Solution:

In 12.1 we used to have key WinshuttleUpdateLegacyOperation key; we added this key keeping in mind that existing customers behaviour for Winshuttle update plugin should not get changed
In case this key value was yet to true then update plugin jobs for the solutions executes in the context of workflow admin user(SAP creds of Workflow admin user is checked).

But in Evolve this key has been removed and you would need to specify the Runner node in the Winshuttle Update plugin Parameter in order to use the Service account.

 Evolve onwards it will work as per the runner node of Winshuttle update plugin or in case if it is blank then it will run with Swim lane user.

If in the Solution Runner node is empty it will use the swimlane user;  you would need to specify the node and then it will pick the Admin account .

Please see attached sample solution for the same created in version 20.1