A Business Entity (BE) represents the main entity of the data to be provisioned by TDM. A BE can have multiple LUs with a flat or hierarchical structure. For example, a Customer BE can have Customer Care, Billing, Ordering and Usage LUs. Each LU can be attached to multiple BEs.
The Business Entities window displays a list of all BEs defined in the TDM. Only Admin users can create, edit or delete a BE. Other users can open BEs for view only purposes.
The Business Entity window displays information about a selected BE. It has three main sections:
The following is an example of a Customer Business Entity window:
The General Information section holds the BE Name and Description. The Name setting is mandatory. Note that only one active BE can have a specific Name. An error is displayed when an attempt is made to create several BEs with the same name.
To use a BE in a TDM task, it must have one or more LUs assigned.
Do either:
Check All Logical Units to attach all LUs that are deployed to Fabric and that are not attached to the BE. The LUs are attached to the BE in a flat structure whereby the Parent LU is empty. When needed, the LUs can be edited to populate the Parent LU and the Data Center settings.
Check Select and select an LU from the Logical Unit dropdown list:
Click Add Logical Units to add the selected LUs to the BE.
Notes:
Click or to edit or delete the LU from the BE. Note that the LU is deleted from the BE in the TDB DB.
Click for more information about TDM DB tables that hold the BE and LU relationship.
This tab enables adding post-execution processes that must run at the end of the task's execution after all the related LUs have been executed. For example, sending an mail to the tester to notify them that the execution of a task has ended.
Post-execution processes are Broadway flows defined in Fabric by the TDM implementer. The relationship between a post-execution process and a BE is many to many. That is, a BE can have several post-execution processes, and a post-execution process can be attached to multiple BEs.
The task execution process executes the BATCH command on each post-execution process attached to the task's BE. The execution order is set according the execution order defined in the BE.
Unlike for LUs, post-execution processes are optional. A BE can be defined without any post-execution processes.
Note that the post execution processes must be populated in trnPostProcessList to be displayed by the BE window.
Click for more information about BE TDM DB tables and the hold BE and post-execution processes relationship.
A Business Entity (BE) represents the main entity of the data to be provisioned by TDM. A BE can have multiple LUs with a flat or hierarchical structure. For example, a Customer BE can have Customer Care, Billing, Ordering and Usage LUs. Each LU can be attached to multiple BEs.
The Business Entities window displays a list of all BEs defined in the TDM. Only Admin users can create, edit or delete a BE. Other users can open BEs for view only purposes.
The Business Entity window displays information about a selected BE. It has three main sections:
The following is an example of a Customer Business Entity window:
The General Information section holds the BE Name and Description. The Name setting is mandatory. Note that only one active BE can have a specific Name. An error is displayed when an attempt is made to create several BEs with the same name.
To use a BE in a TDM task, it must have one or more LUs assigned.
Do either:
Check All Logical Units to attach all LUs that are deployed to Fabric and that are not attached to the BE. The LUs are attached to the BE in a flat structure whereby the Parent LU is empty. When needed, the LUs can be edited to populate the Parent LU and the Data Center settings.
Check Select and select an LU from the Logical Unit dropdown list:
Click Add Logical Units to add the selected LUs to the BE.
Notes:
Click or to edit or delete the LU from the BE. Note that the LU is deleted from the BE in the TDB DB.
Click for more information about TDM DB tables that hold the BE and LU relationship.
This tab enables adding post-execution processes that must run at the end of the task's execution after all the related LUs have been executed. For example, sending an mail to the tester to notify them that the execution of a task has ended.
Post-execution processes are Broadway flows defined in Fabric by the TDM implementer. The relationship between a post-execution process and a BE is many to many. That is, a BE can have several post-execution processes, and a post-execution process can be attached to multiple BEs.
The task execution process executes the BATCH command on each post-execution process attached to the task's BE. The execution order is set according the execution order defined in the BE.
Unlike for LUs, post-execution processes are optional. A BE can be defined without any post-execution processes.
Note that the post execution processes must be populated in trnPostProcessList to be displayed by the BE window.
Click for more information about BE TDM DB tables and the hold BE and post-execution processes relationship.