The CustomerServiceConfiguration_Wireless workflow is one of three WebSphere MQ Workflow processes corresponding to the IBM WebSphere Business Integration Collaboration for Customer Service Configuration and Activation. This WebSphere MQ Workflow process takes a TelcoOrderWL input, and returns a TelcoOrderWL output.
The following diagram shows the process model for the CustomerServiceConfiguration_Wireless workflow:
The CustomerServiceConfiguration_Wireless workflow contains the following activities:
Description: This activity encompasses the processing that is completed by the system in order to create a new subscriber.
Program name: CreateSubscriberHLR
Input: ServiceConfigRecord
Output: ServiceConfigRecord
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Create subscriber Home Location Registry (HLR)
Description: This activity encompasses the processing that is completed by the system in order to create a temporary password for a subscriber.
Program name: CreateTemporaryPassword
Input: ServiceWL
Output: ServiceWL
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Create temporary password
Description: This activity encompasses the actions taken by a customer service representative to notify the subscriber about the progress of a service order.
Program name: NotifyInstructionToSubscriber
Input: ServiceWL
Output: ServiceWL
Start type: Manual
Staff: All people
Program execution server: None
Activity name in use case: Notify customer about temporary password
Description: This activity encompasses the actions taken by a customer service representative to set up a wireless service.
Program name: SetupService_Wireless
Input: TelcoServiceOrderWL
Output: TelcoServiceOrderWL
Start type: Manual
Staff: All people
Program execution server: None
Activity name in use case: Set up service
Description: This activity encompasses the processing that is completed by the system in order to update the status of a sales order.
Program name: UpdateSalesOrderStatus
Input: TelcoSalesOrderWL
Output: TelcoSalesOrderWL
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Update sales order status
The following table shows the program details for the CustomerServiceConfiguration_Wireless workflow.
Name | Input | Output | Invoked program | Command line arguments |
---|---|---|---|---|
CreateSubscriber HLR |
ConfigRecord | ConfigRecord | nevercalled.exe | verb=Create |
CreateTemporary Password |
ServiceWL | ServiceWL | nevercalled.exe | verb=Setup |
NotifyInstruction ToSubscriber |
ServiceWL | ServiceWL | nevercalled.exe | - |
SetupService | TelcoServiceOrderWL | TelcoServiceOrderWL | nevercalled.exe | - |
UpdateSales OrderStatus |
TelcoSalesOrderWL | TelcoSalesOrderWL | nevercalled.exe | verb=UpdateStatus |
Many of the data structures that the CustomerServiceConfiguration_Wireless workflow uses are defined as CrossWorlds generic business objects (GBOs). CustomerServiceConfiguration_Wireless also uses data structures that are related to GBOs, but define different elements from those specified in the GBO. These data structures are listed below (along with the related GBO, in parentheses):
The CustomerServiceConfiguration_WL workflow also uses the following data structures, which are defined only in WebSphere MQ Workflow:
Note: All GBOs contain a ProcessContext child GBO. In WebSphere MQ Workflow processes, this element is absent from all data structures. The data defined by ProcessContext is used for communication between a collaboration object and a WebSphere MQ Workflow connector.
The following table shows the members of the TelcoSalesOrderWL data structure. The members that appear in italic text either have a different data type from the attribute of the same name in the related GBO, or they do not appear in the GBO (TelcoSalesOrder). Members in plain text appear in the GBO as well as in the data structure.
The TelcoSalesOrder GBO has a ContactPerson attribute that does not appear in this data structure. Instead, the data structure uses ContactPersonRef.
Data member name | Data type | Description |
---|---|---|
SalesOrderId | String | |
SalesOrderDate | String | |
CompletionDate | String | |
SalesInfo | String | |
SalesOrderTerms | String | |
Charge | String | |
CustomerRef | PartyRef | |
AccountRef | AccountRef | |
BillingAccountRef | BillingAccountRef | |
CreditApproval | String | |
AgentRef | PartyRef | |
SOLine | SelectedProduct | |
ContactPersonRef | ContactPersonRef | Reference to a ContactPerson |
SOSetup | SalesOrderWireless | The SalesOrderWireless object appears directly as a member of this data structure. In the TelcoSalesOrder GBO this object appears at a lower level of hierarchy. In the GBO, SOSetup has a data type of TelcoSalesOrderForDataService, and the TelcoSalesOrderForDataService GBO contains SalesOrderDSL, SalesOrderIDC and SalesOrderWireless attributes. |
Status | Status |
The following table shows the members of the TelcoServiceOrderWL data structure. The members that appear in italic text either have a different data type from the attribute of the same name in the related GBO, or they do not appear in the GBO (TelcoServiceOrder). Members in plain text appear in the GBO as well as in the data structure.
Data member name | Data type | Description |
---|---|---|
ServiceOrderId | String | |
DueDate | String | |
EndDate | String | |
SubmitterRef | PartyRef | |
Name | String | |
SalesOrderRef | TelcoSalesOrderRef | |
Priority | String | |
RequestedBy | String | |
ServiceOrderDateTime | String | |
AnticipateCompletion Date |
String | |
RequiredResourceRef | ResourceRef | |
ReqService | ServiceWL | The ServiceWL data type is used for this data member. In the TelcoServiceOrder GBO, the data type of the ReqService attribute is the Service GBO. |
Status | Status |
The following table shows the members of the ServiceWL data structure. The members that appear in italic text either have a different data type from the attribute of the same name in the related GBO, or they do not appear in the GBO (Service). Members in plain text appear in the GBO as well as in the data structure.
Data member name | Data type | Description |
---|---|---|
ServiceId | String | |
AccountRef | AccountRef | |
ServiceName | String | |
OfferingId | String | |
DesiredDueDate | String | |
CustomerRef | PartyRef | |
ServiceNotes | TelcoNotes | |
ServiceSetting | ServiceWLSetting | The ServiceWLSetting object appears directly as a member of this data structure. In the Service GBO this object appears at a lower level of hierarchy. In the GBO, SOSetup has a data type of ServiceSetting, and the ServiceSetting GBO contains ServiceDSLSetting, ServiceIDCSetting, and ServiceWirelessSetting attributes. |
Location | ServiceLocationData | |
Status | Status |
The following table shows the member of the ContactPersonRef data structure. This data structure is defined only in WebSphere MQ Workflow, and is used by WebSphere MQ Workflow instead of the ContactPerson GBO.
Data member name | Data type | Description |
---|---|---|
ObjectId | String |
The following table shows the member of the TelcoOrderWL data structure. This data structure is defined only in WebSphere MQ Workflow.
Data member name | Data type | Description |
---|---|---|
TelcoSalesOrderWL | TelcoSalesOrderWL | |
TelcoServiceOrderWL | TelcoServiceOrderWL |
The following table shows the mapping between the data inputs and outputs of activities in this workflow.
Destination activity | Input data structure | Origin activity | Output data structure | Mapping specification |
---|---|---|---|---|
Create SubscriberHLR |
ConfigRecord | Source Node | TelcoOrderWL | ConfigRecord. ConfigRecordWireless. ServiceRef.ServiceId = TelcoOrderWL. TelcoServiceOrderWL. ReqService.ServiceId |
CreateTemporary Password |
ServiceWL | Source Node | TelcoOrderWL | ServiceWL = TelcoOrderWL. TelcoServiceOrderWL. ReqService |
NotifyInstruction ToSubscriber |
ServiceWL | CreateTemporary Password |
ServiceWL | ServiceWL = ServiceWL |
SetupService_ Wireless |
TelcoService OrderWL |
Source Node | TelcoOrderWL | TelcoServiceOrderWL = TelcoOrderWL. TelcoServiceOrderWL |
NotifyInstruction ToSubscriber |
ServiceWL | TelcoServiceOrderWL. ReqService = ServiceWL |
||
UpdateSales OrderStatus |
TelcoSales OrderWL |
Source Node | TelcoOrderWL | TelcoSalesOrderWL. SalesOrderId = TelcoOrderWL. TelcoSalesOrderWL. SalesOrderId TelcoSalesOrderWL. Status.State = "Installed" |
Activities in the CustomerServiceConfiguration_Wireless workflow may invoke collaboration objects for application/information integration. The following table shows the collaboration objects that may be invoked by this workflow's activities.
Activity | Collaboration object | Generic business object | Verb |
---|---|---|---|
Create SubscriberHLR |
ConfigRecord Manager |
ConfigRecord | Create |
CreateTemporary Password |
Wireless ServiceSetup |
Service | Setup (From) ReturnSetupResult (Return) |
UpdateSales OrderStatus |
SalesOrder Manager |
TelcoSales Order |
UpdateStatus |