All Products
Search

This Product

    Data Management:Create an iteration template

    Document Center

    Data Management:Create an iteration template

    Última atualização: May 21, 2026

    Iteration templates in DMS allow you to customize the development process and control its quality. You can use this feature for all ticket types, including data change, schema design, and SQL review tickets. This topic describes how to create an iteration template.

    Procedure

    1. Log in to DMS 5.0.

    2. In the top navigation bar, choose Database Development > R&D Space > DevOps.

      Note

      If you use the DMS console in simple mode, move the pointer over the 2023-01-28_15-57-17.png icon in the upper-left corner of the console and choose All Features > Database Development > R&D Space > DevOps.

    3. Click the Iteration Template tab.
    4. Click Create Iteration Template.
    5. On the Create Iteration Template page, configure the following settings and click OK.
      Parameter Description
      Template name Enter a name for the template.
      Usage scope Select the scope in which the template can be used.
      • All Members: All users within the tenant can use the template.
      • Specified Members: Only specified users can use the template.
      Description Enter a description for the iteration template to aid in its future use and management.
    6. Click the name of the new iteration template to open the Template Details page.
    7. Customize the iteration stages to match your development process.
      • To add an iteration stage, click Add and enter a name for the stage.
      • To edit the name of an iteration stage, select the stage and click the 5编辑 icon next to its name to modify it.
        Note By default, a new template includes the Development and Production iteration stages. You can edit or delete these stages.
      • To delete an iteration stage, select the stage, click the 删除 icon next to its name, and then click OK.
    8. For each iteration stage, select it and configure its rules.
      1. Click the Basic Rule Settings tab and configure the following rules.
        Parameter Description Actions
        Database environment type Specifies the database environment types that can be selected when you create a ticket in this iteration stage. Click the value in the Database environment type field and add or remove environment types from the drop-down list.
        Stage progression permissions Specifies which users can advance the iteration to the next stage. Click the value in the Stage promotion personnel authority field and add or remove users from the drop-down list.
        Note Only the iteration creator and participants can advance the iteration stage.
        Rollback management Specifies if users can roll back the iteration to a previous stage. Click the value in the Fallback management field and select Rollback Allowed or Rollback Not Allowed from the drop-down list.
        Note This setting is not available for the first iteration stage.
      2. Click the Stage Tickets and Checkpoints tab to configure ticket rules.
        • To add a ticket rule, click Create Ticket Rule.
          • From the Ticket Type drop-down list, select a ticket type:
            • Data Change: Includes standard data change, lock-free change, data import, and programmable objects.
            • Schema Design.
            • SQL Review.
            • Database and Table Synchronization: Includes schema synchronization and empty database initialization.
            Note You can create rules for multiple ticket types within each iteration stage.
          • From the Required drop-down list, select Yes or No.
            • Yes: A ticket of the specified type must be created in this stage. Otherwise, the iteration cannot be advanced to the next stage.
            • No: The iteration can be advanced to the next stage even if a ticket of this type is not created.
          • From the Stage Status (Click Value to Modify) drop-down list, select one or more ticket statuses.
            Parameter Actions
            Data Change
            • No Check: The ticket status is not checked. The iteration can advance.
            • Execution Successful: The iteration can advance after the ticket is successfully executed.
            • Closed: The iteration can advance after the ticket is closed.
            Schema Design
            • No Check: The ticket status is not checked. The iteration can advance.
            • Design nodes completed: The iteration can advance after the design nodes of the schema design ticket are completed.
            • The nth node is completed: The iteration can advance after the nth node of the ticket is completed.
              Note
              • The value of n is an integer from 1 to 7.
              • To learn about the configuration of each node in schema design, see the Schema Design > Basic Configurations > Development Process definition in the security rules for the instance that hosts the target database.
            • Published: The iteration can advance after the ticket is published.
            • Ticket complete: The iteration can advance after the ticket is complete.
            • Closed: The iteration can advance after the ticket is closed.
            SQL Review
            • No Check: The ticket status is not checked. The iteration can advance.
            • Review Passed: The iteration can advance after the ticket passes review.
            Database and Table Synchronization
            • No Check: The ticket status is not checked. The iteration can advance.
            • Execution Successful: The iteration can advance after the ticket is successfully executed.
            • Closed: The iteration can advance after the ticket is closed.
            Note You can select multiple ticket statuses for the progression check.
        • To delete a ticket rule, click Delete next to the ticket type.
      3. Click the Stage Progression Approval Process tab to configure the approval process.
        Parameter Description Actions
        Failed status check The ticket status does not meet the progression criteria. Click the value in the Failed Status Check field and select a status from the drop-down list.
        • No propulsion allowed: If the ticket fails the status check, it cannot be advanced to the next stage.
        • Can be promoted and requires approval: If the ticket fails the status check, it can advance to the next stage with approval.

          For example, if you set the status check to Can be promoted and requires approval, the approvers could be the project test engineer and the project administrator, in that order.
        Passed status check The ticket status meets the progression criteria. Click the value in the Passed Status Check field and select a status from the drop-down list.
        • Can be promoted without approval: If a ticket passes the status check, it can advance to the next stage without approval.
        • Can be promoted and requires approval: If a ticket passes the status check, it can advance to the next stage only with approval.

          For example, if you set the status check to Can be promoted and requires approval, the approver could be the project test engineer.