Enabling UCM Transaction Manager Callback Functions

You can enable the UCM Transaction Manager’s callback functions depending on the business model you are using. You can also enable both functions, before commit Hook 1 and after commit Hook 2, by adding new Business Service User Prop using Siebel Tools.

Note: The UCM Transaction Manager’s callback functions is not a default function, you must enable it to Configure the UCM Transaction Manager Callback Functions.

To enable UCM Transaction Manager’s callback functions for both real-time and batch process

1. In Siebel Web Tools, create a new workspace to deliver repository changes to runtime database.

2. In Object Explorer, select Business Service: UCM Transaction Manager.

3. Select Business Service User Prop, and create a new record.

4. To enable Hook 1 (before commit), enter the name of new Business Service User Prop: Custom Business Service.

   To enable Hook 2 (after commit), enter the name of new Business Service User Prop: Custom Business Service After Commit.

5. In the value of new Business Service User Prop, enter the Business Service Name and Method, separated by a colon.

   Format: "Business Service Name "+ ": "+ "Business Service Method Name". For example, UCM Utility Service:PositiveTestAfterCommit

6. Add checkpoint and submit workspace for delivery.

7. Deliver repository changes to runtime database.

The diagram below shows both callback functions are enable, invoking methods in our internal testing business service UCM Utility Service users should create their own custom business service to handle UCM Transaction Manager’s callback function.

To enable UCM Transaction Manager’s callback functions only for real-time process

1. Create a new workspace to deliver repository changes to runtime database in Siebel Tools.

2. Edit the following workflow processes:

   For CONTACT: UCM Person Customer Profile Integration SOAP Process.

   For ACCOUNT : UCM Organization Customer Profile Integration SOAP Process.

3. Select Workflow Step Transaction Manager and add new input arguments.

4. To specify Business Service Name and Method for hook 1 (before commit), use input argument:

   Name: “CustomBS”, Type: Literal, Value: “UCM Utility Service”
   Name: “CustomMth”, Type: Literal, Value: “PositiveTestBeforeCommit”

5. To specify Business Service Name and Method for hook 2 (after commit), use input argument:

   Name: “CustomBSAfterCommit”, Type: Literal, Value: “UCM Utility Service”
   Name: “CustomMtdAfterCommit”, Type: Literal, Value: “NegativeTestAfterCommit”

6. Add checkpoint and submit workspace for delivery.

7. Deliver repository changes to runtime database.

Note: The Name of the input argument should be exact as above; users should enter their own custom business service and method in the Value.

The diagram below shows a view of real-time SOAP workflow process, when user adds a new input argument for hook 2 (after commit). The value specified in the input arguments overrides the value (if any) specified in UCM Transaction Manager’s Business Service User Prop.

For this example, hook 2 will invoke method NegativeTestAfterCommit instead of PositiveTestAfterCommit as specified in Business Service User Prop: Custom Business Service After Commit.

To enable UCM Transaction Manager’s callback functions only for batch process

1. Create a new workspace to deliver repository changes to runtime database in Siebel Tools.

2. Edit workflow process: UCM Batch Process.

3. Select workflow Step: Execute Propsets and add new input arguments.

4. To specify Business Service Name and Method for hook 1 (before commit), use input argument:

   Name: “CustomBS”, Type: Literal, Value: “UCM Utility Service”
   Name: “CustomMth”, Type: Literal, Value: “PositiveTestBeforeCommit”

5. To specify Business Service Name and Method for hook 2 (after commit), use input argument:

   Name: “CustomBSAfterCommit”, Type: Literal, Value: “UCM Utility Service”
   Name: “CustomMtdAfterCommit”, Type: Literal, Value: “NegativeTestAfterCommit”

6. Add checkpoint and submit workspace for delivery.

7. Deliver repository changes to runtime database.

Note: The Name of the input argument should be exact as above; users should enter their own custom business service and method in the Value.

The diagram below shows a view of UCM Batch Process workflow, when user adds a new input arguments for hook 2 (after commit). The value specified in input arguments overrides the value (if any) specified in UCM Transaction Manager’s Business Service User Prop.

For this example, hook 2 will invoke method NegativeTestAfterCommit instead of PositiveTestAfterCommit as specified in Business Service User Prop: Custom Business Service After Commit.