The iteration template feature of Data Management (DMS) allows you to customize R&D processes and manage the quality of R&D processes. This feature can be used in combination with various types of tickets such as data change, schema design, and SQL review. This topic describes how to create and configure an iteration template.
Create an iteration template
- Log on to the DMS console V5.0.
- In the top navigation bar, move the pointer over the All Features icon and choose .
Click the Iteration Template tab.
Click Create Iteration Template.
In the Create Iteration Template dialog box, set the parameters that are described in the following table and click OK.
Parameter
Description
Template Name
The name of the iteration template.
Usage Scope
The scope within which the iteration template is available. Valid values:
Available for All Users: This iteration template can be used by all the users of the current tenant.
Specific Users: This iteration template can be used only by specific users.
Description
The description of the iteration template. Enter an informative description that can help you manage the iteration template.
Manage an iteration template
- Log on to the DMS console V5.0.
- In the top navigation bar, move the pointer over the All Features icon and choose .
Click the Iteration Template tab.
Click the name of the iteration template that you want to manage.
On the Template Details page, you can perform the following operations:
To modify the name of the iteration template, click the
icon next to the template name. To change the status of the iteration template, turn on Status. In the message that appears, click OK.
Enabled: The iteration template is enabled and can be used when you create a project or an iteration.
Disabled: The iteration template is disabled and cannot be used when you create a project or an iteration.
To modify the description of the iteration template, click the
icon next to Template Description. Configure the iteration template. For more information, see Configure an iteration template.
To create a similar iteration template, click Create As in the upper-right corner. In the Replicate Iteration Template dialog box, set the Name and Description parameters. Then, click OK.
To view the operation records of the iteration template, click Operation History in the upper-right corner. In the Operation History panel, you can view the operation time, operator, and logs of each operation performed on the iteration template.
Configure an iteration template
When you configure an iteration template, you can create, delete, or modify an iterative stage and configure rules for each stage. An iterative stage indicates a specific stage of an R&D process in the development environment. For example, you can configure the development, testing, production, and publishing stages.
- Log on to the DMS console V5.0.
- In the top navigation bar, move the pointer over the All Features icon and choose .
Click the Iteration Template tab.
Click the name of the iteration template that you want to configure. The Template Details page appears.
To create an iterative stage, click Add in the left-side pane, enter a name in the field, and then click a blank area on the page.
To modify the name of an iterative stage, click the
icon next to the name of the iterative stage that you want to modify. NoteBy default, a new iteration template contains two iterative stages: Dev and Product. These two stages can be modified and deleted.
To delete an iterative stage, click the
icon next to the name of the iterative stage that you want to delete. In the message that appears, click OK. Click an iterative stage and configure rules for the stage. Repeat this step for each stage.
Click the Basic Rule Configuration tab and configure the rules that are described in the following table.
Rule
Description
Operation
Database environment type
Specifies one or more types of environments to which databases belong. You can select the databases in the selected environments when you create tickets in the iterative stage.
Click the value in the Parameter column of the Database environment type rule. From the drop-down list, select one or more environment types. You can also remove the selected environment types.
Stage promotion personnel authority
Specifies one or more types of users who have the permissions to advance the iteration to the next stage.
Click the value in the Parameter column of the Stage promotion personnel authority rule. From the drop-down list, select one or more user types. You can also remove the selected user types.
NoteOnly the creator and participants of an iteration can advance the iteration to the next stage.
Fallback management
Specifies whether the iteration can be rolled back after it is advanced to the next stage.
Click the value in the Parameter column of the Fallback management rule. From the drop-down list, select Allow Rollback or Rollback not allowed.
NoteThe Fallback management rule is not displayed in the first iterative stage of the iteration template.
Click the Tickets and Checkpoints tab and configure rules for tickets.
To create a ticket rule, click Create Ticket Rule.
Select a ticket type from the Ticket Type drop-down list. Valid values:
Data change: data change tickets, including the Normal Data Modify, Lockless change, Data Import, and Programmable Object tickets
Schema design: schema design tickets
SQL Review: SQL review tickets
Library table synchronization: database and table synchronization tickets, including the Schema Synchronization and Empty Database Initialization tickets
NoteYou can specify the types of tickets that can be created in the iterative stage.
Select Yes or No from the Required (Click Value to Modify) drop-down list.
Yes: You must create a ticket of the specific type in the iterative stage. Otherwise, the iteration cannot be advanced to the next stage.
No: The iteration can be advanced to the next stage regardless of whether you create a ticket of the specific type in the iterative stage.
From the Stage Status (Click Value to Modify) drop-down list, select whether to check the status of a ticket and the ticket state that allows the iteration to be advanced to the next stage.
Ticket type
Operation
Data change
Do not check: does not check the status of the ticket and allows the iteration to be advanced to the next stage.
Successful execution: allows the iteration to be advanced to the next stage if the data change is performed.
Closed: allows the iteration to be advanced to the next stage if the ticket is closed.
Schema design
Do not check: does not check the status of the ticket and allows the iteration to be advanced to the next stage.
Design node completed: allows the iteration to be advanced to the next stage after the design node of the schema design ticket is complete.
The nth node has been completed: allows the iteration to be advanced to the next stage after the nth node of the schema design ticket is complete.
NoteValid values of n: 1 to 7.
To view the configuration of each node in a schema design ticket, go to the Details page of security rules for the database that you want to manage and click the tab. On this tab, find the R & D process rule under the Basic Configuration Item checkpoint and click Edit in the Actions column.
Published: allows the iteration to be advanced to the next stage if the schema design is published.
Work order closed: allows the iteration to be advanced to the next stage if the schema design is complete.
Closed: allows the iteration to be advanced to the next stage if the ticket is closed.
SQL Review
Do not check: does not check the status of the ticket and allows the iteration to be advanced to the next stage.
Audit successful: allows the iteration to be advanced to the next stage if the SQL review is complete.
Library table synchronization
Do not check: does not check the status of the ticket and allows the iteration to be advanced to the next stage.
Successful execution: allows the iteration to be advanced to the next stage if the synchronization is complete.
Closed: allows the iteration to be advanced to the next stage if the ticket is closed.
NoteYou can select multiple ticket states that allow the iteration to be advanced to the next stage based on your requirements.
To delete a ticket rule, click Delete in the Actions column.
Click the Procedure and Approval tab and configure rules for approval processes.
Rule
Description
Operation
Non-compliance status check
The action to take if the status of the ticket does not meet the requirements of the iteration template.
Click the value in the Parameter column of the Non-compliance status check rule. Select an action to take from the drop-down list. Valid values:
No propulsion allowed: does not allow the iteration to be advanced to the next stage.
Can be promoted and requires approval: allows the iteration to be advanced to the next stage after approval.
In the following figure, Can be promoted and requires approval is selected for the Non-compliance status check rule. Project testers and project administrators are selected as approvers in sequence.
Compliance check
The action to take if the status of the ticket meets the requirements of the iteration template.
Click the value in the Parameter column of the Compliance check rule. Select an action to take from the drop-down list. Valid values:
Can be promoted without approval: allows the iteration to be advanced to the next stage without approval.
Can be promoted and requires approval: allows the iteration to be advanced to the next stage after approval.
In the following figure, Can be promoted and requires approval is selected for the Compliance check rule. Project testers are selected as approvers.
