...
It supports PSPCL event flow. It collects events from fiscal event(PSPCL) service and pushes it to mGramSeva service.
This process triggered by cron job has a configurable Qurtz Quartz time interval. It does not depend on the external scheduler. Time interval depends on what time is being passed in the quartz interval.
Fiscal event search time interval should be greater than quartz time interval. e.g. if the quartz interval is every 6 hours then the event search time interval could be 7 hours. Fiscal event search time interval - time unit is Minute- This depends on Quartz cron expression. It add some extra overlap time to the cron time interval. Overlap time addition is configurable and it’s time unit minute - we can only provide time in minute. Right now it has not been added to the helm chart - it is being set in properties file - ifix.fiscal.event.search.time.overlap.minutes.
When quartz triggers its scheduler, it starts by collecting PSPCL events from fiscal event service (iFix Core).
It calls the fiscal event search API and It passes tenantId, event type, receiver name and time interval. It does not collect all events(PSPCL) at once. It collects chunks of events based on time intervals, which has been mentioned above. Events from the fiscal event are not compatible with mGramSeva events. Events can have two types Demand and Receipt, it does different calculation or conversion based on event type.
Demand event type
When it finds event type is demand, it tries to create challan in challan service through create challan API. To create challan, we require a few attributes i.e. tenantId, business service, consumer type, vendor details, amount details, referenceId, bill date and time period. Here are two major attributes that require calculation.
First one is vendor id - to get the vendor id we have to call a third party(Vendor service). Vendor search API mainly depends (in our scenario) on tenantId and it’s name - it gives us a list of vendors for particular tenantId. We take the first one from the list and attach it to the "Create Challan API" attribute. If it does not find any tenant detail. It will create new one with tenant id and configured tenant name.
Second one is reference id - It is actually a PSPCL account number which is coming through the fiscal event search API, it is tagged in an additional attribute of event. This plays a main role in the overall process. It works as a tracker for payment and bill.
...
Environment Variables | Description |
| It collect only those event from ifix service which matches to this receiver value. |
| It searches events from iFix service based on this time interval. |
| mGramSeva OAuth token username. |
| mGramSeva OAuth token password. |
| mGramSeva OAuth token scope. |
| mGramSeva OAuth token grant type. |
| mGramSeva OAuth token tenant id. |
| mGramSeva OAuth token user type. |
| It is a quartz job time interval value. |
| It has two values “Never” or “Always” for Quartz table creation. Never - It wont create any table Always - It will create table every time when service deploy and erase every existing details. (Not recommended).
|
| Host name of mGramSeva |
Related Page
PSPCL Adaptor v1.0 Release notes