Best Practice for custom Developing processes, forms, etc
There is a very limited post on "What are Best Practices for Testing in Integrify?" but nothing in regards to best practices for how to develop code and features for use in Integrify. To me the development process seems quite different since it can be brought in and out of Production by changing "Publish Status" on the same environment. Traditional software development typically happens on separate environments. This seems especially critical in regards to existing processes, forms, etc that are in Production status that need to be modified. What are the techniques for making changes, modifications and then updating them? What are pros and cons to doing this a certain way?
-
Adam,
One way to test while on Production is to copy the process, make edits/changes, and run the process using "Run Request" (https://help7.integrify.com/hc/en-us/articles/115005738987-Process-Menu-Run-Request) to have the tasks and alerts are assigned to you, the tester as you walk through it. You can copy processes from the "Process Detail" screen: https://help7.integrify.com/hc/en-us/articles/115004333667-Process-Menu-Process-Detail.
Mike
-
Is it best to use the method above when the only changes are to the process? What if changes also need to be made to forms within the process? Example: I copied a process and find I need to make changes to a form - but upon opening I get the message that it's used by multiple tasks or processes. Naturally I don't want to affect an existing form, but I want to test my changes for the new process. Do I simply create copies of each form and save them each to a new form name? What steps do you recommend?
-
Go to the form you want to change, click on References on the far right which will show you everywhere that form is being used on a process. In some cases, the same form might be used as an attachment in a notification which would mean that changes made to the form wouldn’t affect other areas of the process. Naturally, it is always recommended to make a copy prior to making any changes, especially to a live production workflow.
Please sign in to leave a comment.
Comments
3 comments