Global Variables DSC

Please check out the following article for scenario where Global Variables DSC will be use: 

[Migrating a LiveCycle Process from "Dev" to "Production" - Without Pain|Migrating a LiveCycle Process from "Dev" to "Production" - Without Pain]





h3. Component: com.avoka.livecycle.globalVariables 1.0



h2. GlobalVariables Service

Global Variables: For years programmers have used text files, hidden away, to contain deployment properties for applications. Deployment properties allow programmers to declare and set variable values, tailoring the solution to its host environment. They get set once and are then kept out of harms way. The *Global Variables* service allows business processes to do this, in a powerful graphical modelling environment -- and more. With this service we can also change the values of globals variables - if we want to -- making it more powerful/flexible.




h3. Operation Title: Get Global Variables   (getValues)
Get Global Variables: Get values of global variables and copy their value/s to process variables.
|| Input Parameter || Type || Description || Editor ||
| Global Variabes | Table | This is the user interface used to display what global variables are in the system. It can display their values and also allows users to update their values. Each global variable is a row of the illustrated table. The first column (Name) is the unique name for the global variable. The column (Type) shows its datatype, and the column (Value) shows its current value. To change the value of a variable just edit the appropriate table cell -- as shown -- and click the 'Update Values' button.| [GlobalVars|#globalGet1.jpg] |
| New Global Var | Fields | This is the user interface where users can create global variables. The first field (Name) is the unique name for the global variable. The next fields (Title) is optional, and holds free text describing the global variable. The field (Type) holds its data type. The field Length is only relevant for string based types; such as String and NString), and identifies how much database storage is to be allocated to the variable. The field (Scale) is only used for decimal types. The field (Description) is optional and used for long text descriptions of a variable.| [Create Var|#globalGetNewVar.jpg] |
| Get Settings | Table | This is the user interface where we can query the global variables and update our process variables with their values. The first column (Sequence) only affects the visual ordering of the table rows, we can change the sequence of a row by selecting it, and presssing the up/down buttons. The column (Local Variable) has an xpath expression editor that allows us to choose the process variable to be updated. The column (Global Variable) is a drop-down box that allows us to choose the global variable to 'GET' the value of.| [Map Vars|#globalGet2.jpg] |




|| Output Parameter || Type || Description ||





h3. Operation Title: Set Global Variables   (setValues)
Set Global Variables: Set values of global variables by reading process variable value/s and writing their values to global variables.
|| Input Parameter || Type || Description || Editor ||
| Global Variabes | Table | This is the user interface used to display what global variables are in the system. It can display their values and also allows users to update their values. Each global variable is a row of the illustrated table. The first column (Name) is the unique name for the global variable. The column (Type) shows its datatype, and the column (Value) shows its current value. To change the value of a variable just edit the appropriate table cell -- as shown -- and click the 'Update Values' button.| [GlobalVars|#globalSet2.jpg] |
| New Global Var | Fields | This is the user interface where users can create global variables. The first field (Name) is the unique name for the global variable. The next fields (Title) is optional, and holds free text describing the global variable. The field (Type) holds its data type. The field Length is only relevant for string based types; such as String and NString), and identifies how much database storage is to be allocated to the variable. The field (Scale) is only used for decimal types. The field (Description) is optional and used for long text descriptions of a variable.| [Create Var|#globalGetNewVar.jpg] |
| Get Settings | Table | This is the user interface where we can map process variables to global variables for the purpose of dynamically updating the global variable values. The first column (Sequence) only affects the visual ordering of the table rows, we can change the sequence of a row by selecting it, and presssing the up/down buttons. The column (Local Variable) has an xpath expression editor that allows us to choose the process variable to be queried. The column (Global Variable) is a drop-down box that allows us to choose the global variable to 'SET' the value of.| [Map Vars|#globalSet1.jpg] |




|| Output Parameter || Type || Description ||






h5.
{panel:borderStyle=solid}
For how to configure license information for this component service - Global Variables, please click on the following link:
[Avoka LiveCycle ES Component License Configuration]

Please send us any questions or comments on this documentation regarding Global Variables by clicking on the following link:
[Feedback|mailto:docfeedback@avoka.com?subject=DSC Documentation Feedback on Service: Global Variables]
{panel}


h3. Licence Configuration:

|| Parameter || Type || Description ||
| License Key | java.lang.String | The license key provided to you when you purchased a production license for this Solution Component. If blank this Solution Component will assume evaluation mode and allow 100 invocations or 6 hours up-time. |
| License Organisation | java.lang.String | The organization name you provided to Avoka for which you are licensing this Solution Component. |




{anchor:globalGet1.jpg}