Winshuttle Update Plug-in

« Back to Plug-ins Table

The Winshuttle Update plug-in allows you to interact with SAP using Transaction or Query scripts (like, a web-service) which are imported into the Form solution. It allows you to dynamically perform SAP data operations within the workflow. It also supports repeating web services.

The user returned by the runnernode parameter is used:

To get the credentials to log in to SAP, unless the webservice is configured with the System Account.
To validate the appropriate license, even if the webservice is configured with the System Account.

Note:

In SAML/OAuth Authentication for SAP Trust and SAML EIS configuration:

If the System Account option is used to execute a webservice and the user has never logged into Evovle, webservice will fail to execute with an error.

Properties


Name	Description	Mandatory	Group Name	Modes
webservicename	The name of the Web Service to run.	Yes	Web Service	NA
runnernode	The runner node can be configured in one of two ways: Select a specific node: In the Properties pane, next to RunnerNode, click the Options button. On the Edit Runnernode screen, click Node to select a specific activity or approval node in the workflow. The person assigned to the selected node will be used as the runner. If there are multiple users in the selected node (such as multiple approvers, for example), the most recent user to have completed the activity (the most recent approver, for example) isused. Blank : If the Runnernode setting is left blank, the plug-in will use the user from the nearest activity (such as an Approval node) in the swimlane where the Update plug-in is located. If this would result in multiple users, the most recent user from the list of users is used.	No	Web Service	NA

On the Processes page, under Process History, the Update plug-in status options are as follows:


Status	Description
Scheduled	The job has been created in the background and is ready to be picked up. Runner <Runner Name>
InProgress	The system picked up the job and execution has started.
Enqueued	The job is queued for posting.
Preprocessing	The job has been picked by the worker for processing. Worker: <name of worker>
Posting	The processing has started.
Post-Processing	The document is being updated after having been posted.
Finished	The job execution has completed.

Example

The Update plug-in is useful if your Master Data team prefers to interact with SAP in the background (not manually) after an approval is completed.

Tips and best practices

If there are multiple Update plug-ins, set the plug-in node property “Continue Without Waiting” to False. If “Continue without waiting” is set to True, the plug-ins could run together and impact the result. If the “Continue without waiting” property is set to False, the second plug-in process will start only after the first one has completed.

Note:

When the Winshuttle Update plug-in is configured to run using the Swimlane or RunnerNode and it resolves to an external user, then license will be checked for an external user. This blocks the webservice execution. As a workaround, configure the plug-in to resolve to an internal user.