Components of Winshuttle Workflow Solutions

Winshuttle Solutions

There are two primary types of solutions:

• Workflow Solution for Documents — A document solution has only a deployment profile component. With the Solution for Documents, you can design a workflow and publish it to any deployment profile.
• Workflow Solution for Forms — A form solution can contain every component possible. With the Solution for Forms, scripts are used automatically and you don't need to publish web services through client products of QUERY or TRANSACTION. A solution file has the extension .wssln.

Solution components

A solution can contain some or all of these components:

• InfoPath Form Views
• TRANSACTION Scripts
• QUERY Scripts
• Deployment Profiles
• JavaScript

Solution components are available in the Solution Tree, which appears in Designer when you create a new solution or open an existing one. Click to expand each section.

SAP Logon Types

There are three types of SAP logon types that can be used. Briefly, these are as follows:

SAP (Logon): This type of logon is performed on SAP Application or Group server using the user's credentials. These credentials can be entered at run time by the user or they can be picked from SAP credentials defined on Winshuttle Central.

IntegratedLogon_SSO: This type of logon uses the Windows ID to logon to the SAP Application or Group server. The user enters windows credentials into the form while submitting its data for SAP run. After the user enters their windows credentials they are 'impersonated' and the call for submitting data to SAP runs under this impersonation block. This means that the corresponding SAP User of the windows user is used for posting data into SAP.

IntegratedSSO_Certificate: The SAP logon is used to logon to the SAP Application or Group server. The user's Windows user name is considered the SAP user name on the form while submitting its data for SAP run. The SAP logon is handled internally by the Winshuttle Server Engine. SAP User’s SNC (Secure Network Communication) name is validated against the SNC name of the user certificate for the SAP Server present in SECUDIR. The SAP Application server’s SNC name is validated against the SNC name of the server certificate present in SECUDIR.

Saving solution changes

Changes to an InfoPath form in a solution must be saved in the solution. You cannot edit and save changes to the solution file outside of the solution.

InfoPath form views

In the Solution Tree, right-click Views, and then click New View or Edit View to display the View Editor window. Set this as the default view or select from one of the template views.

Note: It is important to create and edit views only in Designer. If you create or edit a view in InfoPath, it is not saved to your solution.

• Click the layout, and then right-click Edit.

  The InfoPath form that corresponds to the view appears. Perform the edit that you want.

TRANSACTION and QUERY scripts

You can import one or more each of TRANSACTION and QUERY scripts. You can also delete scripts from a solution. To edit a script, you must save the file to a specific location, and then reimport the script. Note that if you edit a script in a workflow or delete a script from workflow, the original script is not changed or deleted from the original repository. When you work with a script in a solution, you are essentially working offline, and Designer does not connect to web services until you publish the solution. A script or scripts are not necessary to create a solution.

• For scripts, the properties available for that script appear. For TRANSACTION, you can change whether you allow the script to be overwritten or not.
• For QUERY scripts, properties include: EnableCache, IsOverwriteAllowed, System Usage Level associated with the script, Timeout, and the WebService Description and WebServiceName. For more information on these properties, see the CENTRAL Advanced Guide.

If a solution that includes a script is destined for production, and your deployment requires approval, the solution must be submitted for approval before it can be published.

1. In the Solution Tree view, right-click Transaction Script or Query Script.
2. Click Import.
3. In the Open File dialog box, select your script. Click OK.

   If the script has the same name as an existing script, you are prompted to update the mapping or to overwrite the existing script.

4. In the Solution Tree view, right-click Transaction Script or Query Script.
5. Click Save As to save the script locally.

   If you do not save to a specific location, the script is saved to a Windows Temp folder.

6. Update the script as you want and save it. Close the client program.
7. In the Solution Tree view, right-click Transaction Script or Query Script.
8. Click Import to reimport the script.
9. Right-click the script.
10. Click Delete.
11. In the Solution Tree view, right-click Transaction Script or Query Script.
12. Click Export.
13. Specify the destination.

Mapping form fields

In Designer in a solution, form fields are mapped in the Manage Field Mappings dialog. Input and output fields are separated under an Input value and an Output value pane.

Deployment profiles

With development profiles, you can use one solution in different environments without remapping. Three templates are provided--Development, Staging, and Production--or you can create extra custom profiles.

JavaScript

JavaScripts can be embedded directly into the solution. When embedded, scripts have less chance of being lost or deleted.

Start and End tags and solutions

In Solutions, you can continue to use older scripts, but be aware that the Solution JavaScript editor removes any content before ==ShareVisBeginScript== and after ==ShareVisEndScript==.

Approvals

If you want to publish your solution on an SAP production server, the solution must be submitted to an approval process, just as a script would. If you do not want to use the solution on a production server, or if the solution does not contain a production script, you can publish the solution without first submitting it to CENTRAL.

• Right-click JavaScript, click Edit in Solution.

Solutions and web services

It is not possible to use existing web services that are published through Winshuttle SERVER in Winshuttle Solutions.