The NotifyProblemStatus collaboration template is used to handle notifications of problem status in the telecommunications (telco) industry.
NotifyProblemStatus uses the Generic Notification business object to represent a problem status notification.
This collaboration template uses the ProcessContext attribute of generic business objects to maintain process information between two or more collaboration objects. In order to maintain this information, the collaboration object performs the following actions, starting from when it receives a triggering business object:
This section includes information on port bindings and required steps for setting up collaboration objects based on this collaboration template. For information on standard features, ports, and configuration properties for collaboration templates, and for general information on creating collaboration objects refer to the documents listed in Required documents for creating collaboration objects.
The following diagram illustrates the ports of NotifyProblemStatus:
Note: To keep the collaboration object from using a port, bind that port to the Port connector. Doing so indicates that the port is unused without causing the collaboration object to provide additional functionality.
Business object | Bound to | Function | Verbs used |
---|---|---|---|
ProblemRecord | CRM system |
Receives the triggering business object. | Update |
Business object | Bound to | Function | Verbs used |
---|---|---|---|
Notification | Intelligent notification server |
Sends the triggering business object out of the collaboration object | Create |
Business object | Bound to | Function | Verbs used |
---|---|---|---|
TroubleTicket | CRM system |
Sends a reference-valued business object to retrieve the
full-valued business object. Note: This port is only used when the triggering business object has a TroubleTicketId |
Retrieve |
Business object | Bound to | Function | Verbs used |
---|---|---|---|
ProblemRecord | CRM system | Retrieves the source data from the master
application. When the collaboration object is used in a sync mode, where it receives only the key information from the From port, retrieves the source data from the master application, and synchronizes that data with other applications. Note: Since this port is closely related to SYNC_FROM_SOURCE property, see the SYNC_FROM_SOURCE property. |
Retrieve |
To set up NotifyProblemStatus as a stand-alone collaboration object, complete the following steps:
This section illustrates the following business processes for this collaboration template:
This section illustrates NotifyProblemStatus's process logic for its supported verbs indicated below, as well as additional process logic that will be executed if the SYNC_FROM_SOURCE configuration property is set to true:
The following diagram shows the process logic for this collaboration template's Create, Delete, and Update verbs.
In the Create Notification action, the collaboration object performs the following processes:
Iif you want to change the logic for creating the notification message, use the Process Designer to open the NotifyProblemStatus collaboration template, and then complete the following steps:
The following diagram shows the additional process logic that is executed when the collaboration object's SYNC_FROM_SOURCE configuration property is set to true.
This collaboration template uses the following standard business processes:
IBM WebSphere InterChange Server provides the ability to roll back a transaction upon the failure of any step in the transaction. For example, when this collaboration object is a member of a collaboration object group, its process is one subtransactional step in a larger process. If any step fails in the collaboration object group's processes, IBM WebSphere Business InterChange Server allows you to roll back the processing of every collaboration object in the group.
When this collaboration object is used independently of other collaboration objects, its process comprises a single transactional step. In such a situation, it is not necessary to perform a rollback.
To cause a collaboration object or a collaboration object group to perform rollback requires modifying the collaboration template. To understand transaction processing by IBM WebSphere InterChange Server, see the Technical Introduction to IBM WebSphere InterChange Server. For information on adding transaction processing to the collaboration template, see the Collaboration Development Guide.
To extend the collaboration object to handle transaction processing, complete the following steps:
This section describes the following properties for this collaboration template:
This collaboration template uses the following standard configuration properties:
In addition to its standard configuration properties, this collaboration template has the SYNC_FROM_SOURCE configuration property.
This property specifies whether to retrieve the source data from the master application through the SourceApp port before sending the data to another application. When the triggering business object has only the key information, this property should be set to true.
Possible values | Usage |
---|---|
true | Causes this collaboration object to retrieve the full-value business object and use it as triggering business object. |
false (default value) | Causes this collaboration object to use the triggering business object directly. In this case, the SourceApp port is bound to the Port connector. |