...
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.
...
TL Enhanced Flow :
If the citizen selects Movable as the structure type in the previous screens, then the flow will jump to owner details flow, in which “Same as Property Owner’s” check box will not be visible.
If the citizen selects Immovable as the structure type then user is allowed to add the property details, Once property is added, the flow will redirect to owner details flow, where “Same as Property Owner’s” check box is added, if user checked it, then following details will get auto populated and screen will skip to proof of Identity page.
CommonPT integration with TL :
...
On clicking on the Download Acknowledgement Form, A PDF will be downloaded.
...
Release 2.8 Enhancements & Changes:
In the Trade Units page, values for trade type and trade subtype has been loaded by the following MDMS call :
| Code Block |
|---|
const { isLoading, data: Data = {} } = Digit.Hooks.tl.useTradeLicenseMDMS(stateId, "TradeLicense", "TradeUnits", "[?(@.type=='TL')]"); |
Following Validation has been added for the same :
Users when select trade type and then subtype, it compared with the available billing slab for which the hook has been mentioned below, and if the billing slab is not there it wont allow users to move forward and error will get displayed.
| Code Block |
|---|
const { data: billingSlabTradeTypeData, isLoading : isBillingSlabLoading } = Digit.Hooks.tl.useTradeLicenseBillingslab({ tenantId: tenantId, filters: {} }, {
select: (data) => {
return data?.billingSlab.filter((e) => e.tradeType && e.applicationType === "NEW" && e.licenseType === "PERMANENT" && e.uom);
}}); |
...
once the right trade type and subtype is added, and correct billing slab is there, then for the UOM value validation is added, it will check the value in the given range, mentioned in the billing slab object and displays the error if the value is outside of the range.
...
Technical Implementation Details:
...
The link for the Apply Trade License Main Index is given below, it can be used to understand the starting point of the flow:
https://github.com/egovernments/digit/DIGIT-Dev/blob/master/frontend/micro-ui/web/micro-ui-internals/blob/main/packages/modules/tl/src/pages/citizen/Create/index.js
TL (Trade License) Module has been segregated into a specified structure, All the screen configuration is inside PageComponent Folder, and the configuration for routing of the pages are mentioned under config folder which is common for both Citizen as well as Employee. Below is the snippet for folder structure and routing configuration.
...
After completing the flow the user can download the acknowledgement PDF form of the License created and the config for the PDF generation can be found in the link given below:
https://github.com/egovernments/digit/DIGIT-Dev/blob/master/frontend/micro-ui/web/micro-ui-internals/blob/main/packages/modules/tl/src/utils/getTLAcknowledgementData.js
Utils Folder basically contains all the methods which are being used throughout the TL module, and if any common method needs to be declared here, which in turn can be imported in other files.
...