A topic as a package, instead of three templates that are supposed to belong together
An access request is a process, a rule chain and a checklist, and the three have to fit together. Until now they were created and maintained separately. A domain package bundles them into one package that models a topic as a whole. It is created and changed in the system, released or locked per tenant, introduced for a tenant with all building blocks instantiated, tracked in progress, continuously updated and finally archived. A vendor catalogue ships ready-made packages; your own arise in self-service.
When a domain package is introduced for a tenant, all its building blocks are created there as objects of their own: the process from the template, the rule chain, the checklist. The tenant works with its copies; the package remains the source for the next version.
A package from the vendor catalogue is not automatically available everywhere. It is released or locked per tenant, so that an association, a consultancy or a group parent controls which organisation receives which topic.
How far a tenant has got with a topic is shown by the package itself: which building blocks are introduced, which version is running, what is open since the last update.
A topic is introduced as a whole and updated as a whole, instead of three templates drifting apart.
Schedule a no-obligation demo – we will show you the module with your own use cases.
