Siebel Master Data Applications Reference for Industry Applications > Architecture and Framework >

About Siebel Master Data Application Workflows

Workflows are a feature of Siebel Master Data Applications. They automate the business processes associated with managing data stored in the master data application.

You can modify these workflows to suit your own business model using Siebel Business Process Designer. For more information, see Siebel Business Process Designer Administration Guide.

To view the diagrams of the following workflows, use the Workflow Process Designer view in Administration - Business Process screen.

The following workflows describe the business processes for the Siebel Universal Customer Master (Siebel UCM):

• UCM Batch Process - Single Step
• UCM Server Party Package Workflow (MQSeries Server Transport)
• UCM Server Party Package Workflow (MQSeries Server Transport Error Handling)
• UCM Server Party Package Workflow (File Transport)
• UCM Async Real-time Publish Workflow
• UCM Daily Publish Workflow
• UCM Account Batch Data Management Workflow
• UCM Contact Batch Data management Workflow
• UCM Batch Process Workflow

UCM Batch Process - Single Step

This workflow mainly calls the UCM Batch Manager business service to process the queued Insert requests or records imported through EIM. The workflow looks for queued or batch records in the Source Data History table, then calls UCM Data Quality Manager to cleanse and match the records. Depending on the match results, it then calls Transaction Manager to execute the insert or update operation, or store the cleansed version for later deduplication processing.

NOTE:  This workflow may be configured to be invoked by the UCM Batch Process server component (alias UCMBatchProcess).

UCM Server Party Package Workflow (MQSeries Server Transport)

This workflow handles incoming requests. It converts and dispatches the incoming request message, checks if the source system has privileges for the requested operations, executes the operations, captures source version, captures History version as necessary, invokes CDM and Survivorship as necessary, and publishes to other subscribing systems. It is expected that this workflow process is the dispatch workflow for an MQSeries Receiver.

This workflow receives data as a CRMML message, which differs the UCM Batch Process workflow in that it does not going through the SDH tables.

UCM Server Party Package Workflow (MQSeries Server Transport Error Handling)

This workflow is the same as UCM Server Party Package Workflow (MQSeries Server Transport) but additionally handles errors.

This workflow receives data as a CRMML message, which differs from the UCM Batch Process workflow in that it does not go through the SDH tables.

NOTE:  As this workflow reads in the input from file, it is intended for debugging purposes.

UCM Server Party Package Workflow (File Transport)

This workflow is the same as UCM Server Party Package Workflow (MQSeries Server Transport) but additionally handles reading the request message from a file and writing the response message to a file.

UCM Async Real-time Publish Workflow

This workflow is invoked as part of a server request to perform asynchronous real-time publishing. It is called from either the connector workflow (for example, UCM Server Party Package Workflow (MQSeries Server Transport)) or Batch Data Management workflow (UCM Batch Process) when the real-time Publish/Subscribe flag is true.

In this workflow, the second step, RealTimePublish, calls the UCM Publish/Subscribe service with the method RealTimePublishMethod(). This method of UCM Publish/Subscribe Business Service handles the actual publishing of the message to the registered systems.

Real-time, asynchronous, publishing increases the performance for both the Connector workflow and the batch data management workflow.

UCM Daily Publish Workflow

This workflow is a one-step workflow calling the PublishMethod without sending in any input message. When run from UCM Batch Publish Subscribe (alias UCMBatchPubSub) server component, the Workflow Process Manager (alias WfProcMgr) triggers this workflow.

There are three server component parameters that UCMBatchPubSub reads during this process:

• UCM Batch Object Type (alias UCMBatchObjectType)
• UCM Batch Size (alias UCMBatchSize)
• UCM Sleep Time (alias UCMSleepTime)

This workflow publishes all the new and updated records to the registered systems with Publish Frequency set as Daily Batch.

UCM Account Batch Data Management Workflow

This workflow performs the same task as the UCM Batch Process - Single Step workflow but only processes Account records. The steps are exposed so they can be configured if necessary. The Workflow Process Batch Manager server component (alias WfProcBatchMgr) retrieves the IDs of records to be processed and then invokes this workflow to cleanse and match account data.

UCM Contact Batch Data management Workflow

This workflow performs the same task as the UCM Batch Process - Single Step workflow but only processes Contact records. The steps are exposed so they can be configured if necessary. The Workflow Process Batch Manager server component (alias WfProcBatchMgr) retrieves the IDs of records to be processed and then invokes this workflow to cleanse and match account data.

UCM Batch Process Workflow

This workflow also performs the same task as the UCM Batch Process - Single Step workflow, but the steps process multiple records instead of one record at a time. It will be invoked by the UCM Batch Process server component (alias UCMBatchProcess).