1. Data Catalog
  2. Accessing Data Catalog
  3. Catalog Extension
  4. Catalog Extension Process Workflow

2.5.1 Catalog Extension Process Workflow

The catalog extension process workflow is as follows:

Figure 2-3 Catalog Extension Process Workflow


The image describes the workflow of catalog extension

  • Analyze
    • Analyze the requirements based on the existing details in Data Catalog.
    • Use the Catalog Viewer to understand existing Business Terms, logical entities and their properties.
  • Review
    • Prepare the list of Gaps – additional business terms, dimensions, fact extensions and other associated properties.
    • Document the list of Gaps – group based on type and purpose of extensions.
    • Review the list of Gaps to ensure if the proposed additions are consistent and conformance according to the Data Catalog Extension Principles and Naming Standards.
  • Document
    • An Issue Administrator will Log an Issue (Category as Catalog Extensions) based on the purpose of the extension. To know how to log an Issue, see the Issues section.
    • Document the details of the extension requirements in the Issue. Upload the analysis and requirement documents.
    • Assign to the Issue Owner.
  • Action
    • Issue Owners create Action (Type as Catalog Extension) for the issue. It is recommended to define an action for each type of change. To learn how to create an Action, see the Actions Section in the OFS Accounting Foundation Cloud Service Core Functions User Guide.
    • Upload the document containing the list of changes in Action details.
    • Action Owners create or extend the catalog objects based on the type of Change Request.
    • Action Owners submits the action for approval.
  • Publish
    • Issue Owner reviews submitted actions and approves or rejects along with appropriate comments.
    • After approval no modification is allowed to object definitions.
    • Issue Administrator publishes the approved Action to approve the changes in the Catalog data model.
    • Actions need to be published sequentially and in the logical sequence that would be reflected in schema. To use a Custom BT in a new Dimension Entity or while Extending the Fact, first create and publish the Business Term. Once the BT is published, it will available in the list of Available Business Terms during creation of Dimension Entity and while extending a Fact.
    • You can verify the published Actions from Catalog Viewer for Dimension Entity and Extend Fact Entity.
    • Please note that extensions will be reflected in master repository of objects only on Publish and it is mandatory to publish before users can view or consume the object for further extensions.
    • If a Publish action is successful, the action is displayed under Publish tab. If a Publish action is unsuccessful, the action is displayed under Approved tab.

      Note:

      • To publish an action, the custom DQ rule must be mapped to at least to one group. A custom rule which is not mapped to any group will not be published.
      • Similarly, to publish an action, the custom DQ group must be mapped to at least one rule. A custom DQ group with no DQs mapped to it will not be published.