...
Accessory details - The option for accessory are retrieved from MDMS, according to the option selected Unit of measure gets pre-populated, which is non editable by user, rest UOM value and accessory count user can edit or gets pre-populated from MDMS, for adding multiple accessory Add More Trade Accessory button can be clicked, it will be as similar as trade units.
...
CommonPT integration with TL :
After entering the details of the Trade, user will have an option to either search and integrate the already created property or create a new lightweight property for the trade license, or can skip this step altogether and proceed with normal address details flow.
Once property is selected user can see the details of the property throught property details page, for in-depth knowledge about the flow, please refer to Common PT
...
Address Details Flow:
After entering about the details about the Trade user will need to enter about the address of the Trade, where it is located. The flow will be straight forward, without any conditional routing.
...
Throughout the flow, few of the pages data are being imported from MDMS, Following are the list of pages which are using MDMS data, These pages .js files can be found under page components.
PageComponent | MDMS Detail | Module Details Name | Master Detail Name |
---|---|---|---|
TradeLicense | List of documents required for registration |
|
|
SelectTradeName | Current Financial Year |
|
|
SelectVehicleType | Type of mobility trade |
|
|
SelectBuildingType | Type of Steady Trade |
|
|
SelectTradeUnits | List of trade category and its corresponding type and sub-type |
|
|
SelectAccessoriesDetails | Lit of Accessory and its Unit of measure and UOM value |
|
|
TLSelectAddress | List of cities and its corresponding localities |
|
|
SelectOwnerShipDetails | categories imported are single and multiple owner. |
|
|
SelectOwnerDetails | List of Gender options. |
|
|
For calling of MDMS data React Hooks has been used, so that it could be shared throughout the modules. Below is the little code snippet for the call used for MDMS.
...
API Call Role Action mapping:
S.No. | API | Action id | Roles |
---|---|---|---|
1 |
|
|
|
2 |
|
|
|
3 |
|
|
|
4 |
|
|
|
5 |
|
|
|
6 |
|
|
|
7 |
|
|
|