You can use JobRouter system variables in various places in your process, such as in forms or rules. They contain information such as date and time as well as information about the current instance, the initiator, or the instance number. The following shows a list of all JobRouter system variables.
URL |
Description |
|---|---|
[jr_jobrouter_url] |
JobRouter URL |
Date and time variables |
Description |
|---|---|
[jr_date] |
Current date |
[jr_date+x] |
Date x days in the future |
[jr_date-x] |
Date x days in the past |
[jr_int_date] |
Internal timestamp |
[jr_int_date+x] |
Internal timestamp in x days |
[jr_int_date-x] |
Internal timestamp x days ago |
[jr_time] |
Current time |
User variables |
Description |
|---|---|
[jr_department] |
Department |
[jr_E-mail] |
|
[jr_fax] |
Fax number |
[jr_fullname] |
First and last name |
[jr_language] |
User language |
[jr_lastname] |
Last name |
[jr_phone] |
Phone number |
[jr_prename] |
first name |
[jr_supervisor] |
Supervisor / Job Function |
[jr_username] |
Username |
User-defined variables |
Description |
|---|---|
[jr_user_defined1] |
Contains the content of the first user defined field of the user data. |
[jr_user_defined2] |
Contains the content of the second user defined field of the user data. |
[jr_user_defined3] |
Contains the content of the third user defined field of the user data. |
[jr_user_defined4] |
Contains the content of the fourth user defined field of the user data. |
[jr_user_defined5] |
Contains the content of the fifth user defined field of the user data. |
Variables in rules |
Description |
|---|---|
[jr_boxaction] |
Executed action in a process inbox |
[jr_send_action] |
Send mode: 1: Send 2: Terminate |
[jr_workflowid] |
Unique step ID |
Variables in SQL list elements in subtables |
Description |
|---|---|
[jr_row] |
Number of the subtable row (starts at 0) |
[jr_row_id] |
ID of the subtable row that is saved in the database table |
Process variables |
Description |
|---|---|
[jr_assigned_jobfunction] |
Job Function to which the step was originally assigned |
[jr_assigned_username] |
User to whom the step was originally assigned |
[jr_escalation] |
Escalation date of the step |
[jr_escalation_date] |
Formatted escalation date of the step |
[jr_guid] |
GUID |
[jr_incident] |
Instance number |
[jr_incident_escalation] |
Escalation date of the incident |
[jr_indate] |
Receipt date |
[jr_initiator] |
Username of initiator |
[jr_lastuser] |
Last user |
[jr_priority] |
Priority of the step |
[jr_processid] |
Process ID |
[jr_processname] |
Process name |
[jr_startdate] |
Start date of the instance |
[jr_step] |
Current step |
[jr_step_id] |
ID of the current step |
[jr_step_username] |
This variable can contain three different values: •A step is assigned to a user and edited by the user. In the subsequent step the variable contains the user assigned to the step. •A step is saved and reserved by a user. In the subsequent step the variable contains the user who has reserved the previous step. •A request is sent for a step and answered. This variable contains the user who responded to the request.
In the first two cases, this value is only available using a value assignment rule. |
[jr_summary] |
Subject of the step |
[jr_version] |
Process version |
Variables in e-mail templates and escalations |
Description |
|---|---|
[jr_link] |
Link to Step Form |
[jr_link_details] |
Link to Instance History |
[jr_link_login] |
Link to Login |
[jr_username] |
Username |
[jr_info] |
Step Information |
Variables only in e-mail templates |
Description |
|---|---|
[jr_recipient_summarized_steps] |
Open steps information for recipient |
[jr_last_notification_date] |
Last summarized notification date |
[jr_date_time] |
Date with Time |
[jr_lastuser_fullname] |
Full name of last user |
[jr_recipient_fullname] |
Full name of the recipient of a step |
[jr_summary] |
Summary |
Other variables |
Description |
|---|---|
[jr_jobfunction] |
Job function |
[jr_description] |
Description |
