0

BACS and payment advice set up in Electronic Reporting payment models. Every time we do a database refresh from PROD to UAT it breaks the payment model. To get around this we have to delete the set up that has come across from PROD and start the set up from the beginning again. It also means that a database refresh requires extra resource to complete the set up for this. This is a time-consuming task and some of our clients would like this to be fixed in a future release.

STATUS DETAILS
Needs Votes

Comments

S

Hello Steven,
Electronic Reporting uses Document Management framework to handle templates using to generate outbound documents and import data from inbound documents in Excel format. DM does not allow to use DATABASE location for storing ER templates. Therefore, they could not be moved from PROD to UAT along with the rest of refreshed database. If you configure AZURE location for storing ER templates, they could not be moved from PROD to UAT either as the migration process does not cover Azure resources. Currently, you can configure SHAREPOINT location for storing ER templates to share same templates for PROD and UAT environments.
Starting from the 10.0.5 release, ER will offer the ‘Backup storage of templates’ feature allowing you to configure ER for automatic creation of backup copies of ER templates in F&O database (PROD). When such copy exists in database of the current environment, but a template is missing in the primary location (configured by using DM) of this environment (UAT), at the moment when a template is requested it will be automatically restored to the primary location.
This feature is already available in the build that has been released for participants of the PEAP program - we are looking forward to your feedback regarding it.
Regards,
Nick

Category: Globalization - Regulatory features