Enabling Job Approvals

Enabling Job Approvals

Knowing different User Roles

Below is the table that defines users levels and their group names.
0disabledcannot login
1browsercannot submit jobs
4modeleraka designer
6systemsame as manager

Default privileges for each of the users can be seen in the bottom of the article User Roles and Groups

File to modify

To enable approvals, we will be modifying tools setup file. 
This can be access under (1) Admin -> Setup -> Configuration files -> (2) YCE tools setup: edit

The 'tool_setup' has a section per job-type and also the default, which is applicable for all job-types.
The 'levels' attribute of the 'approvals' record is a list of user/client-levels that can 'approve' a scheduled job. 
When the 'level' value has the numbers '3', '4', '5' and '6' (producing “3456”), the checkbox is available for 'engineer' through 'system' level privileges.
'limit' controls the total number of jobs in the scheduler of the job-type that are in a 'scheduled' or 'pending' state.
'threshold' defines how many of these jobs may be submitted to the scheduler before new jobs are set 'pending' requiring an approval.

State Machine:

Below diagram gives an understanding of job states at various stages of job.

Example: Setting up Job approvals for the operator user by the Engineer user

Consider a user named oper of the group operator(user-level 2)

(1) Admin ->  Setup -> Configuration files 
(2) For the job_type="default" (which would mean for all type of jobs.. listed in the same configuration file scrolling above)
for approvals name = "1" (browser) and "2" (operator), update the values of levels to "3456" which would mean all the users of engineers and higher levels can approve the job.

Hereafter, the oper user's job goes to pending state.  Once approved moves to scheduled state as below.

Users of Engr or above levels, see the "Approval" option under Operate -> Job status -> Scheduled Jobs as below:

    • Related Articles

    • Enable debug and creating support file

      Debug mode is enabled when we need more logs to analyze any issue. In this article we shall enable debug for a Job. Debugging via GUI Enabling Debug (1) Admin -> System -> Debug Logs -> (2) Start debug -> (3) OK         Create a Job Create ...
    • Change id not being accepted

      The Change-id is by default configured to accept only specific formats. A configuration file exists to modify the format, its character or add additional patterns. These options are described in this Wiki article: ...
    • Hardware sizing requirements

      NetYCE is very light software and needs very moderate hardware requirements. Sizing mainly depends on either the number of nodes or number of jobs executed per day. Sizing for complete setup: This is for High availability setup, 2 (DB) servers. Nodes ...