It would be very helpful if I could map data sources, just like connection profiles, when importing a workflow.
Use Case
I have a test workflow system connected to a test repository which connects to test system equivalents of all our production systems (CRM, Core, custom database applications, etc). In 8.3, if I imported a test workflow into production, it would add the test data sources to the production system. I would then have to change the sources in the workflow, publish, remove previous version of the workflow from the WF admin console and then delete the data sources in the admin console.
As a result of the behavior in 8.3, I would manually make changes to test workflows and then manually make the same changes to the existing production version in order to avoid the chaotic import process. In 9.1 this has changed slightly by forcing authentication for the imported data sources, but it is not enough.
In order to easily develop in a test system and publish the changes to production, I think I need the following features:
- Ability to map a data source from an imported workflow to an existing data source on that WF server. This behavior could look just like the interfaces for mapping/changing the connection profile when importing a workflow.
- Ability to configure email to/cc fields in a test system, but force all email to go to a specific email address. (I'll be adding a feature request)
If anyone has recommendations or would like to share how they develop and make changes to workflows in their Laserfiche systems, I'm all ears.
Thanks for considering this feature request.