Set PS Variable

Description:

Set PS Variable step sets PS Variables with global or local scope as specified with value assigned from a field. These variables are available in the same workflow.

Note: The PS variables set in this cannot be used for database connection details.

Configurations:

No.	Field Name	Description
1	Step Name	Name of the step. This name has to be unique in a single workflow.
2	Execute even if no row is found	A checkbox to define if the step is to be executed in case no rows are received. By default it is unchecked.
3	Fail if field not found	A checkbox to define if the step is to be failed in case no field is specified. By default it is unchecked.
	Field values (Tabular):
1	Field name	Specify the field value which is to be assigned to a variable.
2	Variable name	Specify the variable name which will be used further.
3	Variable scope type	Specify the scope of the variable (Global or Local). Note: Global variables are available throughout the lifecycle of the parent workflow/process. They can be created at any sub-level and it will be available after that to the entire scope. They will be destroyed after the main or parent workflow/process ends. Local variables are available only in the workflow/process where it has been created.They are not available to the child workflow/process. The same variable name can be used for global and local scopes simultaneously. The value modified or fetched is completely based on the scope specified as mentioned in the note below. The PS variables are added to the existing list which pops up on Ctrl-Space where applicable. The format of these variables in the list will be as ${GLOBAL.varname} and ${LOCAL.varname}. The PS variables created in ‘User Defined Java Class’ or ‘Modified Java Script’, are not visible in this list. However, If the child workflow/process is already opened and a variable is added in the parent workflow/process. This variable is not reflected directly at design time (i.e. on Ctrl-Space) although there no issues during runtime. There are two options for this, - The user can type the variable name where required - Reopen the child workflow/process (from Open referenced object) after the variable is added.