Add support for versioning control systems to designers
Not planned
This is a request for all 5.x modules, i.e. Workflow, Web, Reporting, ....
Right now it is virtually impossible to keep track of changes in workflows, webapps, etc. Having support for VCS would make it easier to see a history of what has changed, to revert changes, etc. This would also provide an easier way to migrate items from one ArcGIS environment to another.
One workaround is to download items from ArcGIS, and then commit them to a VCS, but this still won't work for server workflows and report templates.
Ideally, there would be checkout and commit (or push and pull) options added to all the designers. I can see though that this won't be an easy thing to build, so any other solution or workaround that would make this easier would be appreciated. Maybe something similar to a webhook, that runs after saving an item? Or a desktop app that mirrors (a selection of) ArcGIS items locally?
-
I can see the value in this, although it would be quite a big feature to implement.
In the short term, you may be interested to know that server workflows are actually versioned in the file system, although there are no REST APIs to take advantage of it.
Take a look in the C:\ProgramData\Geocortex\Workflow\Workflows folder (Where "C:\ProgramData\Geocortex\Workflow" is the Data Directory defined in the Post Installer. Each json file is a version of a workflow. The guid matches the item in ArcGIS Online / Portal and the suffix after the dash is the revision number. Whenever you save a server workflow, the existing files are not changed - we just add a revision and update the index.
0 -
Ken Lyon I think there's a case especially for Workflow. These items can be very complex, so having reliable ways to collaborate and insurance against mistakes in development would be very valuable, even for intermediate users. My $0.02.
1
Please sign in to leave a comment.
Comments
2 comments