Overview of System Parameters
The following parameters are provided with the X4 BPMS:
| Number of the currently executed process action. Example: | |
| Relative repository path and file name of the Technical Process that called the current Technical Process. This parameter can only be substituted, if the current Technical Process has been invoked directly from another Technical Process as subprocess. Example: | |
| File name (without file extension This parameter can only be substituted, if the current Technical Process has been invoked directly from another Technical Process as subprocess. Example: | |
| Relative repository path of the Technical Process that called the current Technical Process directly as subprocess. Example: | |
| Relative repository path and file name of the current Technical Process. Example: | |
| File name (without file extension Example: | |
| Relative repository path of the current Technical Process. This parameter can only be substituted, if the current Technical Process has been invoked directly from another Technical Process as subprocess. Example: | |
| Name of the current respository project. Example: | |
| Host name of the current X4 Server. Example: | |
| HTTP port that has been defined in the configuration file Example: | |
| Name of the current X4 Server instance that has been defined in the configuration file Example: | |
| IP address of the X4 Server. Example: | |
| Current date and time in the ISO format The date is based on the local time zone, which can be set separately if required. See detailed information further down this page: Setting the time zone for the %NOW% and %NOW_PLAIN% parameters Example: | |
| Current date and time in the format The date is based on the local time zone, which can be set separately if required. See detailed information further down this page: Setting the time zone for the %NOW% and %NOW_PLAIN% parameters Example: | |
| ID of the current Technical Process instance as an integer number that is unique within an X4 Server instance. Subprocesses are executed with the same Technical Process ID, however, not processes that have been started using the Process Starter. Example: If multiple instances of the X4 Server are executed within one application server simultaneously, it is recommended to use the unique parameter | |
| Outputs the unique UUID of the start process. | |
| Relative repository path and file name of the Technical Process that has been started originally. If the current Technical Process has been started as a subprocess of another Technical Process, the path and file name of this main Technical Process will be displayed. Example: | |
| File name (without file extension If the current Technical Process has been started as a subprocess of another Technical Process, the file name of this main Technical Process that has created the current Technical Process context will be displayed. When calling a Technical Process with the Process Starter, a new Technical Process context will be created. Example: | |
| Relative repository path of the Technical Process that has been started originally. If the current Technical Process has been started as a subprocess of another Technical Process, the path of this main Technical Process will be used. Example: | |
| Number of milliseconds since January 1st 1970, 0:00 h. Example: | |
| Name of the X4 Server instance Thus, the process instance can be identified explicitly, if multiple X4 Server instances are executed within one application server simultaneously. Example: | |
| Repository folder path (absolute or relative) of the current user in the This value is taken from the global configuration file Example: | |
| Absolute repository folder path of the current user in the Example: | |
| ID of the current user, whose repository folder contains the Technical Process ("user collection"). Since X4 BPMS version 4.0, the user ID is a string and no longer an integer number. Example: | |
| Absolute path of the current working directory, where the application server has been started. Example: |
Setting the time zone for the %NOW%
and %NOW_PLAIN%
parameters
You can set the timezone for X4 by setting a parameter to the start of X4 / wildfly in the startX4.bat
(Windows) or startX4.sh
(Linux) file.
Examples:
@set JAVA_OPTS=%JAVA_OPTS% -Duser.timezone=Europe/Berlin
or
@set JAVA_OPTS=%JAVA_OPTS% -Duser.timezone=UTC
or
@set JAVA_OPTS=%JAVA_OPTS% -Duser.timezone=US/Eastern
Parameters for Web Services
Within the Webservice Configuration Editor, additional parameters can be enabled to be used exclusively for web services. This allows to enable parameter handling for this ReSTful webservice or SOAP webservice operation, and hand over HTTP request information to the Technical Process context as parameters (as a more efficient alternative to Input Mode HTTP-MetaXml
).
Possible values:
Disabled
: Do not provide parameters within the Technical Process from the HTTP request (Default)Enabled
: Provide parameters within the Technical Process context that contain HTTP request information

If the Enabled
option is selected, the following parameters with HTTP request information are available within the Technical Process context, e.g. within XSL mappings:
REQUEST_PARAMETER_<Name>
: Desired parameter (case-sensitive!)REQUEST_HEADER_<NAME>
: Desired HTTP header (only uppercase!)REQUEST_METHOD
REQUEST_SCHEME
REQUEST_PATH
REQUEST_FULL_PATH
REQUEST_REMOTE_ADDRESS
REQUEST_REMOTE_PORT
REQUEST_REMOTE_USER
REQUEST_LOCAL_ADDRESS
REQUEST_LOCAL_PORT
REQUEST_SERVER_NAME
REQUEST_SERVER_PORT
These parameters can be used like default parameters, but cannot be overwritten and are not visible in the global parameter managemernt.