Prerequisites
...
In the CT_REQ_MDLR_AUTHFLOW table, change the type of authentication from noauth to foureye or sixeye and make changes to the AUTH_FLOW column accordingly. A sample entry is provided as follows:
...
TABLE COLUMN
...
VALUES
...
FLOW_CTRL_ID
...
004
...
PRODUCT
...
CTSTUDIO
...
SUB_PRODUCT
...
REPORTS
...
CHANNEL_ID
...
3
...
APPLICATION_ID
...
CTSTUDIO
...
DEFAULT_IND
...
Y
...
EVAL_CONDITION
...
{
condition : [
{
id : equals ,
field : $context.authflow
value : true
}
]
}
...
EVAL_ORDER
...
1
...
STOP_PROCESS_IND
...
FALSE
...
RESPECT_HIER_IND
...
FALSE
...
TYPE
...
foureye
...
AUTH_FLOW
{
authflow : [
{
tier : [
{
type : INTEGER,
min : 10,
max : 100,
workflow : {
type : foureye ,
flow : {
completed : false
}
}
},
{
type : INTEGER,
min : 100,
max : 1000,
workflow : {
type : sixeye ,
flow : {
completed : false
}
}
},
{
type : INTEGER,
min : 1000,
max : 10000,
workflow : {
type : tree ,
flow : {
condition : OR ,
completed : false,
flow : [
{
role : A ,
count : 1,
completed : false
},
{
role : B ,
count : 2,
completed : false
},
{
role : D ,
count : 1,
completed : false
},
]
},
{
completed : false,
flow : [
{
role : A ,
count : 1,
completed : false
},
{
role : C ,
count : 1,
completed : false
},
{
role : D,
count : 1,
completed : false
}
]
},
{
completed : false,
flow : [
{
role : X ,
count : 1,
completed : false
},
{
role : Y ,
count : 1,
completed : false
}
]
},
{
role : E ,
count : 1,
completed : false
}
]
}
}
}
]
}
]
}
In the same CT_REQ_MDLR_AUTHFLOW table, provide an entry to enable the report approval workflow for viewing the reports, which must be approved by the Studio Administrator. A sample entry is provided as follows:
...
TABLE COLUMN
...
VALUES
...
FLOW_CTRL_ID
...
005
...
PRODUCT
...
VISUALIZATION
...
SUB_PRODUCT
...
REPORTS
...
CHANNEL_ID
...
3
...
APPLICATION_ID
...
CTSTUDIO
...
DEFAULT_IND
...
Y
...
EVAL_CONDITION
...
{
condition : [
{
id : equals ,
field : $context.authflow
value : true
}
]
}
...
EVAL_ORDER
...
1
...
STOP_PROCESS_IND
...
FALSE
...
RESPECT_HIER_IND
...
FALSE
...
TYPE
...
foureye
...
AUTH_FLOW
{
authflow : [
{
tier : [
{
type : INTEGER,
min : 10,
max : 100,
workflow : {
type : foureye ,
flow : {
completed : false
}
}
},
{
type : INTEGER,
min : 100,
max : 1000,
workflow : {
type : sixeye ,
flow : {
completed : false
}
}
},
{
type : INTEGER,
min : 1000,
max : 10000,
workflow : {
type : tree ,
flow : {
condition : OR ,
completed : false,
flow : [
{
role : A ,
count : 1,
completed : false
},
{
role : B ,
count : 2,
completed : false
},
{
role : D ,
count : 1,
completed : false
},
]
},
{
completed : false,
flow : [
{
role : A ,
count : 1,
completed : false
},
{
role : C ,
count : 1,
completed : false
},
{
role : D,
count : 1,
completed : false
}
]
},
{
completed : false,
flow : [
{
role : X ,
count : 1,
completed : false
},
{
role : Y ,
count : 1,
completed : false
}
]
},
{
role : E ,
count : 1,
completed : false
}
]
}
}
}
]
}
]
}
In the OD_USER_FUNCTION_MB table, update the administrators' details to enable report approval. A sample entry is provided as follows:
...
TABLE COLUMN
...
VALUES
...
OD_USER_NO
...
201407010004
...
OD_FUNCTION_CODE
...
To roll back the report approval workflow, the values of the EVAL_CONDITION, TYPE and AUTH_FLOW columns must be modified in order to nullify the report approval workflow process. Therefore, it is necessary to specify the appropriate entries for the respective columns In the CT_REQ_MDLR_AUTHFLOW table in the Studio schema, as shown in the following table:
...
TABLE COLUMN
...
VALUES
...
FLOW_CTRL_ID
...
004
...
PRODUCT
...
CTSTUDIO
...
SUB_PRODUCT
...
REPORTS
...
CHANNEL_ID
...
3
...
APPLICATION_ID
...
CTSTUDIO
...
DEFAULT_IND
...
Y
...
EVAL_CONDITION
...
{"condition" : true}
...
EVAL_ORDER
...
1
...
STOP_PROCESS_IND
...
FALSE
...
RESPECT_HIER_IND
...
FALSE
...
TYPE
...
noauth
...
AUTH_FLOW
...
{"authflow":[{"tier":[{"type":"number","min":10,"max":100,"workflow":{"type":"none","flow":{"completed":true}}}]}]}
...
This section contains information related to basic administration of CT Sigma, such as enabling role-based access and report maker-checker flow.
Refer the following pages:
| Page Tree | ||
|---|---|---|
|