This example uses a very simplified claims processing activity to illustrate inheritance in derived workflows.
This example business handles three different types of insurance claims—Auto, Aircraft, and Boat. Processing tasks for these claims have many similarities, but there are differences that make it desirable to use a separate workflow for each type of claim. Therefore, we have a base workflow that contains tasks shared by all processes, and we will create three specialized workflows—one for each type of claim—that contain the shared processes inherited from the base workflow.
ClaimsBase workflowThe ClaimsBase workflow contains submaps for two basic tasks used for all claims processing: Evaluate policy, and Print letter. It will be the base workflow for the three new workflows designed to process the specific types of claims. Note that the workflow (main) map is not important in this base workflow definition—it will be overwritten in each derived workflow definition.
|
BoatClaims workflowThe BoatClaims workflow is based on the ClaimsBase workflow, so it includes read-only submaps EvaluatePolicy and PrintLetter.
|