Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.To learn more, read the FAQ and watch the video.Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.
I'm looking for a way to manage the WFA with a version check, as WFA is really not build to have some way to extract just the codes what we do for a custom solution or even for some sort of edits that might happen mistakenly ..i want to know if there are any ways to manage WFA code versions.
what i want to really do is
-Know if there are any edits done to a code by mistake we can pick it.
WFA doesnt have a native source control mechanism. But as sinha and abhit has explained, it does provide hooks to do that.
This is how, many WFA customers today manage and source control the workflows.
Have 3 WFA servers
Development Server- This is the server where the actual wokflow development command development etc happens (This is a sandbox enviroment typically)
Test Server- This is the server that exactly mimics the product server with exact OCUM datasources, controllers etc
Production Server - This is the server on which the workflow gets invoked and executed.(Worfkow gets prometd from test to prodcution)
Do all your workflow development in Development server once its good enough with WF development and testing move to Test Server by exporting as dar file. Run couple of more test on the test server. If everything is satisfactory move to Produciton Server.
As you do your development in server 1, keep checking in the command scripts into SVN,CVS etc as .ps1 and .txt files for sql finders, filters and userinput query.
And once the workflow is in a decent shape checkin the .dar file as well.
The reason to checkin both the .ps1 file and .dar file is because the workflow also contains variable, mvel expressions etc which is not captured in the .ps1 file.
This way you can have a source control system, with WFA.
Make use of the version for individual commands and the description fields as comments for the changes as well.
I have seen quite a few workflow developers making use of the description fields of commads,workflows as comment field as well apart from description of the workflow or command.
Hope this helps. Not the easiest or the simple solution. But it does help to keep version control and source control.
PS: Lock all the commands, finders, filters and workflow in your development enviroment right before you move it to test.
Version control and management is a totally different software solution requirement from what WFA is aimed and built for.
Prevention of accidental edits can be achieved using "Locking" feature. Any designer item like a workflow, command, etc. can be "LOCKED" by an Admin/Architect and no editing is allowed to be saved on the content and only "Save AS" works. You can see it at the tool-bar or upon the right-click.
WFA also provides content versioning where any edit to a designer content is followed up by prompt to modify the existing version of the content. So anytime you modify a content, you can upgrade the version to indicate it.
However this is not mandatory to update the version upon every edit before saving it.
Also there is is no separate field to indicate what was changed from the last version. I think this should have been available.
If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.