Process Designer - Editing / Testing / Debugging / Deploying workflow (3 Comments)

Topic by RobertP

Content

I'm trying to figure out the basic workflow for Editing / Testing / Deploying custom processes in the Process Designer.  I see that I can click on the external event and see the code, but I can't edit the code directly in the Process Designer dialog.  I tried to export the code, but that results in some xml code with certain characters replaced with XML codes such as line feed replaced with &#xA;, '<' replaced with &lt, etc.  

I can cut-n-paste into notepad, but how do I get it back into Process Designer?  Do I enter my edited notepad file in the PHP Code File widget and Save? 

What is the intended workflow to Edit/Test/Deploy?  I think I saw in the manuals that I should:

1. Ask customer care to create a cloned test site.  This should have my current production custom process code.
2. In the test site, edit the PHP code in Process Designer.
3. Save the Process Designer.  (is my code active in the test site now, or do I need to "Deploy" to be able to test & debug it?
4. Once I'm happy with the code, I think I saw that I should then export from the test site, then import to the production site, and then Deploy in the production site.  

Is that all correct?

What is the best way to debug the code?  Without a debugger, resorting to log files with print statements seems to be the best option.  I see in our current answer_update event code, they (RN engineers) are writing to a /tmp/answer_updatelog.txt file (see below for example).  I’m pretty sure I can’t see that file anywhere in the RN console.  Is there a file path that can be used instead of /tmp, that I can do something similar and maybe see the contents in the file manager->custom folder?  Any better solutions?                                                                                          

Thanks,

Robert

Code Block