...
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:
GCIF
CTSTUD2014ENTL
FLOW_CTRL_ID
004
PRODUCT
CTSTUDIO
SUB_PRODUCT
PUBLISHER
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 request approval. A sample entry is provided as follows:
OD_GCIF
OD_USER_NO
APP_ID
OD_FUN_CODE
OD_PROD_CODE
OD_SUB_PROD_CODE
OD_ACC_NO
OD_TRAN_MAX_AMT
OD_ACC_GRP
OD_FLG
CRT
USER_ROLE
CTSTUD2014ENTL
201407010004
CTSTUDIO
APPROVE
CTSTUDIO
PUBLISHER
READONLY
0
(NULL)
(NULL)
READONLY
ALL
For the full set of information on Request Approval workflow, refer the following pages:
- Approving Components
- Initiating Requests
- Approving Requests
- Rejecting Requests
- Re-submission of Rejected Requests
The Request Approval in Canvas Studio paves the way for an effective mechanism in managing configuration data or metadata. When any Canvas component (e.g. forms, templates, shortcuts, shortcut containers etc.) is created by a Canvas Studio user, the configuration data or metadata of those components gets stored in the Canvas schema. Canvas administrators or users, who possess the privilege of Canvas administrator, can then approve or reject those Canvas components. The approval workflow is even applicable for editing and deleting the components. The following steps provide precise information on the request approval workflow in Canvas Studio.
Request Approval Workflow
Note: The Request Approval workflow is applicable only for Forms, Form Containers, Events, Template, Shortcuts, Shortcut Containers, Entitlements and Reports.Initiating Requests
To initiate a request, the Canvas Studio user must create Canvas components, such as forms, templates, shortcuts, reports, entitlements and events. Let's assume that the user needs to create a form.
Click Create >Form.
...