Workflow

Keeping everything flowing

A workflow is a sequence of process steps that are coordinated by a system using rules and assigned to the appropriate users. PSIpenta Workflow enables processes to be defined that will run automatically when certain events occur.

Workflow ERP-System PSIpenta
©ThinkstockPhotos, sidewaysdesign, iStock

Features

Object-based workflow

  • Definition of queries using filter window trays
  • Task list summarises all work orders using traffic light logic
  • Flexible system-wide task assignment, using roles and users
  • The volume of work pending can be discerned at a glance using a counter

Activity-based workflow

  • Management of process elements
  • Event
  • Activity/task
  • Operation (AND, OR)
  • Task status (in progress, interrupted, activated, completed, aborted)
  • Definition of transitions between individual activities
  • Selection and transfer of (alternative) decisions within a process
  • Monitor function for processes, process elements, events, task assignment
  • Import processes
  • (Basic framework) from Microsoft Visio®

Object-based workflow

PSIpenta Workflow allows databases to be selected easily using filter functions. This means that the database to be processed is selected according to the specific task. Object or user-specific selection criteria can be saved and reused. Identifying the stored filter as workflow-relevant causes the result set to be displayed in the workflow management task list. Traffic light functions help the user to prioritise the tasks. Implementing these filters updates the task list and displays the number of data records found. Starting from the task list, the corresponding data records can then be processed. Filtering using dynamic date ranges is supported. The date or a range of dates (from/to) is updated daily (incremented).

Activity-based workflow

Process chains are initiated by defined events, i.e. a sequence of activities is initiated. These activities must be assigned to individual people or a group of users. The assignment of an activity to a group is based on the stored roles, i.e. a person from the group can perform the task. The transitions from one activity to the next can be linked to conditions. Each task is accepted by a user and reported as finished. The processing times that can be derived from this provide impetus for process optimisation. The completion message for a task releases the next task. The stored workflows can be versioned and assigned a validity. Escalations and complex processes are mapped using sub-processes.