The iteration template feature of Data Management (DMS) allows you to customize R&D processes and control 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

  1. Log on to the DMS console.
  2. In the top navigation bar, move the pointer over the All functions icon and choose R&D Space > DevOps.
  3. Click the Iteration Template tab.
  4. Click Create Iteration Template.
  5. 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.
    • 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

  1. Log on to the DMS console.
  2. In the top navigation bar, move the pointer over the All functions icon and choose R&D Space > DevOps.
  3. Click the Iteration Template tab.
  4. Click the name of the iteration template that you want to manage.
  5. On the Template Details page, you can perform the following operations:
    • To modify the name of the iteration template, click the 5编辑 (2) 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. The iteration template is available when you create a project or an iteration.
      • Disabled: The iteration template is disabled. The iteration template is unavailable when you create a project or an iteration.
    • To modify the description of the iteration template, click the 5编辑 (2) 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 operation 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 a development environment. For example, you can configure the development, testing, production, and publishing stages.

  1. Log on to the DMS console.
  2. In the top navigation bar, move the pointer over the All functions icon and choose R&D Space > DevOps.
  3. Click the Iteration Template tab.
  4. Click the name of the iteration template that you want to configure. The Template Details page appears.
  5. 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.
  6. To modify the name of an iterative stage, click the 5编辑 icon next to the name of the iterative stage that you want to modify.
    Note By default, a new iteration template contains two iterative stages: Dev and Product. These two stages can be modified and deleted.
  7. To delete an iterative stage, click the 5删除 icon next to the name of the iterative stage that you want to delete. In the message that appears, click OK.
  8. Click an iterative stage and configure rules for the stage. Repeat this step for each stage.
    1. Click the Rule base configuration tab and configure the basic rules.
      Parameter Description Operation
      Database environment type Specify one or more types of environments to which databases belong. Then, you can select the databases in the selected environments when you create tickets in the iterative stage. Click the value next to Database environment type. From the drop-down list, select one or more environment types. You can also remove the selected environment types.
      Stage promotion personnel authority Specify one or more types of users who have the permissions to advance the iteration to the next stage. Click the value next to Stage promotion personnel authority. From the drop-down list, select one or more user types. You can also remove the selected user types.
      Note Only the creator and participants of an iteration can advance the iteration to the next stage.
      Fallback management Specify whether the iteration can be rolled back after it is advanced to the next stage. Click the value next to Fallback management. From the drop-down list, select Allow Rollback or Rollback not allowed.
      Note The Fallback management parameter is not displayed in the first iterative stage of the iteration template.
    2. Click the Stage Work Orders 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, Large Data Import, and Programmable Object tickets
          • Structural design: schema design tickets
          • SQL audit: SQL review tickets
          • Library table synchronization: database and table synchronization tickets, including the Schema Synchronization and Empty Database Initialization tickets
          Note You can specify the types of tickets that can be created in the iterative stage.
        • Select Yes or No from the Required 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.
          Structural 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 checked.
          • 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 checked.
            Note Valid values of n: 1 to 7.
          • 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 audit
          • 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.
          Note You 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.
    3. Click the Stage to advance the approval process tab and configure 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 next to Non-compliance status check. 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.

        1 DevOps-符合推进审批
      Compliance check The action to take if the status of the ticket meets the requirements of the iteration template. Click the value next to Compliance check. 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.

        1 DevOps-不符合推进审批

References