Skip to main content

Glossary

Key Term Definitions​

The purpose of this document is to clarify the core terminology used in workflow management.This document aims to clarify the key terms used in workflow management. In our system, a workflow is divided into three levels: business, service, and alias, corresponding to the following interface parameters: business_id, feature_name, alias.

  • Business (business_id): The business layer represents different business domains or functional modules and is the highest level in the workflow hierarchy. Each business domain can include multiple services.Each operational area could include multiple services.

  • Service (feature_name): As a subset of the business layer, the service layer denotes various functions or services under a specific business domain. A business domain can contain multiple services, each providing its unique functionality.There are multiple different services within an area of operation, each providing its unique function.

  • Alias (alias)：Aliases belong to a subset of the service layer, mainly used to identify different versions or variants of the service.Alias (alias): The alias layer, a subset of the service layer, is used to identify different versions or variants of a service. A service may have multiple aliases, each potentially corresponding to different configurations or usage scenarios.

This hierarchical structure enables flexible management and operation of workflows, allowing detailed configuration and control according to different business requirements.

Rule Examples​

Generation Rules for Unique Workflow Identifier (descriptor_id)​

  1. Based on MD5 of YAML file:

    Format:

    business_id + ":" + feature_name + ":" + "md5_" + 32-character md5 string generated from the YAML file

    Example:

    DemoFlowTest:DemoTest:md5_4f1707841ad4413fff4afa9d53e526b4

  2. Based on the process alias (using the latest YAML version under the alias by default):

    Format:

    business_id + ":" + feature_name + ":" + alias

    Example:

    DemoFlowTest:DemoTest:sandbox

Generation Rules for Unique Workflow Execution Identifier (execution_id)​

Format:

business_id + ":" + feature_name + "_c_" + 36-character UUID generated based on the timestamp

Example:

DemoFlowTest:demoTest_c_0c0a9d5e-878b-11ee-9fe1-cfc95b641e41