Designer Custom Controls Reference Guide

Winshuttle Designer custom controls enable workflows and forms be tightly integrated and share information. For example, the Ws.CurrentUser custom control takes information about the user who is starting a form, and puts it into the form.

Note: Beginning with version 10.6 of Winshuttle products, control names were renamed to 'WS.<controlname> from 'ShareVis.<controlname>. For example, ShareVis.Assignment (10.5 name) is called WS.Assignment in version 10.6.

On this page

• How to change control parameters
• Special note about InfoPath controls
• Control variant list

Click a control in the menu (at right) to view usage, parameters, and other information about Designer controls.

How to change control parameters

Back to top

To change controls, you must change settings and parameters for them in the Ws.config file. The Ws.config file can be opened in any text editor, such as Windows Notepad.

It's recommended that you make a back up copy of your Ws.config file and store it in a safe location prior to making any changes.

1. Open the Ws.config file in a text editor; by default, the Ws.config file is located at:
   <servername>\InetPub\wwwroot\ws.config
2. Find the control you need to change and make the necessary changes.
3. Save the Ws.config file.
4. Open a command prompt on the server, and then run an iisreset. (If you are unable do this yourself, contact your system administrator).

Special note about InfoPath controls

Back to top

Certain circumstances can create a condition where an InfoPath rule and its associated control action will not be triggered.

If all of the following conditions are true, neither the infopath rule nor the action of the control will be triggered:

• The control is configured to run at Start or End.
• It changes a field.
• If any rule is set to run on the field change, or any another custom control is configured to run on the field change.

Control Variant List

Back to top

Deployment variants enable you to specify values for parameters that depend upon the deployment profile. Variants can have different values for different profiles.

Example: A solution using the Add Attachment plug-in could have a different value for the file parameter depending upon which profile is used. A Development profile could use a value of D:\ (for the drive location), whereas the Publishing profile could use a value of C: drive.

The following table lists available variants associated with certain controls

Control	Variant(s)
WS.Lookup	DataSourceName | ImageUrl
WS.Query	ConnectionString | PortalRoot
WS.SharePointUsers	Site | GroupName