Skip to main content

Celonis Product Documentation

Do's and Don’ts overview
  • Administrate the process architecture

    • Set up and modify categories (including permissions)

    • Create, modify, and version main processes.

    • Release and expire main processes and sub-processes

    • Delete and move main and sub-processes within their architecture.

    • ! Modify Responsibles who are automatically inherited from the level above!

  • Administrate objects

    • Create, modify, and version objects in tabular or hierarchical structure.

    • Release and expire objects

    • Delete and move objects within their hierarchy

    • Consolidate objects (NOTE: only objects in version 0.1 can be consolidated)

  • Change attributes in released processes without versioning (audit-proof)

    • Attributes that can be edited without re-release are responsible, author, start/end of validity, scope-filter (responsible organizations, locations, tags)

  • Set up Customer Experience Management

    • Create, modify, and delete touchpoints

    • Create, modify, and delete sales channels

    • Create, modify, and delete stakeholders

  • Apply sorting function

  • Create or generate uploaded documents for guidelines/manuals as pdf.

  • Maintain ID Provider

  • Clean up processes, objects, and hierarchy to keep them up to date.

  • Clean up ‘orphaned’ view (should be empty)

  • NOTE: we recommend not to create more than 50 elements per level in hierarchies (processes/objects)

  • No more than one architect should consolidate objects in the same navigation simultaneously. Otherwise, there is a risk of consolidating objects mutually, which can lead to data inconsistencies.

  • No more than one architect should move or delete elements in architectures/hierarchies (of processes or objects) simultaneously (e.g., categories or processes/objects that have not yet been released) - under no circumstances should elements be moved in parallel in the same branch. This also applies to moving from the ‘orphaned’ view

  • When deleting subtrees (processes, objects, categories, or similar), all child elements should have been deleted or moved before. The same applies to setting the status to ‘expired’