The CustomerResourceProvisioning workflow is the WebSphere MQ Workflow process corresponding to the IBM WebSphere Business Integration Collaboration for Resource Provisioning and Allocation. This WebSphere MQ Workflow process takes a TelcoServiceOrderDSLAndConfigRecordDSL input, and returns a TelcoServiceOrderDSLAndConfigRecordDSL output.
The following diagram shows the process model for CustomerResourceProvisioning:
The CustomerResourceProvisioning process contains the following activities:
Description: This activity encompasses the actions taken by a service agent to request equipment for a customer
Program name: RequisitionCustomerEquipment
Input: TelcoServiceOrderDSL
Output: TelcoServiceOrderDSL
Start type: Manual
Staff: All people
Program execution server: None
Activity name in use case: Requisition customer equipment
Description: This activity encompasses the actions taken by a service agent to schedule field work for a customer.
Program name: ScheduleFieldWork
Input: TelcoServiceOrderDSL
Output: FieldServiceElement
Start type: Manual
Staff: All people
Program execution server: None
Activity name in use case: Schedule field work
Description: This activity encompasses the actions taken by a service agent to perform field work.
Program name: PerformFieldWork
Input: FieldServiceElement
Output: FieldServiceElement
Start type: Manual
Staff: All people
Program execution server: None
Activity name in use case: Perform field work
Description: This activity encompasses the processing that is completed by the system in order to update the status of field work.
Program name: UpdateFieldWorkStatus
Input: FieldServiceElement
Output: FieldServiceElement
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Update field work status
Description: This activity encompasses the actions taken by a service agent to enter a customer configuration record
Program name: InputCustomerConfigRecord
Input: ConfigRecordDSL
Output: ConfigRecordDSL
Start type: Manual
Staff: All people
Program execution server: None
Activity name in use case: Enter customer configuration record
Description: This activity encompasses the processing that is completed by the system in order to update a customer's configuration record.
Program name: UpdateCustomerConfigRecord
Input: ConfigRecord
Output: ConfigRecord
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Update customer configuration record
The following table shows the program details for the CustomerResourceProvisioning process.
Name | Input | Output | Invoked program | Command line arguments |
---|---|---|---|---|
RequisitionCustomer Equipment |
TelcoServiceOrderDSL | TelcoServiceOrderDSL | nevercalled.exe | - |
ScheduleFieldWork | TelcoServiceOrderDSL | FieldServiceElement | nevercalled.exe | - |
PerformFieldWork | FieldServiceElement | FieldServiceElement | nevercalled.exe | - |
UpdateFieldWork Status |
FieldServiceElement | FieldServiceElement | nevercalled.exe | verb=UpdateStatus |
InputCustomerConfig Record |
ConfigRecordDSL | ConfigRecordDSL | nevercalled.exe | - |
UpdateCustomer ConfigRecord |
ConfigRecord | ConfigRecord | nevercalled.exe | verb=Update |
Many of the data structures that the CustomerResourceProvisioning workflow uses are defined as generic business objects (GBOs). CustomerResourceProvisioning 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 CustomerResourceProvisioning workflow also uses the ContactPersonRef data structure, which is 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 | |
AnticipateCompletionDate | 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 mapping between the data inputs and outputs of activities in this workflow.
Destination activity | Input data structure | Origin activity | Output data structure | Mapping specification |
---|---|---|---|---|
Requisition Customer Equipment |
TelcoService OrderDSL |
Source Node |
TelcoService |
TelcoServiceOrderDSL = |
Schedule FieldWork |
TelcoService OrderDSL |
Requisition Customer Equipment |
TelcoService OrderDSL |
TelcoServiceOrderDSL = TelcoServiceOrderDSL |
Perform FieldWork |
FieldService Element |
Schedule FieldWork |
FieldService Element |
FieldServiceElement = |
Update FieldWork Status |
FieldService Element |
Perform FieldWork |
FieldService Element |
FieldServiceElement = |
InputCustomer ConfigRecord |
ConfigRecord DSL |
Source Node |
TelcoService |
ConfigRecordDSL = |
Update Customer ConfigRecord |
ConfigRecord | InputCustomer ConfigRecord |
ConfigRecord DSL |
ConfigRecord. |
Activities in the CustomerResourceProvisioning 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 |
---|---|---|---|
UpdateFieldWorkStatus | FieldServiceElementManager | FieldServiceElement | UpdateStatus |
UpdateCustomerConfigRecord | ConfigRecordManager | ConfigRecord | Update |