Processes

Representation of processes in Docusnap365 – such as contract handling or invoice verification – with links to applications, business services, departments, and people. Without role models or explicit responsibilities.

Objective

In Docusnap365, processes can be defined as independent objects and embedded into the model structure.

The goal is not full-scale process modeling on execution level, but rather the structured linking of processes to relevant applications, business services, departments, and people at a higher abstraction level.

This chapter describes how processes are currently modeled and represented in Docusnap365.

Scope of Functionality

The current functionality for modeling processes includes:

  • Creating processes

    • Manually via the user interface or automatically via REST API
  • Linking to other objects, such as:

    • Applications used within the process
    • Business services that the process depends on
    • Departments that carry out or support the process
    • People associated with the process
  • Dependency diagram

    • Visualization of the modeled relationships between a process and other objects
    • Supports navigation and structural understanding within the overall model – without modeling sequences or role assignments

Example Use Cases

  • Which applications are used in a given process?

    • Visible via the modeled relationship
  • Which business services are linked to a process?

    • Traceable through the structural connection
  • Which department is involved in a process?

    • Recognizable via the organizational linkage
  • Which people are associated with a process?

    • Can be displayed, e.g., for filtering or analysis