Skip to main content
Customization Hierarchy

Learn the hierarchy of configuration setup for different entities

e
Written by eLogii
Updated over a week ago

When setting up different task workflows, there is a hierarchy eLogii follows when applying data.

One example of this setting up PODs, where it’s possible to add them on customer and task level, as well as in Configuration.

This means if there are different preferences for PODs set in each of these, eLogii will follow the hierarchy to apply the adequate workflow.

The following is the order in which the settings will be applied:

1. Task level

2. Customer level

3. Configuration level

For example, if PODs in Configuration are set and a different set is applied to a customer selected for a task, the system will retrieve the ones from the customer’s profile.

Also, if a customer is selected for a task, but in the Advanced section of the task form, different POD actions have been set up, the system will use those and disregard the ones applied to the customer.

This workflow also applies to all other data such as customer location, contact information, etc.

Did this answer your question?