The CustomerServiceConfiguration_DSL workflow is one of three WebSphere MQ Workflow processes corresponding to the IBM WebSphere Business Integration Collaboration for Customer Service Configuration and Activation. This workflow takes a TelcoOrderDSL input, and returns a TelcoOrderDSL output.
The following diagram shows the process model for the CustomerServiceConfiguration_DSL workflow:
The CustomerServiceConfiguration_DSL workflow contains the following activities:
Description: This activity encompasses the actions taken by a service agent to release a configuration request.
Program name: ReleaseRequest
Input: TelcoServiceOrderDSL
Output: Default data structure
Start type: Manual
Staff: All people
Program execution server: None
Activity name in use case: Release request
Description: This activity encompasses the processing that is completed by the system in order to send a configuration request to a service provider.
Program name: InitiateConfigRequestToProvider
Input: TelcoServiceOrderDSL
Output: FOC
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Initiate configuration requests to provider
Description: This activity encompasses the processing that is completed by the system in order to add a new customer configuration record.
Program name: AddCustomerConfigRecord
Input: FOC
Output: ConfigRecord
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Add customer's configuration record
Description: This activity encompasses the processing that is completed by the system in order to test a service configuration. This activity is included in the TestConfiguration block activity, along with FixConfiguration.
Program name: ExecuteTest
Input: ConfigRecordDSL
Output: TestResult
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Test service configuration
Description: This activity encompasses the processing that is completed by the system in order to fix a service configuration. This activity is included in the TestConfiguration block activity, along with ExecuteTest.
Program name: FixConfiguration
Input: ConfigRecordDSLAndTestResult
Output: ConfigRecordDSL
Start type: Manual
Staff: Process starter
Program execution server: None
Activity name in use case: Test service configuration
Description: This activity encompasses the processing that is completed by the system in order to set up a new service.
Program name: SetupService_DSL
Input: ConfigRecordDSL
Output: ConfigRecordDSL
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Set up service
Description: This activity encompasses the actions taken by a service agent to configure customer premise equipment.
Program name: ConfigureCPE
Input: TelcoServiceOrderDSL
Output: TelcoServiceOrderDSL
Start type: Manual
Staff: All people
Program execution server: None
Activity name in use case: Configure Customer Premise Equipment (CPE)
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: TelcoSalesOrderDSL
Output: TelcoSalesOrderDSL
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Update sales order status
Description: This activity encompasses the processing that is completed by the system in order to update the status of a service order.
Program name: UpdateServiceOrderStatus
Input: TelcoServiceOrderDSL
Output: TelcoServiceOrderDSL
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Update service order status
The following table shows the details of CustomerServiceConfiguration_DSL's block activity.
Included activities | Input | Output | Exit condition |
---|---|---|---|
ExecuteTest, FixConfiguration | ConfigRecordDSL | ConfigRecordDSL AndTestResult |
TestResult.Result = true AND TestResult.CompletionStatus = Success |
The following table shows the details of CustomerServiceConfiguration_DSL's single process activity, CustomerResourceProvisioning.
Input | Output | Auto / Manual [A/M] | Staff |
---|---|---|---|
TelcoServiceOrderAndConfigRecDSL | TelcoServiceOrderAndConfigRecDSL | A | Process starter |
The following table shows the program details for the CustomerServiceConfiguration_DSL workflow.
Name | Input | Output | Invoked program | Command line arguments |
---|---|---|---|---|
ReleaseRequest | TelcoService OrderDSL |
Default Data Structure | nevercalled. exe |
- |
InitiateConfig Request ToProvider |
TelcoService OrderDSL |
FOC | nevercalled. exe |
verb=Initiate Request |
AddCustomer Config Record |
FOC | ConfigRecord | nevercalled. exe |
verb=Create |
ExecuteTest | ConfigRecord DSL |
TestResult | nevercalled. exe |
verb=Test |
FixConfiguration | ConfigRecord DSL AndTestResult |
ConfigRecordDSL | nevercalled. exe |
- |
SetupService_DSL | ConfigRecord DSL |
ConfigRecordDSL | nevercalled. exe |
verb=Setup |
ConfigureCPE | TelcoService OrderDSL |
TelcoService OrderDSL |
nevercalled.exe | - |
UpdateService OrderStatus |
TelcoService OrderDSL |
TelcoService OrderDSL |
nevercalled. exe |
verb=Update Status |
Many of the data structures that the CustomerServiceConfiguration_DSL workflow uses are defined as CrossWorlds generic business objects (GBOs). CustomerServiceConfiguration_DSL 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_IDC 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 TelcoSalesOrderDSL 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 | SalesOrderDSL | The SalesOrderDSL 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 TelcoServiceOrderDSL 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 | ServiceDSL | The ServiceDSL 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 ServiceDSL 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 | ServiceDSLSetting | The ServiceDSLSetting 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 TelcoOrderDSL data structure. This data structure is defined only in WebSphere MQ Workflow.
Data member name | Data type | Description |
---|---|---|
TelcoSalesOrderDSL | TelcoSalesOrderDSL | |
TelcoServiceOrderDSL | TelcoServiceOrderDSL |
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 |
---|---|---|---|---|
ReleaseRequest | TelcoService OrderDSL |
SourceNode | TelcoService OrderDSL |
TelcoServiceOrderDSL = TelcoOrderDSL. TelcoServiceOrderDSL |
InitiateConfig RequestTo Provider |
TelcoService OrderDSL |
Source Node | TelcoOrderDSL | TelcoServiceOrderDSL = |
AddCustomer ConfigRecord |
FOC | InitiateConfig |
FOC | FOC = FOC |
Test Configuration |
ConfigRecord DSL |
AddCustomer ConfigRecord |
ConfigRecord | ConfigRecordDSL = |
Test Configuration |
ConfigRecord DSL |
(Data Loop Connector) ConfigRecordDSL =
ConfigRecordDSL |
||
Test Configuration |
ConfigRecordDSL AndTestResult |
(Data Default Connector) ConfigRecordDSL AndTestResult. ConfigRecordDSL = ConfigRecordDSL |
||
Test Configuration. ExecuteTest |
ConfigRecord DSL |
Source Node (Block activity) |
ConfigRecordDSL | ConfigRecordDSL = ConfigRecordDSL |
Test Configuration. FixConfiguration |
ConfigRecord DSL AndTestResult |
Source Node (Block activity) |
ConfigRecordDSL | ConfigRecord DSLAndTest Result. ConfigRecordDSL = ConfigRecordDSL |
Test Configuration |
TestResult | ConfigRecordDSL AndTestResult. TestResult = TestResult |
||
Sink Node (Block Activity) |
ConfigRecord DSLAndTest Result |
Test Configuration. ExecuteTest |
TestResult | ConfigRecordDSL AndTestResult. TestResult = TestResult |
Test Configuration. Fix Configuration |
ConfigRecordDSL AndTestResult |
ConfigRecordDSL AndTestResult. ConfigRecordDSL = ConfigRecordDSL AndTestResult. ConfigRecordDSL |
||
SetupService_ DSL |
ConfigRecord DSL |
Test Configuration |
ConfigRecord DSL |
ConfigRecordDSL = |
ConfigureCPE | TelcoService OrderDSL |
Source Node | TelcoOrderDSL | TelcoServiceOrderDSL = |
Customer |
TelcoService |
SetupService_ DSL |
ConfigRecordDSL | TelcoServiceOrderAnd |
ConfigureCPE | TelcoService OrderDSL |
TelcoServiceOrderAnd |
||
UpdateService OrderStatus |
TelcoService OrderDSL |
Source Node |
TelcoOrderDSL | TelcoServiceOrderDSL. ServiceOrderId = TelcoOrderDSL. TelcoServiceOrderDSL. ServiceOrderId TelcoServiceOrderDSL. Status.State = "Installed" |
UpdateSales OrderStatus |
TelcoSales OrderDSL |
Source Node |
TelcoOrderDSL | TelcoSalesOrderDSL. |
Activities in the TelcoServiceOrderDSL 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 |
---|---|---|---|
InitiateConfig RequestToProvider |
LoopServiceRequest Initiator (From) ServiceRequest Responder(Return) |
LSLSR (From) FOC (Return) |
InitiateRequest (From) Create (Return) |
AddCustomer ConfigRecord |
DesignManager (From) CompleteDesign (Return) |
FOC (From) ConfigRecord (Return) |
Create |
TestConfiguration.ExecuteTest | TestDSLService Processing (From) ReturnTestResult (Return) |
ConfigRecordDSL (From) TestResult (Return) |
Test (From) Create (Return) |
SetupService | DSLServiceSetup | ConfigRecordDSL | Setup (From) ReturnSetupResult (Return) |
UpdateService OrderStatus |
ServiceOrderManager | TelcoServiceOrder | UpdateStatus |
UpdateSales OrderStatus |
SalesOrderManager | TelcoSalesOrder | UpdateStatus |
AddProduct | TelcoProductManager | TelcoProduct | Create |
UpdateProduct Status |
TelcoProductManager | TelcoProduct | UpdateStatus |
UpdateProduct | TelcoProductManager | TelcoProduct | Update |