Batches
This extension is delivered with a number of batches that need to be scheduled for the environments synchronisation to occur.
The Eftsure parameters form contains a tab dedicated to the configuration of Eftsure batches. Configure this section to influence batches, logs...
This section needs to be configured before generating batches.
We recommend using a dedicated service account to run D365 batches (never expire, never resign).
Configuration
Most batches become critical or obsolete depending on your Eftsure configuration.
For example,
- the Sync onboarding batch should only run if the customer is using Onboardings
- the Sync verification batch should only run if the customer is using Verifications
Alerts
The user selected in User ID, will receive all the alert notifications configured in this section for the batches creating during check batches.
Please select a service account for the User ID.
Incremental batches
There are 3 different batches that can be monitored and configured in this tab:
- Vendor update from Eftsure sync.
- Eftsure onboarding sync.
- Bank accounts expiration
These 3 batches are delta-based batches, meaning they process all changed data since their last run.
The administrator has the ability to reset the last run date in order to reprocess the entire dataset, and the ability to re-run the process directly from this form.
Scheduling
Below are our recommendations in terms of batch setup and recurrence:
| Name | Recurrence recommendation | Description | Scope |
|---|---|---|---|
| Sync form(s) | Either manually after changes or daily, weekly, outside business hours for peace of mind | Sync updated onboarding/change request form from Eftsure portal | Global |
| Sync vendor(s) from Eftsure | Every 60 minute during business hours | Update vendor verification status from onboarding, verification process | Global |
| Expiring Documents | Occurs with an interval of 7 days | Update onboarding attachments with expiry date | Global |
| Sync expiring bank accounts | Daily | Update vendor bank account which is expired, in-active | Global |
| Clean Webservices log(s) | Occurs on the first Monday with an interval of 1 month | Withhold during hypercare for investigation purpose | Global |
| Clean History log(s) | Occurs on the first Monday with an interval of 1 month | Withhold during hypercare for investigation purpose | Global |
| Clean batch(es) | Daily | Clean Eftsure batches history and error | Global |
| Check license | Monthly | Occurs on the first Monday with an interval of 1 month | Global |
Check Batches
Our Check batches feature, available in Eftsure parameters or Eftsure Workspace > Admin > All batches, reads Eftsure configuration to schedule the appropriate batches when necessary, in the Eftsure monitoring category.
We recommend to check batches after each deployment to ensure that new batches are created and obsolete batches are deleted as part of the deployment.
Once completed, 7 to 12 batches are generating, depending on the Eftsure configuration, linked to the associated recommended Batch group, User ID, and Active period.
Batches are run for all enabled legal entities. Company reference on each batch is a reference in which legal entity the batches are initiated.
Monitoring
Batches status can be reviewed Eftsure workspace > Admin > All batches
Our extension uses a custom Eftsure batch monitoring category which allows us to regroup all Eftsure related tasks in a single view. The Eftsure administrator can now monitor tasks prefiltered on the Eftsure actions for a bird's eye view.
4 views are available to peek into the tasks:
- Batches: Tasks currently waiting or running
- Batch job history: history of Eftsure task execution and logs
- Batches errors: filtered history with errors
- Supplier Sync: sync task from Eftsure
Each of these sections offers the ability to further drill down into the batch tasks using the standard batch framework.
When available, the bottom part of the screen will display the current recurrence rule for the selected item.