Description

We built a solution that uses the Winshuttle Update Plug in to Run the web services automatically after the Manager Approved the form.

The web services are configured in both the mapping and in the Solution Variants to run using a Admin Account and not the logged in user account.

When we run the web services from a button, it runs the web services with the admin account as specified. When the web services are run using the Plugins, it uses the user's details to whom the swimlane was assigned and NOT the admin account. This is not correct.

Please advise what we must do to get the plug in to use the correct admin account details when running the web service.

Applies To

20x

Solution/Immediate Workaround

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