Manage pending data standard objects

Actions

Description

Filter

You can perform a fuzzy search by object name or use precise filters such as object type, last update time, last updated by, deployment status, change type, and environment change.

• Batch Search: Click Batch Search. In the Batch Search dialog box, you can enter search terms for multiple objects, with a maximum of 1,000 entries. Separate each term with a line break. After you click OK, the system performs an exact match search and displays the results in the list below.

• Filter:

  • Object Type: This filter applies only to standard objects. You can select one or more object types at a time. The types include code table directory, standard set directory, standard set, standard template, data standard, and common standard attribute.

  • Deployment Status: You can select one or more statuses at a time. Statuses include To be deployed, Queued, Deploying, Deployment Succeeded, Deployment Failed, and Succeeded with Risks. Queued indicates that the object is in the deployment queue waiting to be processed. Succeeded with Risks indicates that the deployment was successful, but the deployed content differs from the imported content. This status is a warning and does not affect the object's usability.

  • Last Updated By: You can select one or more users from the system list to filter the results.

  • Last Update Time: Filter by a start and end date. The format is YYYY-MM-DD hh:mm:ss.

  • Change Type: You can select one or more change types at a time. Types include Add, Update, and Delete.

  • Environment Change: Select whether the target environment has been changed since the last import.

  • Project Type: Select Dev-Prod or Basic mode.

  • Is Active: This filter applies only to standard-to-asset mapping rule objects. Select whether the rule is active.

  • Mapping Type: This filter applies only to mapping relationship objects. You can select one or more types. The types include Valid Mapping and Invalid Mapping.

  • Asset Type: This filter applies only to mapping relationship objects. Asset types include physical table, physical view, materialized view, regular dimension logical table, hierarchical dimension logical table, enumerated dimension logical table, virtual dimension logical table, transaction fact logical table, event fact logical table, snapshot fact logical table, aggregate logical table, logical view, meta table, and mirrored table.

Deploy

You can redeploy objects with a Deployment Failed or To be deployed status. Both individual deployment and batch deployment are supported. Objects that are already deployed do not need to be redeployed.

• Individual deployment: In the Actions column for the target object, click Deploy. In the dialog box that appears, enter a deployment name (up to 64 characters) and click OK.

• Batch deployment: Select the checkboxes next to the target objects, or click Select All or Select Current Page at the bottom of the page. After selecting the objects, click Deploy at the bottom of the page. In the dialog box that appears, enter a deployment name (up to 64 characters) and click OK.

  Note

  Select All applies to all objects that match the current filter and search criteria. Select Current Page applies only to the objects on the current page.

View Details

Displays the details of a single object in the target environment.

Compare Versions

Version comparison is available only for objects with a change type of Update. It compares the imported object version with the latest version in the target environment.

Deployment Details

In the Deployment Details dialog box, you can view basic information, process check results, and exception alerts. The Process Check section includes permission check, dependency check, duplicate name check, and deployment check. The specific checks vary depending on the object type.

• permission check: This check applies only to standard object, code table, and business entity objects. If the permission check in the cross-tenant deployment settings is Validate Operator Permissions, the system verifies the operator permissions for each object during import. If this setting is Ignore Permission Check, the system skips this check.

  Note

  During deployment, the system checks whether the member assigned by the import policy has the required permissions.

