P&C Endorsement Workflow

P&C => Property and casualty, Is basically an insurance policy feature available in tawuniya
insurance, which can be saved and updated by brokers and policy holders.

What we have done so far ( Current Flow )

1 - We have created a web portal for brokers to be able to see the policy details and to be able
to update the policy details, updated details are sent through an endorsement request to the
backend.

2 - We have used Webmethods IS for rest API which is being used by the web portal

3 - The Stored procedures are used in webmethods for data flow.

What we need to do (Proposed New flow)
1 - Broker Submits Endorsement request from web portal
2 - Check if the policy is valid.
3 - if yes, Endorsement is saved in the DB
4 - if no, exception is thrown.
5 - Task ID is generated
6 - Endorsement number is generated which will be later required for payment
7 - Underwriter will see the task and start action on it
8 - Workflow should check UW approval status
9 - If it is pending, UW will check the endorsement request through the task dashboard
10 - UW, if it sees all good, will approve the endorsement.
11 - Status is updated in DB
12 - Workflow checks if the payment is required or not, if not then payment status is
updated in db and endorsement is finalized.
13 - if payment is required, Broker sees approved status and moves for sadad payment
on web portal, upon completion status is updated in db and endorsement is finalized.
14 - If UW rejects, UW uploads a document or draft and rejects it.
15 - UW status is updated in db
16 - Broker sees the endorsement update request status is rejected
17 - Broker, clarifies everything and uploads required documents, and re-submits
endorsement.
18 - Task ID gets updated
19 - Step 4 to 10 is repeated.
20 - We need to create a dashboard where the UW will see all the tasks for P&C listed so
that actions can be performed the same as other lines of businesses.

NOTE:

- From step 5 to 18, Workflow will be triggered in the endorsement update request.

- Only Endorsement updates from frontend will be done through the rest API which will
eventually trigger the workflow.

- Workflow will require soap APIs to be created and SPs needs to be integrated in the IS.

- We will create a new table for the endorsements to be saved, all other updates will be
done through the workflow, SPs will be created for this.

- Underwriters will be created from the Webmethods BPM Panel from users tabs.