...
If the toggle is on, any published update on the static page will reflect on a popup to be accepted by the customer in the app:
...
Note: You need Configurator needs to force one update in each of the static page that you want to show in the pop-up. It can accomodate a list of pages containing a link.
| Note |
|---|
What if FZ updated an agreement static page by mistake? The modal can be prompted improperly to the customer. To prevent any undue changes, there is a flag created that works within integration with sanity called “Switch Update Date Acceptance Agreement”. This flag has "Variations” for each environment that supports an array of Sanity Ids and UpdateAt dates, which overrides the value that is configured in Sanity. In other words, the date from the feature flag will be considered a priority over sanity. Despite of that, note that the app still stores (in the database) the customer acceptance date based on the Sanity static page updateAt. It means that this flag was not meant to be with updateAt dates that are larger than Sanity’s updateAt (or future dates). In other words, it was meant to be used when you want to bring back the configuration of the agreement updateAt date. This flag should be used with caution and should be normally turned off. |
Feature Account Updated Agreements
...