Defining a Process

To start defining a business process, you must first create an instance of the "Business Process" definition. This instance provides an overview of the process itself and allows for organizing the processes. An application evaluation process could be defined as below:

Enclosing processes

In more complex environments, there might be several parallel processes working towards the same goal. In cases like this, it is a good practice to aggregate processes together by enclosing them in other processes. Say that besides a recruitment process there was a specific process for submitting an application. It would thus be a good practice to create a parent process, for example "Job Applications" with two child processes "Recruitment" and "Application".

In the Details group, you'll find a series of fields:

• Name. This is the name of the business process
• Enclosing Business Process. The parent business process, for now, let's just create a single process without a parent, thus leaving this blank.
• Specific Data. Is the name of the definition that serves as the process' central entity
• State Field. Is the name of the field in the Specific Data definition that holds its state.
• Specific Data Main Customer Data Field. Sometimes, the central entity may reference (with a $ref) another instance to whom the process is relevant. For example, the job offer an application refers to. This field tells the queue who the Main customer of the Specific data is, and adds it as a $ref to all work items (allowing for easy search and $references).
• Observations. Is a field that allows to write observations or a general description of the process's purpose

In the Visibility group you can specify a Groups field. This field specifies a UserM group that can see the process. Users without it won't be able to see or interact with this process.

Work Queues

The work queues of a process are accessible in the instance through a $references listing. This is because each work queue is an instance of the definition Work Queues. It is recommened that a process' work queues be defined via the business process instance (with the green plus highlighted in the image below), as this automatically fills a series of fields and avoids errors.