Executing Jobs

A job puts the assignments for a certain process into motion, so they can be worked through step-by-step by the respective employees assigned to them. A job is a tick list for a valid process that can be reused as and when required.

A job represents the essential elements of a process from a workflow perspective in such a way that employees/groups/organizational units can be assigned responsibility to the individual activities. The planned flow can be checked and improvements made if necessary. You can add comments to the worksteps to help improve the process.

You can view the attachments directly at the process or workstep so that you can glean detailed information about the workstep.

It is also possible to map how decisions are made in the process and how process steps are carried out in parallel by various people spanning various departments within the job.

You can add new process steps which are not currently mapped in the process when running through the job. It is also is possible to skip certain process steps if these are not relevant.

This enables jobs to be flexibly used within the daily tasks and enables discussions to be carried out about possible improvements which can be made to the current way the job is carried out.

Bpanda provides the following support when executing processes using the jobs feature:

• Open the overview of your current jobs by clicking on Jobs in the main menu. You can also see how many jobs you have on the Assignments tile on the start page and your assignments are shown in the overview. This also includes the jobs in your group.

• Jobs relevant to you are shown in the order of deadlines to be completed by.

• Every user can create a new job on the process page by clicking on  Create Job, as long as the process fulfills all prerequisites. The process must be valid and cannot contain any modeling errors or unsupported elements.

  Note

  The following are not supported:

  • Inclusive gateways.

  • Event-based gateway.

  • The use of more than one start event.

  • All boundary events.

  • All typed events (assigned to an event category), apart from messages as start or end events.

   

  Untyped start and end events are not supported.

  A dialog opens to show you if any modeling errors were made or unsupported elements were used. The dialog also shows you where in the process the modeling error or unsupported job is.

• You can add a job by clicking on the icon on the Favorites, Relevant Processes and Last Viewed overview pages.

• You can add a name to the job and you can also add a deadline for completion if required and any information about how to execute the job.

• You can add attachments to the process or a process step and then edit them.

• Once a job is handed over, responsibility is also handed over. You are initially assigned responsibility of the job and can execute it. If the job starts with a start event that is not in your lane, then you should assign the job to an appropriate employee.

• It is clear to see which colleague or group is responsible for the individual worksteps and this can be easily managed. It is easy to assign and take on responsibility. This also applies for the competence of organizational units.

• A message can be added as a comment for the job and for each workstep.

• The current workstep is shown in the list and process diagram in the job.

• Any unnecessary worksteps can be immediately canceled and additional worksteps can be added. If worksteps are canceled or added, then a comment about it should also be added.

• Completed worksteps are marked in the list and in the process diagram.

• You can cancel and reactivate worksteps.

• Changes cannot be made to a completed job. Information about the job serves as a log.