The ProductDevelopmentAndRetirement workflow is the WebSphere MQ Workflow process that corresponds to the IBM WebSphere Business Integration Collaboration for Product Development and Retirement. This workflow takes an input of Default Data Structure, and returns a TelcoProduct output.
The following diagram shows the process model for the ProductDevelopmentAndRetirement workflow:
The ProductDevelopmentAndRetirement workflow contains the following activities:
Description: This activity encompasses the actions taken by a customer service representative to select a product from a list.
The following diagram shows the path that a customer service representative may follow when completing the SelectProductData activity:
Program name: SelectProductData
Input: Default Data Structure
Output: TelcoProduct
Start type: Manual
Staff: All people
Program execution server: None
Activity names in use case: Enter item search criteria, Find and retrieve items
Description: This activity encompasses the actions taken by a customer service representative to enter information about a product.
Program name: InputProductData
Input: Default Data Structure
Output: TelcoProduct
Start type: Manual
Staff: All people
Program execution server: None
Activity name in use case: Enter item data
Description: This activity encompasses the processing that is completed by the system in order to add a new product.
Program name: AddProduct
Input: TelcoProduct
Output: TelcoProduct
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Add item to product catalog
Description: This activity encompasses the actions taken by a customer service representative to specify the status of a product.
Program name: SetProductStatus
Input: TelcoProduct
Output: TelcoProduct
Start type: Manual
Staff: All people
Program execution server: None
Activity name in use case: Set item status
Description: This activity encompasses the processing that is completed by the system in order to modify the status of a product.
Program name: UpdateProductStatus
Input: TelcoProduct
Output: TelcoProduct
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Record item detail
Description: This activity encompasses the actions taken by a customer service representative to validate or change information about a product.
Program name: ValidateAndModifyProduct
Input: TelcoProduct
Output: TelcoProductAndResult
Start type: Manual
Staff: All people
Program execution server: None
Activity name in use case: Verify item data, Modify item data
Description: This activity encompasses the processing that is completed by the system in order to update product information.
Program name: UpdateProduct
Input: TelcoProduct
Output: TelcoProduct
Start type: Automatic
Staff: Process starter
Program execution server: InterChange Server
Activity name in use case: Update item
The following table shows the program details for the ProductDevelopmentAndRetirement workflow.
Name | Input | Output | Invoked program | Command line arguments |
---|---|---|---|---|
SelectProductData | Default Data Structure | TelcoProduct | nevercalled.exe | None |
InputProductData | Default Data Structure | TelcoProduct | nevercalled.exe | None |
AddProduct | TelcoProduct | TelcoProduct | nevercalled.exe | verb=Create |
SetProductStatus | TelcoProduct | TelcoProduct | nevercalled.exe | None |
UpdateProduct Status |
TelcoProduct | TelcoProduct | nevercalled.exe | verb=UpdateStatus |
ValidateAnd ModifyProduct |
TelcoProduct | TelcoProduct AndResult |
nevercalled.exe | None |
UpdateProduct | TelcoProduct | TelcoProduct | nevercalled.exe | verb=Update |
Most of the data structures that the ProductDevelopmentAndRetirement workflow uses are defined as CrossWorlds generic business objects (GBOs). The ProductDevelopmentAndRetirement workflow also uses TelcoProductAndResult, which is shown in the following table:
Data member name | Data type | Description |
---|---|---|
TelcoProduct | TelcoProduct | |
ResultOfValidation | 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 |
---|---|---|---|---|
SelectProduct Data |
Default Data Structure | - | ||
InputProduct Data |
Default Data Structure | - | ||
AddProduct | TelcoProduct | InputProduct Data |
TelcoProduct | TelcoProduct = TelcoProduct |
ModifyProduct Status |
TelcoProduct | AddProduct | TelcoProduct | TelcoProduct = TelcoProduct |
UpdateProduct | TelcoProduct | TelcoProduct = TelcoProduct | ||
ValidateAnd ModifyProduct |
TelcoProduct AndResult |
TelcoProductAndResult. TelcoProduct = TelcoProduct |
||
UpdateProduct Status |
TelcoProduct | ModifyProduct Status |
TelcoProduct | TelcoProduct = TelcoProduct |
ValidateAnd ModifyProduct |
TelcoProduct | SelectProduct Data |
TelcoProduct | TelcoProduct = TelcoProduct |
UpdateProduct | TelcoProduct | ValidateAnd ModifyProduct |
TelcoProduct AndResult |
TelcoProductAndResult. TelcoProduct = TelcoProduct |
Activities in the ProductDevelopmentAndRetirement 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 |
---|---|---|---|
AddProduct | TelcoProductManager | TelcoProduct | Create |
UpdateProductStatus | TelcoProductManager | TelcoProduct | UpdateStatus |
UpdateProduct | TelcoProductManager | TelcoProduct | Update |