• dependency check:

  • standard object: Checks for the existence of dependent objects.

    • When the change type of a code table directory is Add or Update, the system checks whether the parent directory exists. When the change type is Delete, it checks whether the code table directory is empty (that is, whether the current deployment item contains subdirectories or code tables).

    • When the change type of a standard set directory is Add or Update, the system checks whether the parent directory exists. When the change type is Delete, it checks whether the standard set directory is empty (that is, whether the current deployment item contains subdirectories or standard sets).

    • When the change type of a common standard attribute is Add or Update, the system checks whether the code table referenced in the current deployment item exists in the target environment. When the change type is Delete, no dependency check is performed.

    • When the change type of a standard template is Add or Update, the system checks whether the code table referenced by the standard template being deployed exists in the target environment. When the change type is Delete, it checks whether the standard template is referenced by any data standard in the target environment.

    • When the change type of a standard set is Add or Update, the system checks whether the standard set directory and the configured default standard template for the standard set being deployed exist in the target environment. When the change type is Delete, it checks whether the standard set being deployed is empty (that is, whether any data standards have been created under it in the current deployment item).

    • When the change type of a data standard is Add or Update, the system checks whether the following dependencies exist in the target environment: the parent standard set, the referenced standard template and its version, referenced code tables (if used as an attribute value), referenced code values (if used as an attribute value), specified data categories (if used as an attribute value), specified data security levels (if used as an attribute value), quality rule templates referenced by the standard monitoring configuration, identifiers, projects (if used as an attribute value), and data domains (if used as an attribute value). When the change type is Delete, no dependency check is performed.

  • standard-to-asset mapping rule: When the change type is Add or Update, the system checks whether the filter conditions in the asset selection, and the source standard set and standard template in the data standard selection exist in the target environment. When the change type is Delete, no dependency check is performed.

  • mapping relationship: When the change type is Add, the system checks whether the mapped asset (data table), and all metrics, fields, data standards, and quality monitoring rules specified in the mapping relationships exist in the target environment. When the change type is Delete, no dependency check is performed.

  • code table: When the change type is Delete, the system checks whether the code table being deployed is referenced by a standard template in the target environment and whether its parent code table directory exists in the target environment. If the code table belongs to the root directory, the deployment is not blocked. When the change type is Add or Update, no dependency check is performed.

• duplicate name check:

  • standard object: Checks if an object with the same name exists in the target environment. This check is performed only when the change type is Add or Update.

    • Code table directory: Checks if a directory with the same name and code already exists under the parent directory.

    • Standard set directory: Checks if a directory with the same name and code already exists under the parent directory.

    • Common standard attribute: Checks if an attribute with the same name exists within the same attribute type (custom or system).

    • standard template: Checks for duplicate names or codes.

    • standard set: Checks for duplicate names or codes within the parent directory.

    • data standard: Checks for duplicate names within the parent standard set.

  • standard-to-asset mapping rule: When the change type is Add or Update, checks for duplicate rule names.

  • code table: When the change type is Add or Update, checks for unique names or codes.

• deployment check:

  • standard object: Verifies if the deployment process is successful. In addition to rerunning the preceding pre-checks, this check includes object count validation, object existence validation, and sales control validation. The system also processes object content based on the cross-tenant deployment settings and the current import policy settings, such as modifying the approval process for a standard set.

    Note

    When the change type of a data standard is Add or Update, the criteria for a successful deployment depend on the deployment approval settings and whether the deployment policy is configured to automatically submit a go-live request:

    • If deployment approval is set to be ignored in the cross-tenant deployment settings and the deployment policy is configured to submit a go-live request, the standard is successfully deployed only after it is deployed to the production environment.

    • If deployment approval is required in the cross-tenant deployment settings and the deployment policy is configured to automatically submit a go-live request:

      • If go-live approval is enabled for the standard set in the target environment, the deployment is successful once an approval task is generated. The system does not check the task's status.

      • If go-live approval is not enabled for the standard set in the target environment, no approval task is generated. The standard must be deployed to the production environment to be successfully deployed.

    • If the deployment policy is not configured to automatically submit a go-live request, creating the standard in draft status counts as a successful deployment.

  • standard-to-asset mapping rule: Verifies if the deployment process is successful. In addition to rerunning the preceding pre-checks, the system checks the rule count for Add or Update changes, and verifies that the object has been deleted for Delete changes.

  • mapping relationship: Verifies if the deployment process is successful. In addition to rerunning the preceding pre-checks, the system checks if the object has already been deleted for Delete changes.

  • code table: Verifies if the deployment process is successful. In addition to rerunning the preceding pre-checks, the system checks the code table count for Add or Update changes, and verifies that the object has been deleted for Delete changes.

  • business entity: Verifies if the deployment process is successful. In addition to rerunning the preceding pre-checks, this check includes business entity count validation and business entity existence validation. It also performs checks based on the current import policy settings.

• Mapping Conversion: This check applies only to mapping relationship objects. When the change type for a standard-to-asset mapping rule is Add, the system checks whether the conversion for the mapping relationship being deployed is successful, based on the import policy settings. This check is not performed when the change type is Delete.