Hi @JFarmer,
Thanks for the response and looking forward when you will post that blog.
In this particular space, I think we are hoping to reduce our overall software and infrastructure footprint as well as the hope to write business driven workflows, rather than system driven workflows. If we can utilize a SaaS offering for workflow manager to handle both Enterprise and AGO needs, this would be preferred (we always struggle with availability of network infrastructure). If we have to do on prem, that's fine, just means a little more work. What I really don't want is having to have both because we have both Enterprise and AGO. Having to implement a "flavor" of workflow manager for each platform, I think will become very burdensome, because overall our workflows are not relegated cleanly to these system delineations. For example, being a City, we have a complicated workflow every time our City Boundary changes which includes data updates, notifications, and changes to published services in multiple locations. Feature services are both in our Enterprise system as well as on AGO. Data access, view and audiences are different (private verses pulic). We have many data sets like this. I want to eliminate the need of having to author different workflows based on a system, and instead write one cohesive workflow as it truly exists defined by the business case. Would I have to write double the workflows if we have data in both systems? How do these workflows "talk" or know what step each is at? Having workflows "aware" of what is happening in either platform is important if the "flavor" of workflow manager must be separate. If AGO Workflow is agnostic to what is on Enterprise, and Enterprise Workflow is agnostic to what is on AGO, this is unhelpful. Many organizations use and need both systems, and singular workflows span both systems. Drawing a "line" based on the system platform breaks up workflows (at least I think it will for us), and will create more complexity and overhead, rather than clarity and helpfulness. We also do not have clean deliniations in terms of who uses Online vs Enterprise. Everyone in the org uses both. Some of this in my mind is still somewhat theoretical as we have not implemented any Workflow Manager at all, so I am imaging and projecting in my head how this might work, and I might not understand everything including current system capabilities (hence my oringal question 😉). Would love to discuss more!
