The do‘s and don‘ts of designing processes

Todos list

Sometimes creating a process and making it work without a hitch requires you to focus on details and take many steps to avoid mistakes, so we have come up with a checklist of all the things you need to do and all the thigs you should avoid, before you‘re ready to start your Application.

The do‘s

  • The first thing you need to do when you‘ve finished creating your process is to double- check if all the variables, including the Component IDs of the forms you will be using in the process, are typed into the Process Variables and ensure that all the variables you have entered are mapped properly.

  • Bare in mind that variable names are case-sensitive and that their first character must be a letter, that subsequent characters may be letters, digits, dollar signs, or underscore characters and that white space is not permitted. In addition to this, the name you choose must not be a keyword or in Java or MVEL programming language.

  • Check if the connectors are working properly by sending a test email for the Email connectors, or doing the ping test, if you are using Remote Agent. Likewise, make sure the passwords that you‘re using are correct.

  • Also, if you‘re using gateways, make sure to define the type of the diverging or converging getway you are using (and/or/xor), before you save your process and run your application.

  • Developer
  • In cases when you‘re using Copy, Move, Wait for file or List files tasks, ensure that you have opened the Remote Agent before running the Application.

  • Additionally, when using these tasks, take a look at whether you‘ve entered the right paths and locations.

The don‘ts

  • Don‘t start your process without previously double-checking the configuration of each individual task.

  • When creating forms, avoid giving different components of the same type (for example radios) the same Component ID, otherwise the user won‘t be able to select an option for each component.

  • Developer
  • When defining the message of the Log, the Responses, the Component and File IDs, etc. don‘t forget ot use the #{} notation.

  • If you‘re using the Script task, don‘t start the process without checking the extensions and making sure you have the execute permission.

  • Also, don‘t run an application that includes a Work Order, without changing its status to ‘‘ready‘‘ beforehand, otherwise the user won‘t be able to select the desired Work Order.

  • Testing and debugging of complex processes can be an overwhelming task. Don't wait until the very end to configure tasks. Instead, try to populate configurations and test them as they are being added to the canvas. Doing so will leave you with a clear overview of the flow at every step of process designing.

  • Avoid the mistake of working on the same process that is opened in several tabs. This may result saving the wrong version and not keeping the necessary changes that you‘ve made.