HI Michael thanks for the response and sharing your current reasons.
Please keep us posted on any change in your road map around this, as this maybe a requirement, however it is hard to say at this stage.
At the moment the use case to move to the new service-driven architecture is for non-GIS/Arc Desktop users.
However, the majority of our users are GIS professional and use ArcGIS Pro or ArcMap on a daily basis, making this use case a very low priority.
Future use case is to maintain an ArcGIS Workflow Manager capability, if the current (classic) Workflow Manager is to be retired.
The timeline to transition is not set but I think it will have two driving factors;
- The life cycle of the current (classic) workflow manager.
- New capabilities/hype of the service-driven architecture creating a demand within our non-GIS users and potentially our GIS users as well.
The move to ArcGIS Datastore would require a large assessment for the business which may affect certain activities such as reporting through PowerBi, SQL (views) queries in the database and custom steps using python.
Acknowledge that PowerBi can use REST calls and there is a Python API for the new architecture, both maybe worthwhile substitutes, there could well be a large body of work ahead to transition.
Finally, I think it is worth noting the current (classic) Workflow Manager is working well for us; the majority of the workforce are using Workflow Manger in ArcGIS Pro for workflow manager activates, and get their insights and reports through ArcGIS Pro, PowerBi, ArcGIS Dashboards with additionally send gdb cuts (derived feature classes) from the workflow manager database. The workforce are using the workflow manager more and more as time goes on requiring numerus extended and related job properties with additional business tables in the database.
Josh
