Added server component based on quartznet server
It is important to completely uninstall any previous version of RIS. You need to delete Schedule.xml file as well if you are upgrading from <3.0
Added ability to switch authentication method with ADAL due to incompatibility of MSAL with on-premise environments working with ADFS 2016
Changes to UI logic on job forms.
Imported entries (entries that are present in job definition, but not existing is RIS parameters) of app registrations, and instances will now have names with timestamp.
refactoring and many changes.
It is not backward compatible with Schedule file. It is required to configure all jobs from scratch.
Ability to import packages into multiple legal entities using single RIS import job.
It is now possible to download execution errors for import job in json format.
All jobs have controls of delays between processed files as well as between execution/processing status checks.
Changed displayed value of trigger state in case it is Blocked. Now it says Executing. "Blocked" was misunderstood by users.
Implementation of error keys file for failed or partially failed imports.
Cleanup of validation procedure. Removed some dubious checks.
Corrects interval in export job
Ignores bad requests of GetExecutionStatusSummary request which sometimes returns Bad request. In such cases job will just retry request.
Updated Quartz.Net to 3.0.6
Updated Polly to 6.0.1
Updated ADAL to 3.19.8
Retarget whole solution to .Net framework 4.6.1
This change makes an extra option available to be able to configure the relative path to the OData actions of ImportFromPackage (Import jobs) and ExportToPackage (Export jobs) actions through the user interface. The configuration is made available through the "Options" button which is available for import/export jobs.
Please note that Upload/Download jobs are not in the scope of this change and remain unchange from configuration point of view.
To increase the traceability of the files getting uploaded to D365FO, the Manifest.xml file is getting updated with the original file name before uploading the data package. Offcourse this change is also using the original file name in the data package for the data file itself. This happens right before the upload of the data package which is getting prepared based onthe template file name.