Configure approval processes for database clone tickets using security rules in Data Management (DMS).
By default, DMS applies a built-in approval template to all database clone tickets. To require a specific approval workflow or block certain clone operations, create a custom security rule under the Approval Rule Validation checkpoint. If no custom rule matches a ticket, the default approval template applies automatically.
Prerequisites
Before you begin, ensure that you have:
Access to the DMS console V5.0
Permission to edit security rule sets
Key concepts
Checkpoints
A checkpoint is a stage in the ticket lifecycle where DMS evaluates whether the ticket meets the conditions defined in your security rules. Database clone tickets use a single checkpoint: Approval Rule Validation.
Actions
An action defines what DMS does when the IF condition in a security rule is met. Each action name starts with the @act. prefix, followed by the action's display name.
The following actions are available for the Approval Rule Validation checkpoint in Database Clone:
| Action | Description |
|---|---|
@act.forbid_submit_order | Blocks ticket submission. Specify a reason in the format: @act.forbid_submit_order 'Reasons for forbidding the submission of the ticket' |
@act.do_not_approve | Specifies the ID of an approval template to use. For details, see Configure approval processes. |
@act.choose_approve_template | |
@act.choose_approve_template_with_reason |
Example DSL rule:
The following rule always routes database clone tickets to approval template 853:
if 1 > 0
then
@act.choose_approve_template 853
endReplace 853 with the ID of the approval template you want to use. For DSL syntax details, see DSL syntax for security rules.
Template database
DMS includes a predefined security rule template for database clone: Approval process for database clone. Load this template as a starting point when creating a custom rule.
Modify the default approval template
Log in to DMS 5.0.
-
Move the pointer over the
icon in the upper-left corner and choose . NoteIf you use the DMS console in normal mode, choose in the top navigation bar.
Find the rule set of the target database and click Edit in the Actions column.
On the Details page of Security Rules, choose Database Development > Database Clone in the left-side navigation pane.
In the row of Default approval template for database clone, click Edit in the Actions column.
In the Change Configuration Item dialog box, click Switch Approval Template.
In the Switch Approval Template dialog box, find the target approval template and click Select in the Actions column.
To skip approval for all database clone tickets, click Reset to Free of Approval.
Click Submit.
Create a rule
Log in to DMS 5.0.
-
Move the pointer over the
icon in the upper-left corner and choose . NoteIf you use the DMS console in normal mode, choose in the top navigation bar.
Find the rule set of the target database and click Edit in the Actions column.
On the Details page of Security Rules, choose Database Development > Database Clone in the left-side navigation pane.
Select Basic Configuration Item for Checkpoints, then click Create Rule and configure the following settings:
Setting Required Description Checkpoints Yes The checkpoint under which the rule applies. Database clone provides one checkpoint: Approval Rule Validation. Template database No A predefined rule template to start from. After selecting a checkpoint, click Load from Template Database and choose a template. See Key concepts for available templates. Rule name Yes A name for the custom rule. If you load a template, the name is populated automatically. Rule DSL Yes The Domain-Specific Language (DSL) statement that defines the rule logic. See DSL syntax for security rules. If you load a template, the DSL is populated automatically. Click Submit.
Enable the rule.
New rules are Disabled by default. To activate the rule, click Enable in the Actions column, then click OK.
What's next
Configure approval processes — Set up the approval templates referenced in your rules.
DSL syntax for security rules — Write conditions that match specific clone tickets.