Add Module MDMS (Master Data Management Service) Configuration

When creating a Contracts module, the module needs to be enabled in citymodule.json.Add the Following details in citymodule.json

{
    "tenantId": "pb",
    "moduleName": "tenant",
    "citymodule": [
        {
            "module": "Contracts",
            "code": "Contracts",
            "active": true,
            "order": 1,
            "tenants": [
                {
                    "code": "pb.jalandhar"
                },
                {
                    "code": "pb.nawanshahr"
                },
                {
                    "code": "pb.amritsar"
                }
            ]
        }
}

1. Contracts will be created by contract_creator, Checked by contract_checker and approver by contract_approver. This will be linear workflow and rejected contracts at any point in lifecycle will come into inbox of creator.

2. Contracts counters on Home Screen will increase/decrease as the inbox items for checkers and approvers increase/decrease respectively.

3. Actions menu on view page of Work orders should have actions to be taken by respective Actors

4. For Work Orders (Non-Departmental)

   1. WO is created by JE, Approved by ME. Checkers in between depends on Implementation and can vary from ULB to ULB

   2. Approved WO goes into Work Order inbox of respective organisation.

   3. Organisation can either accept or reject.

   4. Rejected Work Orders will come back into inbox of creator and cycle repeats

5. For Work Orders (Departmental)

   1. WO is created by JE, Approved by ME. Checkers in between depends on Implementation and can vary from ULB to ULB

   2. Approved WO goes into Work Order inbox of respective organisation.

   3. Organisation can either accept or reject.

   4. Rejected Work Orders will come back into inbox of creator and cycle repeats

6. For Purchase Orders

   1. PO is created by JE, Approved by ME. Checkers in between depends on Implementation and can vary from ULB to ULB. An Infra expert can be assigned to check PO.

   2. Approved PO goes as SMS to registered Vendor

   3. Vendor can click on the PO link & download approved PO’s PDF.

Once the Estimate are created they will move to the respective checker and approver's inbox as pending items.

View Contract

• From Contract Proposal Inbox, User can come into Contract View Screen where Details of Contract present while creating the contract and Workflow history will be displayed.

• User can take necessary actions by clicking on Actions Menu.

Taking Actions on Contract

An Action bar on the View Contract Screen shows the list of actions

1. Forward Contract

2. Reject Contract

3. Modify Contract

4. Approve Contract

When any action is clicked respective popup is rendered according to the selected action. We have created three popups for approve, forward and reject. They are shown below

When these popups are submitted, Update Contract API is called containing the relevant updates in the workflow object contained in the request body. The contract service internally calls the workflow service and updates the status of the application.

Response Screen

Upon successful update, a response screen is displayed as follows

Create Contract will have link to create contract from view approved estimate sub Estimate table screen.

Clicking on this will open create contract screen.

Add create contract fields mdms config

Add the following MDMS config to fetch the values of different dropdown filed of create estimate

MDMS config for Depatment, Designation
{
    tenant,   //pb
    "common-masters",
        [
            {
                "name": "Department"
            },
            {
                "name": "Designation"
            }
        ]
}

Once the above details are filled, user needs to forward contract to concerned department and official for checking. Forwarding is considered as part of contract creation.Fill in the details and click “Forward and Approve”.

Once Create Contract API call is successful, an acknowledgement screen is shown.

DropDown Data and Localization

Some of the dropdown data is fetched from mdms and hrms search API

Localization keys are added under the ‘rainmaker-works’ locale module. In future if any new labels are implemented in works module that should also be pushed in the locale DB under rainmaker-works locale module. Below is the example of few locale labels for hindi and English.

{
    "code":"WORKS_CREATE_CONTRACT",
    "message":"एक अनुबंध बनाएं",
    "module":"rainmaker-works",
    "locale":"hi_IN"
}

{
    "code":"WORKS_CREATE_CONTRACT",
    "message":"Create a Contract",
    "module":"rainmaker-works",
    "locale":"en_IN"
}

1. Rejected Contracts will show up in contract creators inbox.

2. Clicking on it will take to contract view screen. Users Click on “Actions” to make changes to contract.

3. Contract Details, ID, Contract Type and Project Details wont be editable.

4. Financial Details, Agreement Details are editable.

5. Creator Can make these changes and proceed to forward to checker.

Clicking on Rejected Contract ID from inbox will open Contract view page.

Clicking Actions-> Modify Contract will make page editable

From here on the flow is same as that of Create Contract. Once this Contract is submitted it is again moved to the respective Checker's inbox for approval. Contract can be rejected any number of times due to any specific reason which can be mentioned in the comments and the same comments are reflected in the View Contract screen.

Upon Successful update relevant acknowledgement screen displayed.

A contract that is approved and sent to next stage wont be editable.