Process Designer

Processes

Compose process names in lowercase letters.

The process name serves as a key.

Prefix the process name with a customer abbreviation when JobRouter will be deployed in business affairs for a particular client.

The danger of employing the same process name is reduced.

Do not use umlauted characters (like ä, ö, ü) or minus signs in process names.

The database can't implement these characters.

Tables

Use the process name in the table name.

Tables are much easier to find in the database and will be easy to relate to the corresponding process.

Write the table field names in upper case letters.

It is then much easier to transport processes between different database systems.

Do not use umlauted characters (like ä, ö, ü) or minus signs in table names.

The database can't implement these characters.

Forms

Always write form field names in lowercase letters.

This avoids mistakes in scripts, which often result from confusing lowercase and uppercase letters in form field names.

Prefix form field names with an abbreviation. This way, you recognize the element to which the name applies (ex. section_incoming_mail).

You obtain a clear and consistent identifier for your forms.

Do not use umlauted characters (like ä, ö, ü) or minus signs in form names.

The database can't implement these characters.

Steps

Only assign one form to each step.

Avoid modeling several forms into one step using JavaScript queries (no monster forms!)

You keep a manageable overview.

Step and form should have the same name.

You can quickly match a step to a form.

Rules

Assign a meaningful title to each rule with case-sensitive uppercase and lowercase.

Create a description in the documentation field.

Other people can quickly understand the meaning of the rule without opening it.

If you did not assign a Job Function to a step, you can assign it in the rule.

If a Job Function is assigned, you have to consider it for every change.