Business Services
2 minute read
Objective
In Docusnap365, business services can be defined and structured as independent objects.
They represent the functional capabilities of an organization – such as “Time Tracking”, “Customer Relationship Management (CRM)”, or “Financial Accounting” – independent of the underlying software products.
This chapter describes how business services are currently modeled in Docusnap365 and how they can be linked to other objects.
Scope of Functionality
The current functionality for modeling business services includes:
Creating business services
- Manually via the user interface or automatically via the REST API
Linking to other objects, such as:
- Applications that technically support the service (e.g., SAP, Business Central)
- Processes in which the service plays a role (e.g., quotation or invoicing processes)
- Departments that use or operate the service
- People who are associated with the service (e.g., as users or contributors)
Dependency diagram
- Visualization of modeled relationships between a business service and other objects
- Supports understanding of how the service is embedded in the overall model – without evaluation or prioritization of relationships
Example Use Cases
Which applications support a specific business service?
- Visible via the technical linkage
In which processes is a business service used?
- Shown through process relationships
Which department primarily uses a service?
- Derivable from the organizational assignment
Which people are associated with a business service?
- Can be shown, e.g., for filtering or reporting purposes