Hi @RhysDiab ,
You didn’t specify whether it’s a server, DC or Cloud app, but since you mentioned approving the upgrade, I assume it’s Cloud.
In that case, the price change is applied automatically to all customers, they don’t have to approve anything. And even if you add new scopes to your app descriptor, which will force customers to manually accept the upgrade, the new price will still be applied to customers who refused the upgrade.
So if I want users to manually approve the upgrade, I should add new scopes (ie EMAIL)?
I guess I’m still a little unsure if:
There’s a way for users to go back to the previous version of the add-on if they prefer it.
There’s a way to test the old version of the descriptor using a private token. It seems only the previous 2 versions can use a private token and any version older than that can no longer be tested. I’m thinking this might be necessary if there are breaking changes to ACE ect…