@NikitaKamai and team,
I want to clarify that there are cases where the app will be presented as Pinned:
- a customer site is located in
USbased on their origin of access when the site was created → the customer installed the app after theUSlocation was supported in the descriptor via theregionBaseUrlstag → the customer then moved (or moves) the product to theUSlocation - a product has been moved to the
USlocation → the customer installed the app after theUSlocation was supported in the descriptor via theregionBaseUrlstag
The same applies to the other supported regions by the app.
This is because the app is currently supporting data residency pinning based on the descriptor via the regionBaseUrls tag.
If, instead, a customer moves the product to a different location from the one where the site was created, the app will only be shown as Eligible once it supports data residency migrations.
In the case of this app, once data residency migration is supported, the Not Eligible option will only be shown for those regions that are not supported in the descriptors.
If your plan is to support all regions and the migration option, Not Eligible will not be one of the possible options for this app.
As Sean shared above, we are looking into options for a better representation of the app’s status. In the meantime, please provide the answers to the Privacy & Security questions for customers to review the data residency offering of the app.
Hope this helps,
Caterina