The process map is an automatically generated, read-only visualization of connected data processing modules (profiles, CI entries, ASM entries, ETL/ELT pipelines, databases, portals, REST APIs, etc.). It allows you to get a quick overview of your overall data processing flow.
Opening a process map
Simply navigate to the profile overview, mark a profile, open the context menu and select option “Process map”. Note: You can also mark a whole group to open a process map for all profiles in that group.
(1) The profile for which you have opened the process map is highlighted.
(2) The Input Agent of the profile (1).
(3) A channel the profile (1) uses in its Input Agent (2).
(4) A connected database that is used in phase 4 of the profile (1).
(5) A Response of type “File” that is used in profile (1).
(6) A channel that is used in Response (5).
(7) Another Response of profile (1) that creates a backup file.
(8) Another Response of type “Message” that calls a second profile.
(9) A second profile that is called by our profile (1).
(10) The Input Agent of type “Message” of the second profile.
(11) A navigation pane that lets you move the process map, search for specific entries and change the display size.
Opening elements from the process map
Although the map itself cannot be edited, you can open certain elements of the process map (e.g. profiles, channels, …) and directly edit them.
If you do so, it makes sense to switch to the side-by-side view.
.png)
Further examples
Sub profiles
(1) The profile for which you have opened the process map.
(2) First sub profile called by profile (1).
(3) Second sub profile called by profile (1).
ETL/ELT, error profile, profile with variable name
(1) The profile for which you have opened the process map.
(2) Profile that is called if an error occurs in phase 1 of the profile (1).
(3) The profile (1) calls an ETL/ELT entry with a function.
(4) The profile calls a subsequent profile via message, but the name of the profile is specified with a variable.
Content Inspection and ASM
(1) Content Inspection entry sends files to profile (2), which sends files to an ASM entry (3).
Portal
(1) A new style portal with the process map directly opened under “Orchestration → Portals”.
(2) A processing profile connected to the portal (1), see (3).
REST API
(1) A REST API with the process map directly opened under “Integration → API Manager”.
Event handler
(1) An event handler with the process map directly opened under “Orchestration → Workflow → Event handlings”.