Rules of Precedence for the Enhanced Method for App Config Segmentation

Example

To take an example, if there are four app configs–Manager mPOS, Associate mPOS, Manager Fixed, Associate Fixed–with segmentation rules as follows:

Then, when a store user, Jane Smith, logs in on an iPad, and her role is Manager, her register would be served the Fixed POS Manager app config. Now, imagine that a fifth app config is added where the the Personnel criterion of its segmentation rule directly targets an associate with ID equal to “Jane Smith”. In this case, when Jane logs in, her register would receive the fifth app config, Jane Smith App Config.

App Launch (Before Login)

If a token is entered, the app config with the matching token is loaded. However, If no token is entered, the default app config for the merchant is loaded.

Associate Login (After Login)

When an associate logs in, the app config that will be served is the one with the highest-ranking (meaning most specific) segmentation rule that targets that associate and/or their register. Refer to the following table for that rank ordering.

Note A segmentation rule that targets a Device Type segment, an Associate segment, and a Store segment is the highest-ranking rule possible.