Profile trees

So sub profiles can be used to build trees of profiles. With one profile as the root node and an arbitrary branching/nesting below it.

Node profiles and profile networks

By combining the nesting and chaining of profiles, you have the ability to build complex profile networks.

Each profile that integrates other profiles then acts as a collecting/binding node in your profile network, i.e. as vertical integration and the profile chains as horizontal integration. By "vertical" we mean that you can build tree-like layers of profiles and with "horizontal" that you can walk along a profile chain within a layer, so to speak.

In order to optimally support the concepts of vertical and horizontal networking (and the integration of your employees), we offer the add-on modules Workflow and DataCockpit.

Simple application example (vertical integration)

Even though profile nets can be a complicated subject, they are a great simplification for many users in classic application cases, and as a result offer a significantly increased clarity/traceability. The following is an example of a classic EDI case.

Classical EDI: Sequential data enhancement.

Multi Source: Parallel collection of several sources in the source structure. This approach is more compact and clearer and allows a simple decomposition of a problem into sub problems. In addition, better encapsulation is possible and service profiles can be offered. For example, have your SAP expert create a profile once for accessing the SAP system. Afterwards, any user can integrate it, even without SAP knowledge.