Functions are stored in the script library (DialogScript table).
Example of a function in the script library
Public Function BuildInternalName(ByVal Firstname As String,ByVal Lastname As String) As String
BuildInternalName = Lastname & Firstname
End Function
Using the function in a template on person.internalname
Value = BuildInternalName($Firstname$, $Lastname$)
Pre-script code is code that is run before other scripts are run. You can define process specific variables. Process specific variables are local data spaces when a process is generated. They are used for determining values on a one-off basis within a pre-script, which can then be made further use of within the processes and their processes steps, for example, in generating conditions or server selection scripts, or in the parameters.
NOTE: It is recommended only to set process specific variables in the pre-script and to have read access to them during further usage.
Syntax in the pre-script of a process
values("Name") = "value"
Usage in the process and process step code sections
Value = values("Name")
Related topics
The session object is the instance that makes data available to a user session. This includes the current user, their permissions groups and program functions. Furthermore, the session object makes various services available for accessing data. The services provided by the session object are made available through a generic interface (Resolve (Of Service)()). In the following sections, examples are provided of frequently used service.
NOTE: You can find a complete description of all parameters in the VI.DB.DLL documentation.
Detailed information about this topic
The full path for the configuration parameter always has to entered when configuration parameter are queried.
Syntax
Session.Config().GetConfigParm("<full path>")
When a configuration parameter is tested in a generating condition in VB.Net syntax, the function returns a string. In order to compare this value to a numerical value, the configuration parameter has to be set and contain a numerical value. This depends on the implicit value type conversion from VB.Net. If the configuration parameter is not enabled, the function returns an empty string ("") that cannot be compared to a numerical value. This results in a VB.Net runtime error. Configuration parameter values are therefore always compared to strings.
Do not use:
Session.Config().GetConfigParm("QER\Person\User\DeleteOptions\Homedir")=1
Use instead:
Session.Config().GetConfigParm("QER\Person\User\DeleteOptions\Homedir")="1"
In order to ensure that a logical value is always returned, the VID_IsTrue function should be used.
Example
If VID_IsTrue(Session.Config().GetConfigParm("QER\Person\User\DeleteOptions\Homedir")) Then ...
Related topics