ArcGIS Workflow Manager has added a new service-driven implementation pattern which exists in parallel with the geodatabase implementation pattern - referred to as “(Classic)” in documentation and My Esri. The two implementation patterns are separate and not technologically compatible. The new service-driven implementation focuses more on web-based workflows, data editing involving the Utility Network, Parcel Fabric or Linear Referencing, and automated processes while the geodatabase implementation is focused on cartographic mapping.
This blog provides information on how the new implementation pattern is licensed and license migration details for existing Workflow Manager customers.
Below is the detailed description of both implementation patterns and how they are licensed.
Introduced at 10.8.1, the new service-based architecture allows users to connect to a service for web-centric workflows through the Workflow Manager Web app to manage, design, and run workflows. In addition, this pattern has workflow automation and extensibility opportunities and an ArcGIS Pro extension.
There are several components, and each is licensed in the style needed for the software they enable.
Classic implementation connecting to an enterprise geodatabase
This pattern has existed for many years and has a desktop and a server component. The server component requires the Workflow Manager server extension to be installed on top of ArcGIS Server. The Workflow Manager Classic Pro component is embedded in ArcGIS Pro. For those customers who are using ArcMap, the ArcMap component requires the Workflow Manager Desktop extension to be installed on top of ArcMap and a Workflow Manager ArcMap license. The UI and documentation for this pattern have been updated to include “(Classic)” to distinguish from the new service-based UI and documentation.
Workflow Manager (Classic) Server extension is licensed as an extension in the Server Manager. The Workflow Manager ArcGIS Pro extension license enables both the Workflow Manager service-based and geodatabase functionality in ArcGIS Pro.
Esri introduced a service-based implementation pattern of ArcGIS Workflow Manager
A service-based architecture provides a more robust system for managing work across users and the organizations’ GIS environment to support distributed workforce, web-based processes, and more, and benefits users in the following ways.
For customers who primarily use geodatabase-deployed workflows you can continue to use your Workflow Manager (Classic) Server extension with your Workflow Manager (Classic) Desktop extension. For those interested in the service-driven implementation pattern, please note that because both patterns are significantly different technologies, workflows created using Workflow Manager (Classic) will need to be redefined in the service-based implementation.
Customers who currently license ArcGIS Workflow Manager (Classic) Desktop will see ArcGIS Workflow Manager user type extension and ArcGIS Workflow Manager Server Standard automatically added to your My Esri. Please note that the service-driven version of Workflow Manager is currently available for ArcGIS Enterprise deployments only. In order to use this new architecture, you will need to license Workflow Manager Pro through ArcGIS Enterprise.
If you have a product that includes ArcGIS Workflow Manager (Classic) you are also eligible to get the Workflow Manager user type extension as per the above described license entitlement which will automatically appear on your MyEsri.
For questions about licensing changes, contact your customer service representative. For questions about which of the two types of implementations is a good fit for your needs, reach out to your account manager. If your organization has an Enterprise agreement, please reach out to your account manager and customer service representative.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.