Rules of Precedence for the Traditional Method for App Config Segmentation

When loading app configs on the POS app, the system prioritizes configurations assigned directly to associates, followed by role-specific configurations, and finally the app's default settings. This ensures that associates always use the most appropriate configuration, enhancing efficiency and accuracy in store operations.

The traditional approach follows a specific order of precedence when loading app configs on the POS app, with #1 holding the highest priority:

  1. If an associate has an App Config assigned to them, the POS app will load that configuration. This assignment can be configured in Store Management | Associate Management | Associates | Create/Edit | App Configuration.

  2. If an associate is assigned a role (Store Management | Associate Management | Associates | Create/Edit | Associate Roles), and that role has an App Config assigned to it, the POS app will use the role-specific configuration. This assignment can be configured in Store Management | Associate Management | Associate Roles.

  3. If neither of the above configurations is set, the POS app will default to loading the configuration designated as the app's default.

Note
Note Note: The use of tokens can have different precedence depending on the app environment.