Context variables

Context variables can be used in the sourceParams element in the SQL expression to get the lookup value selected by the user. For example, to filter the results in the Department lookup, you can use the CONTEXT_team_NAME context variable to get the team name selected by the user in the Team lookup.

Note: Context variables should not be used directly in the source SQL as that would create a SQL injection vulnerability. The sourceParams element is encoded and therefore protected from SQL injection.

This table lists the context variables that are available for substitution for work details and premiums:

Context variable Example
CONTEXT_department_ID 1
CONTEXT_department_NAME DEPT A
CONTEXT_docket_ID 1201
CONTEXT_docket_NAME AUTODOCKET
CONTEXT_endHundredTime 0001
CONTEXT_flag1..10 true
CONTEXT_hourtype_ID 5013
CONTEXT_hourtype_NAME EL_SICK_PEN
CONTEXT_isWorkDetail true
CONTEXT_job_ID 3
CONTEXT_job_NAME COMPUTER TECHNICIAN
CONTEXT_minutes 1
CONTEXT_project_ID 1203
CONTEXT_project_NAME AUTOPROJECT_REPORT
CONTEXT_rate 53
CONTEXT_startHundredTime 0000
CONTEXT_team_ID 54
CONTEXT_team_NAME MOB_DEPT_A
CONTEXT_timecode_ID 5216
CONTEXT_timecode_NAME AA AAR CODE1 DENIED
CONTEXT_udf1..10 123 Main Street
CONTEXT_workSummaryId 3016568

This table lists the context variables that are available for substitution for elapsed times:

Context variable Example
CONTEXT_department_ID 1
CONTEXT_department_NAME DEPT A
CONTEXT_docket_ID 1201
CONTEXT_docket_NAME AUTODOCKET
CONTEXT_flag1..10 true
CONTEXT_hourType_ID 5012
CONTEXT_hourType_NAME EL_SICK_APP
CONTEXT_job_ID 11
CONTEXT_job_NAME SUPERVISOR
CONTEXT_minutes 1
CONTEXT_ovrDate 20181221 144754
CONTEXT_project_ID 1201
CONTEXT_project_NAME AUTOPROJECT
CONTEXT_team_ID 54
CONTEXT_team_NAME MOB_DEPT_A
CONTEXT_timecode_ID 5216
CONTEXT_timecode_NAME AA AAR CODE1 DENIED
CONTEXT_udf1..10 123 Main Street