How To Use Visibility Rules in a Detail Page or Milestone Diagram
The DCM Page Builder and the Milestone Builder can hide elements or transitions based on the result of a custom rule.
The rule needs to be an SQL Function that has input depending on what it's used for, but the output always has to be a 0 (false/hide) or 1 (true/show).
Detail Page Builder Visibility Rules
To determine if an element will be hidden or shown, the invoker executes an AppBase Rule with the tag 'cust' or 'Page Element Visibility'. Visibility and Readonly rules have the same signature and are tagged by 'Page Element Visibility' tag.
DCM Sample Rules:
Samples of visibility function rules are explained below.
QA_return0Fn | SQL rule function that always determines 0 (hidden) |
QA_return1Fn | SQL rule function that always determines 1 (show) |
SMPL_visByStateFn | SQL rule function that determines visibility by the milestone or state code |
SMPL_visByPriorityFn | SQL rule function that determines visibility by the priority code |
Possible Input Parameters:
These are the parameters of the function. You don't need to fill anything out. DCM will add itself. It needs one input parameter at least.
Case | Case_Id or CaseId (Number) | Optional |
Task | Task_Id or TaskId (Number) | Optional |
Party | ExternalParty_Id or ExternalPartyId (Number) | Optional |
MDM | EntityId (Number) | Optional |
Milestone Diagram Visibility Rules
The invoker executes an AppBase Rule with the tag 'cust' or 'Case Route Visibility'. All custom rules should be tagged 'cust' to select them.
A custom rule that is attached to a Transition to determine his visibility.
DCM Sample Rules:
Samples of visibility function rules are explained below.
QA_return0Fn | SQL rule function that always determines 0 (hidden) |
QA_return1Fn | SQL rule function that always determines 1 (show) |
SMPL_visByBusinessRoleFn | SQL rule function that determines visibility by the business role of a current user |
SMPL_visByTransitionCodeFn | SQL rule function that determines visibility by the transition code |
SMPL_visByStateFn | SQL rule function that determines visibility by the milestone code |
Possible Input Parameters:
These are the parameters of the function. You don't need to fill anything out. DCM will add itself. It needs one input parameter at least.
Case | Case_Id or CaseId (Number) | Optional |
Task | Task_Id or TaskId (Number) | Optional |
Party | ExternalParty_Id or ExternalPartyId (Number) | Optional |
Milestone | Input (NCLOB) | Could be used by Milestone visibility rules to determine a transition data |