Process Designer function list
Explore the core capabilities of the Celonis Process Designer. Use the links below to access detailed documentation on modeling standards, system interfaces, and administrative functions.
Generate printable manuals | |
|---|---|
Manage manual templates centrally. | Templates for creating manuals are centrally managed in the administration area. |
Meta-Model (Company Map) | |
Configure method | The method is configurable. |
Hide, rename, or add attributes/objects (Advanced Configuration) | Attributes/objects can be hidden, renamed, or added in the administration area. Changeable attributes/objects are predefined. |
User Management | |
Manage users and user groups. | Users and user groups are created or deactivated in the administration area (deletion is impossible). They are also assigned user roles and permissions there. |
Authentication | |
Authentication provider: Use OAuth | The authentication provider can be configured in the administration area. |
Authorization Management | |
Define permissions for facets. | It is possible to set permissions so only certain user groups can add or edit a facet. |
Tag Management | |
Define Tags | Tags are grouping criteria that can be defined individually (e.g., product groups). They are also relevant as criteria for the scope filter. |
Review Date | |
Set review date | For the continuous improvement of the process world, a review date can be set for each process. Using evaluations, e.g., on the "start page," one keeps an eye on which processes are reviewed and, if necessary, need to be updated. |
Language Management | |
Configure languages (default: DE/EN) | The languages German and English are available by default. Other European and Asian languages can be configured (optional). |
Configure default or optional language | The default language setting (Default) and other optional languages can be configured. |
Making languages available for reporting | Reports can be offered in different languages. |
Create and upload a new user interface language. | It is possible to create and upload new (user interface) languages. |
Workflows Configuration | |
Configure notifications by e-mail or tasks | E-mail notifications about pending requests ( e.g., about a pending approval) are configurable. The areas of application for e-mail notifications are predefined. |
Adjust release cycle | The approval workflow can be customized by integrating additional approver/authorizer groups or by changing the time span until the validity start. |
Feature Management | |
Enable and disable features. | Certain functionalities/features can be activated or deactivated individually. |
CI Management | |
Customize CI | The workspace in Celonis Process Management can be adapted according to the customer-specific CI. |
Configurable profiles | |
Configure profiles | Profiles are individually configured by the administrator using widgets. They show aggregated information about processes or objects. |
Create and customize stereotypes (subtypes) for diagrams/objects. | Stereotypes (subtypes) can be created to categorize processes or objects further. The author can create them during modeling. |
Generate printable manuals | |
Configure Manuals | Manuals (process manuals, organization manuals, professional and technical specifications, etc.) can be programmed in Word, and static information, such as headings, images, formatting, etc., can be customized using the normal Word application. Within Celonis Process Management, the different manual templates can be uploaded and activated/deactivated in the administration area. |
Process Validation | |
Define validation rules | Standard validation rules can be defined (within a given framework). |
Automation | |
Configure Service and WebHooks | A Webhook enables an application to provide another application with real-time information, i.e., it receives the data immediately - in contrast to typical APIs where the data would have to be queried very often. This makes Webhooks much more efficient for both providers and consumers. |
Organize process architecture | |
|---|---|
Structure process models hierarchically | Process models (consisting of structure-giving processes and process flows) can be built hierarchically as a navigation tree. The process depth is freely selectable. |
Move process models | Processes can be moved within their hierarchical structure. Subordinate elements are moved as well. |
Generate graphical navigation structure automatically. | The navigation tree is also displayed graphically as a "block layout", which can also be used to navigate to the levels below. |
Sort processes in the architecture with sort number | The sequence of processes within their hierarchical structure can be sorted individually. By default, the processes are sorted alphabetically. |
Versioning | |
Delete not-released diagrams | Processes or objects that are in progress can be deleted. |
Sort processes in the architecture with sort number | The sequence of processes within their hierarchical structure can be sorted individually. By default, the processes are sorted alphabetically. |
Consolidation of objects and diagrams | |
Consolidate diagrams and objects. | Redundant processes or objects can be consolidated. For this purpose, a master process or object is selected, and the element to be consolidated is assigned. Only processes or objects that have not been released can be consolidated. |
Authorization Management | |
|---|---|
Authorize editing of diagrams and objects by multiple authors. | Multiple authors can be defined for processes and objects. If no author is defined, any Celonis Process Management user (provided he or she is authorized) can edit a process or an object. |
Define authorization levels | The administrator stores the characteristics of all possible authorization levels. |
Assign permissions to individual users or user groups. | The authorization levels can be assigned to specific users or user groups to authorize content editing for specific authors only. |
Set permissions on diagrams or objects | Each process or object can be assigned appropriate authorization levels and specific users/user groups (optional) |
Assign permissions for facets. | Authorizations can also be assigned for complete facets (navigation areas, e.g., "risks"). |
Assign authorizations for architectures. | It is possible to customize rights to build architectures. For example, an author can be authorized to create structural processes (which, by default, only the architect does). |
Review Workflow | |
|---|---|
Review: Define Reviewer | So-called "reviewers" can be stored to check the process before starting the release workflow. This can be any Celonis Process Management user. |
Review: Automatically forward the request to the reviewer | After a status change, the process/object to be checked is automatically forwarded to the reviewer. |
Review: Notify Reviewer | The reviewer receives a message in his workspace. Feedback to the author can be given via the request function. |
Request Workflow | |
Request: Send request for processes or objects | Every Celonis Process Management user can submit a request, i.e., give feedback on a process or object. |
Request: Automatically forward the request to the responsible person | The request for a process or object is automatically forwarded to the responsible person (or quality manager, if stored). |
Request: Display/change the processing status of the request | The person responsible for the corresponding request area can change the initial status. |
Request: Call process/object directly | The process or object to be released can be accessed directly from the request via a link. |
Request: Accept or reject the request | The responsible person can accept or reject the request. |
Subscriber Service (will soon be integrated in the favorite management) | |
|---|---|
Subscribe to content (subscription service) | Processes or objects can be subscribed to. This allows the Celonis Process Management user to track selected content's version history easily. |
Info-Mail for release changes | The user is notified by e-mail when a new version is released (day/week/month). |
Subscribe to content with multiple selections. | The multiple selection allows you to select and subscribe to several contents simultaneously. |
Select subscriptions for categories. | Multiple selection allows you to select and subscribe to several document categories simultaneously. |
Combine subscriptions and favorites (button with fly-out) | Subscriptions and favorites are summarized in an overview for quick access. |
Show a list of all changes in chronological order. | Subscription changes are listed chronologically. |
Favorites management | |
Define favorites | Contents can be defined as favorites and called up specifically. |
Favorite Service: Manage/Group Favorites | Defined favorites can be grouped and managed for individual groups/functions. |
Favorite Service: Share Favorites | Favorites can be shared with other employees. |
Favorites service: Info mail in case of version change | Through the integration of the central mail service, the user is informed by mail when a new version of his favored process or object is available. |
Link Service | |
Create permanent links from versions. | Links to specific process or object versions can be generated and inserted into emails or documents for further use. |
Create permanent links from version independent versions. | Links to specific processes or objects can be generated and inserted into emails or documents for further use. The latest version is automatically displayed. |
Create permanent links from the selection (in versions) | Links to selected process flow objects can be generated and inserted into emails or documents for further use. The latest version is automatically displayed. |
Glossary | |
Provide a central glossary for all users. | A centrally accessible glossary can be created to provide more detailed explanations of all technical terms or other nomenclatures used. Individual terms in the glossary can be assigned to processes or objects. |
Mass data editing | |
Mass edit linked attributes. | Through mass data processing, attributes linked to processes or objects (in the processing status) can be changed quickly and efficiently, e.g., when changing responsibilities or setting scope filters. |
Training Assistant | |
Use the Training Assistant app to communicate specific expertise. | Employees and their managers can thus individually view, plan, and manage upcoming training on different end devices. Defined roles are assigned to positions created in the organizational structure. This identifies the corresponding users for whom a specific training will be generated. |
Manage Customer Experience | |
|---|---|
Define customer experience management models. | Customer Experience Management is a marketing instrument that describes the cycles of a customer journey (from awareness of a product/service to purchase and long-term customer loyalty). Celonis Process Management's process world can be combined with a customer trip in a uniform management system. |
Modeling Customer Journey Maps | The Customer Journey Map is built up by individual Customer Journey Steps and depicts the chronological sequence of steps as a customer/person moves to their destination. The goals can be different and changed by strategic touch points or further information. |
Generate Customer Journey Map | An aggregated graphical representation of all customer journey steps with additional information, such as linked processes, in the form of a configurable "profile" (matrix) is possible. |
Define customer touchpoints | The customers' touch points with the company are defined. They form the interface between the customer, the brand, the internal company process, and the persona (the potential customer). |
Define Stakeholders | The list of all stakeholders with direct or indirect contact with customers illustrates the complexity of service provision and helps identify potential for improvement. |
Determine and define personas. | Personas reflect certain persons/target groups with their respective typical characteristics. These include characteristics such as purchasing behavior, interests, age, etc. |
Survey and define the voice of the customer | Collecting customer requirements (voice of the customer) is also important for creating a comprehensive customer journey map. Here, the expectations, likes, and dislikes of the customer are described. |
Define distribution channels | All distribution channels are listed. They are closely related to the TouchPoints. |
Digital documents | |
|---|---|
Create document templates for processes and documents | Individual document templates can be created for processes and documents. |
Edit document templates for processes and documents | Content is extended as free text and formatted in the HTML editor. |
Release document templates for processes and documents | Document templates for processes and documents must be approved. |
Create document templates for the remaining facets | For other facets (navigation areas, e.g., "risks"), individual document templates can be created |
Edit document templates for other facets | Content is extended as free text and formatted in the HTML editor. |
Release document templates for other facets | Document templates for other facets (navigation areas, e.g. "Risks") must be released. |
Evaluation of object links | |
|---|---|
List connected diagrams and objects in an evaluation group as links | An aggregated representation of all linked processes and/or objects in a configurable "profile" is possible. These can be called up directly via a link. |
Audit Trail | |
Display version history of all versions of diagrams and objects | An audit trail is used for quality assurance and presents the entire history of process version changes in an audit-compliant manner. |
Generate printable manuals | |
Generate standard manuals as Word files. | Standardized manuals can be generated automatically or manually as Word files. |
Generate process graphics as Word files. | The quick print function allows process graphics to be printed quickly as a Word file. |
Generate individual customer evaluations as Word files. | Evaluations are individually configured and output as Word files. |
Open-generated PDF manuals. | Manuals in PDF format are available and can be opened. |
Automatically generate PDF manuals upon approval. | Manuals in PDF format are automatically generated upon approval. |
Personal settings | |
Role entry for all employees with connected home page | Roles can be selected individually, allowing you to enter the process world. |
Global filtering | |
|---|---|
Adjust the navigation tree on the left and the graphical display according to the set scope filter. | Filtered-out processes or objects are graphically grayed out and no longer displayed in the navigation tree. |
Apply Scope filter to processes and objects in list view (can be activated/deactivated) | Processes or objects can be displayed in the list view. The search results list can be further narrowed down by restricting the search to the scope (Scope filter). |
Enable filtering for manuals. | The extension of the standard filtering for manuals is also possible. |
Import and export process models | |
|---|---|
Export BPMN 2.0 diagram | Exports of processes or objects in BPMN format can be transferred to other systems. |
Import BPMN 2.0 diagram | Imports of processes or objects in BPMN format from other systems are possible. |
Export Process Designer Diagram | Exports of processes or objects in Process Designer data format makes transferring content from one database to another possible. |
Import Process Designer Diagram | Imports of processes or objects in Process Designer data format make it possible to transfer content from one database to another. |
Import XML | Import of processes or objects in XML format from other systems is possible. |
Import ARIS | Processes and objects can be converted from ARIS to Process Designer. The exact mapping must be specified individually in advance (additional service). |
Import Word documents | |
Import Word document (prerequisite: configured import template) | Imports of processes or objects in Word format are possible. An import template must be configured for exact mapping (additional service). |
Visio Importer | Processes and objects can be converted from Visio to Process Designer. The exact mapping must be specified individually in advance (additional service). For further information, see Using the Visio Importer. |
Mass data processing | |
|---|---|
Export Excel mass data processing (translation) | Exports for efficient translation of mass data in Excel format are possible (additional service). |
Import Excel mass data processing (translation) Import Excel mass data processing (translation) | Imports for efficient translation of mass data in Excel format are possible (additional service). |
Architecture Excel Importer | |
Import and update organizational hierarchy. | Initial organization import of provided third-party system data, such as SAP HCM. Additionally, continuous updates of the organization's data are possible. The use of the importers requires individual service to enable the correct import and update (additional service). |
Import and update IT architecture | The IT architecture was initially imported from the third system data provided. Additionally, continuous updates of the IT data are possible. The use of the importers requires individual service to enable the correct import and update (additional service). |
Import and update risk and control architecture | The risk and control architecture is initially imported from the data provided by the third-party system. In addition, the risks and controls can be continuously updated. The use of the importers requires individual service to enable the correct import and update (additional service). |
Requirements can be imported and updated. | Initial import of requests from provided third system data. Additionally, a continuous update of the requirements is possible. The use of the importers requires individual service to enable the correct import and update (additional service). |
REST API interface | |
Open REST API interface to Process Designer | New site coming |
Meta-Model (Company Map) | |
|---|---|
Use BPMN 2.0 standard. | Process modeling is carried out according to the BPMN 2.0 modeling standard about the process flow and the available symbols. |
Extended BPMN 2.0 standard modeling standard | Centrally managed objects (such as risks, standards, etc.) can be added to the processes. |
ArchiMate 3.0 Standard | The ArchiMate 3.0 standard is an open and independent modeling language for enterprise architectures. Celonis Process Management offers the possibility to model IT architectures in this standard and thus makes a decisive contribution to the implementation of Enterprise Architecture Management (EAM) |
Build IT landscape | The IT landscape can be depicted in the uniformly designed hierarchical Celonis Process Management structure. |
Map and manage organizational structure, including positions | The organizational structure can be mapped and edited in a uniformly designed hierarchical structure. |
Implement Customer Experience Management (CEM) | For practical implementation of the CEM, Celonis Process Management offers the option of defining a customer journey. All points of contact between a customer and the company are graphically displayed to optimize interactions and achieve long-term customer loyalty. |
Customer Journey Mapping | The customer journey is displayed in the form of a customer journey map. Celonis Process Management maps the mapping method required for this. |
Create strategy and target diagrams (target trees, measures including status, etc.) | Strategic strategy and target diagrams can be displayed hierarchically and linked to measures and (optionally) their status. |
Define key figure trees and reports with report chapters. | With Celonis Process Management's key figure system, even better control of the company is possible. The KPI system allows mapping KPIs in driver trees (KPI architecture). With the combination of the strategy view and the KPI system, customers can establish a balanced scorecard in Celonis Process Management and communicate this continuously throughout the organization. By continuously measuring the key performance indicators, the achievement of objectives is checked, and the company can react to changes early. Furthermore, the key figures can be linked to processes, IT application systems, and other views in Celonis Process Management. The connection between the goals (the strategy) because of key performance indicators and the processes ensures the fastest possible implementation in the organization and for each employee. In addition to the key figure driver tree, reports with report chapters can be displayed. This enables companies to map the annual report chapter structure, for example, and link the necessary key figures in the various report chapters. This will also enable companies to generate company reports from Celonis Process Management in the future. Celonis Process Management is thus increasingly digitizing corporate management. |
Set up product portfolio. | A clear presentation of a product portfolio and the linking of relevant attributes with the process landscape is possible. |
Manage Skills | Skills can further specify the positions stored in the organizational structure. Thus, the organizational structure can be optimally linked with the skills required for the job. |
Manage Learnings and Training | The training and learning units relevant to implementing BPMN can be mapped and connected to the relevant processes. |
Present risk/control management | Risks and controls of a process can be depicted in a hierarchical structure and assigned to processes. |
Manage requirements | Requirements and solutions are definable and can be linked to stored solutions. |
Deposit standards and standard chapters | The standards required for the process flow (e.g., ISO) and corresponding standards chapters can be defined. |
Central property management | |||||
|---|---|---|---|---|---|
Reuse objects (roles, organizational units ...) | Objects stored in the repository are managed centrally and can be linked to processes or organizations as often as required. | ||||
Create a suggestion list when entering glossary names (Auto-Complete function) | Available objects are quickly found by entering the first 2-3 letters and can be selected from a list. | ||||
Search for objects in lists and architectures via a dialog. | Objects can be searched for keywords. Specific fields or criteria can further filter the result list. | ||||
Upload and link attachments. | |||||
Add attachments as links. | Attachments to further process information can be stored as internal links (e.g., to documents on SharePoint) or external links (e.g., to websites). | ||||
Upload attachments (documents) | Attachments (further process information, such as documents) can be uploaded to Celonis Process Management. The following file formats are accepted when uploading attachments:
| ||||
Upload images and visualize them directly. | Images can be uploaded in various formats (jpeg, png, etc.) and displayed directly. | ||||
Intelligent linking of plants directly with connected systems (additional services) | Plants and connected systems can be linked (additional services). | ||||
HTML text fields | |||||
Formatting descriptions with HTML editor | The HTML editor can make format adjustments (e.g., font size and image uploads) in the description text field. | ||||
Global Filtering | |||||
Define scope (scope filter) via organization, locations, and tags. | With the Scope filter, processes, and objects can be filtered according to their respective scopes. Relevant here are organizations, locations, and freely definable tags. The filter criteria must be maintained throughout the scope filter to make it efficient. Empty filter entries can be hidden in the search result. | ||||
Automatic saving | |||||
Save intermediate states of the modeling automatically (Auto-Save) | The current modeling status is automatically saved at regular intervals to avoid data loss and possible duplication of work. | ||||
Copy and move content. | |||||
Copy process flow objects within a diagram | One or more process flow objects are marked and copied within the diagram. | ||||
Copy process flow objects to another diagram. | One or more process flow objects are marked and copied to another diagram. | ||||
Cut out process flow objects within a diagram (drag and drop) | One or more process flow objects are marked and moved within the diagram. | ||||
Cut process flow objects into another diagram (drag and drop) | One or more process flow objects are selected and moved to another diagram. |
Central property management | |
|---|---|
Model and define objects | Objects can be created in a hierarchy and/or list structure. Processes to which they are linked are listed. |
Detail objects with HTML editor attributes | Objects can be graphically designed and further detailed. |
Detailing objects with attributes | You can add further attributes to objects. |
Connecting objects with other objects | Specific mutual linking possibilities can represent dependencies of glossary elements. |
Release Object Versions | Objects can be released analogous to processes. If the author and the person responsible are the same person, release by this one person is possible. |
Create an object version. | New versions of (released) objects can be created to revise them. |
Consolidate objects | Redundant objects can be consolidated with others if they have not already been linked to processes. |
Filter objects | In the list view, objects can be filtered by name, and you can also search by name. |
Create IDs for objects. | Each versionable element can be assigned a unique ID number. The ID number to be generated can be defined so that, for example, a prefix also facilitates assignment to the information type. |
Structure objects hierarchically | The majority of objects can be displayed in a hierarchical structure, which can be deactivated individually (e.g., for systems). |
Disable architecture in the system facet | The hierarchical structure/architecture can be deactivated for the SYSTEMS facet. This serves to optimize performance. |
Organise inputs/outputs in your architecture | Objects can be sorted hierarchically and by category in the "Business Objects" facet. |
Store documents and link them to processes | Documents or other attachments can be added to the objects, which can then be assigned to processes. |
Evaluation groups Display connections to other objects/diagrams. | You can see which processes are used for each object. The objects are grouped for a clearer presentation. |
Organization Management | |
|---|---|
Define organizational models/diagrams. | Organization charts are modeled hierarchically. |
Automatically generate organizational models/charts graphically. | Organization charts are automatically displayed as graphics. |
Add and define positions in the organization model. | Positions can be defined and detailed within the organization. |
Detail organizations with attributes and related objects | Organizations are further specified by additional linked information. |
Define groups with positions and further details. | Groups (e.g., committees) and their AKVs can be created and assigned to corresponding organizations or positions. |
Location Management | |
Define and detail locations (locations) | Company locations can be created and linked to processes or organizations. They are also used as filter criteria (Scope Filter). |
Skill Management | |
Define skills centrally | Required skills can be defined and detailed. This is relevant for the exact specification of positions or roles. |
Maintain existing user skills. | Defined skills can be assigned roles clustered by work experience (newcomer to master). |
Maintain the required skills in the position. | Defined skills can be assigned to positions and clustered by work experience (newcomer to master). Job descriptions can be derived from this. |
BPMN 2.0 Process Modeling | |
|---|---|
Modeling processes according to the modeling standard BPMN 2.0 | Celonis Process Management supports the BPMN 2.0 modeling standard, enabling all business processes to be modeled, defined, and optimized transparently and in a uniform language. |
Extend processes with data objects and attributes (eBPMN 2.0 extension) | With the eBPMN 2.0 extension, further objects/object connections and standard attributes can be displayed. This offers the user different process detailing, publishing, and evaluation possibilities. |
Semantically guided modeling | The user is guided through the modeling process according to the BPMN 2.0 semantics. Only standard-compliant predecessor and successor objects are displayed for selection, so the initial training effort is to be classified as low. |
Modeling process interfaces | A process interface refers to a predecessor or successor process. They are usually used to connect processes at the same level. |
Modeling standardized process steps (Best Practice Tasks) | Repetitive, standardized process steps can be managed centrally in the repository and used in processes as often as required. |
Initially record processes in tabular form (automatic generation of graphics) | Processes are recorded quickly and clearly in the table view and can be checked immediately in the graphical view. |
Maintain and detail processes in tables (automatic graphics generation) | Processes are efficiently revised in the table view, or further details are added. |
Connect more objects with tasks (eBPMN) | Advanced BPMN 2.0 modeling, which includes the following objects: Requirements, Standards, Risks, Controls, etc. |
Maintain additional attributes | Further standard attributes can be maintained. See Standardized Meta-Model. |
Differentiate roles according to the duty to cooperate (RASCI) | Roles are categorized according to their responsibilities according to the RASCI method. Alternatively, the RACI method (without "S") can be selected (optional). |
Differentiate groups according to the duty to cooperate (RASCI) | Groups are categorized according to their responsibilities using the RASCI method. Alternatively, the RACI method (without "S") can be selected (optional). |
Connect process interfaces in the start and end event. | At the beginning and end of a process flow, predecessor or successor processes (usually at the same level) can be referenced. |
Link predecessor and successor processes | Processes can be assigned to predecessor and successor processes to clarify their position in the overall process landscape. |
Show BPMN Icons on process flow objects. | The process flow objects additionally display the symbol icons of the BPMN 2.0 modeling standard (optional) graphically. |
Store audit results | Audits are created as projects and assigned to the process world. Audit results and recommendations for action can also be stored. |
Advanced Process Modeling | |
|---|---|
Model and orchestrate end-to-end processes (E2E) and business transactions (scenarios) | End-to-end processes and comprehensive business transactions can be represented by logically sequential processes necessary to fulfill a specific customer need. |
Automatically update process layout during process modeling (Auto-Layout function) | The Auto-Layout function automatically updates the individual process flow objects and arranges them accordingly. |
Generate different process layouts automatically. | Possible process layouts are horizontal and vertical swimlane, horizontal and vertical lean process graphics (Lean), detailed process representation (eBPMN) with all object connections, horizontal and vertical swimlanes for IT systems (Application Swimlane), compressed process representation with all objects in matrix form (Process Matrix), and individually configurable profiles. |
Free graphical design of processes and process maps (HTML editor) | Symbols, text fields, shapes, or process flow objects can be modeled graphically and linked to the process house. Images can also be added. |
Upload and graphically visualize process workshop images. | Process workshop images (movement symbol slides) can be uploaded, edited, and saved as graphics. |
Locking and unlocking process processing | Exclusive editing of processes prevents simultaneous editing by several people and thus avoids possible data inconsistencies (optional). |
Language Management | |
Translate diagram and object details. | A dialog window allows easy and fast text input of process and object details in different languages. |
Automated translation of diagram and object details (Online Translation Service) | An integrated translation service makes it possible to translate process and object details at the push of a button. |
Automatic translation function with DeepL or Microsoft Translator | The integration of DeepL or Microsoft Translator guarantees automatic translation. Further translation services can be connected. |
Process maturity level | |
Determine the degree of process maturity. | Process maturity can develop in different stages (percentage from 'defined' to 'continuously optimized'). Thus, the maturity level of a process organization can be determined. This value is displayed both as an attribute and as a graphical dashboard. |
Aggregate process maturity level | The stored process maturity levels are aggregated and displayed on the upper level (structural process level). |
Process Validation | |
Validate process semantics (check modeling errors) | Before release, the application of BPMN 2.0 semantics is checked, and modeling errors are pointed out. If essential information is missing, the release workflow cannot be started, and warnings can be ignored. |
Evaluation of object links | |
|---|---|
Display connected objects in the process in a table | All objects connected to a process ('dependencies') are displayed in a table. From this view, connected objects can be edited efficiently and quickly and sent directly to the release. |
Audit Trail | |
Display life cycle diagrams (audit trail) of all process versions. | An audit trail is used for quality assurance and shows the entire history of process status changes. It is presented as a life cycle diagram in an audit-compliant manner. |
Versioning | |
Change attributes in released processes or objects | Certain attributes can be changed in released processes (only possible for selected user roles) |
Graphical process version comparison | |
|---|---|
Compare released and edited process versions (Process Comparison Editor) | Process versions are displayed side by side, and changes (deleted, added, modified) are graphically highlighted. |
Attribute comparison | Attribute changes are displayed in a dialog. Both the old and the new value of a changed attribute are displayed. |
Configurable home pages | |
Show individual entry pages (home pages) | Arranged entry pages facilitate quick navigation to specific processes or objects. The content can vary depending on the user role (e.g., viewer editor). |
Configurable fact sheets | |
Display fact sheets for all diagrams and object contents. | The fact sheet shows aggregated information about processes or objects and can be selected as a graphical view. The prerequisite is the administrator's previous configuration. |
Generate various graphical diagram representations. | Different process layouts (such as Swimlane horizontal/vertical, detailed, and Application Swimlane) can be selected and displayed by dropdown. |
See and open stored attachments easily. | Symbols on process steps or linked objects in viewer mode allow users to quickly recognize where attachments (e.g., further documents) are available. |
Organize process architecture | |
Display hierarchies in a navigation tree. | Hierarchically arranged processes or objects are displayed as a navigation tree through which you can navigate. |
Graphic visualization | |
Display several process levels in one surface side by side (2-levels) | The 2-level view is particularly suitable for processes containing sub-processes as it allows you to display processes and sub-processes side by side clearly and concisely. |
Process maps, graphical visualization | Process maps can be graphically modeled to provide overviews and direct navigation to the respective areas. |
browser print | |
Print diagrams directly via browser print | The quick print function allows process graphics to be printed quickly, except for profiles. |
Personal setting | |
Make personal user settings: Languages. | The primary and secondary languages can be selected individually, e.g., English as a primary language and the respective national language as a secondary language. |
Make personal user settings: List sizes. | The columns of the list view can be customized. |
Make personal user settings: Selected role. | Processes or objects can be displayed and categorized according to their assigned roles. Every Celonis Process Management user can set this individually. |
Global Search | |
|---|---|
Standard search: Search diagrams, objects, and information globally | The standard search is used to search processes, objects, and content for the beginnings of words entered. If several search terms are entered, they are linked with "AND." |
Expert search: Search/filter in specific attributes. | With the expert search, you can filter by the field where the search terms should occur (e.g., in the description text field). |
Expert search: Search with operators | The expert search allows operators "AND"/"OR" to combine or mutually exclude search terms. |
Expert search: Search with asterisks and quotation marks | In the expert search, you can also search for a partial term (using asterisks) or a compound term (using quotation marks). |
Direct access to the selected search result via a link in the details area | The selected search result (process or object) can be called directly via a link. |
List filtering | |
Filter search results in the list view | The search results list can be filtered according to additional, predefined criteria, such as type, version, author, etc. |
Global filtering | |
Apply scope (scope filter) to search results (can be activated/deactivated) | Restricting the search to the scope (Scope Filter) can further narrow the list of search results. |
Versioning | |
|---|---|
Create new diagrams or object versions. | When new processes or objects are created, new versions are automatically created. Several versions can be created and edited in parallel for processes. |
Delete diagrams and objects that are being edited. | Processes or objects that are in progress can be deleted. |
Create a new version of released processes and objects. | New versions must be created each time to revise released processes or objects. |
Automatic versioning of processes and objects | The version numbers for processes and objects are assigned automatically (integer for 'Released/Valid' (e.g. 1.0), decimal for 'In progress' (e.g. 1.1)). A manual adjustment is not possible. |
Release Workflow | |
Sharing: add more approver/approver groups (optional) | By default, the person responsible and, if applicable, the quality manager are stored as approvers. Additional approver/approver groups can also be configured (optional). For groups, the deposit of the number of permits required is possible. |
Release: Validate methodical rules in the process | Before release, the application of BPMN 2.0 semantics is checked, and modeling errors are pointed out. If essential information is missing, the release workflow cannot be started. |
Release: Send diagrams and objects to the release | After changing the status of a diagram or object, the release workflow starts automatically. The default sequence is Author - (QM) - Person responsible, with optional additional approver group: Author - (QM) - Approver - Responsible. |
Release: Ignore validation rule warnings to start the release (enable/disable) | Before release, the application of BPMN 2.0 semantics is checked, and modeling errors are pointed out. If these are "warnings," the release workflow can still be started. |
Release: Define diagram and object validity start "Valid from | The validity starts with processes and objects that can be freely defined. If no date is defined, the validity start is set to +14 days by default (configurable). There is no automatism when the validity end occurs. |
Release: Enter reason for revision (must have attributes) | Before a process can be sent to the approval workflow, the reason for the revision must be entered in a text field. The input of the reason is optional for objects. |
Release: Automatically forward requests for release to approvers | After a status change, the diagram/object to be checked is forwarded to the first approving instance (e.g., quality manager). In case of approval, the request is forwarded to the second instance for release, in case of rejection the release workflow is interrupted. In all cases, the author is informed. |
Approval: Inform approvers by e-mail about pending requests for approvals (optional) | It is also possible to automatically notify approvers by e-mail when a request for approval is submitted. |
Sharing: Automatically create and view requests (tasks) for approvers | Once the approval workflow is started, a request to the approver is automatically generated and displayed in his workspace. |
Release: Manage requests (tasks) | Outstanding or completed requests are displayed in an overview for further administration. |
Release: Call process/object directly | The process or object to be released can be accessed directly from the request via a link. |
Release: Approve or reject the release of processes and objects | The release of processes or objects can be approved or rejected at the push of a button. A reason must be entered in the text field in case of rejection. |
Set processes and objects to 'Expired. | A process or object can receive an "expired" status. The procedure is similar to the release workflow. Expired processes or objects can be reactivated. |