Self-service plan change documentation #9603
Conversation
NicoletaComan
changed the title
…mendix/docs into nc-olu-self-service-plan-change
| The app environment will remain on its current plan until the request is approved by a Mendix Admin. | ||
|
|
||
| {{% alert color="info" %}} | ||
| Changing plan consumes [Mendix Cloud Tokens](/control-center/entitlements/#cloud-tokens). Only one plan change request can exist per environment at a time. As a result, new requests cannot be submitted until the current one is completed. |
There was a problem hiding this comment.
It should be clear, but just for extra clarity I would say
| Changing plan consumes [Mendix Cloud Tokens](/control-center/entitlements/#cloud-tokens). Only one plan change request can exist per environment at a time. As a result, new requests cannot be submitted until the current one is completed. | |
| Changing plan consumes [Mendix Cloud Tokens](/control-center/entitlements/#cloud-tokens). Only one plan change request can exist per environment at a time. As a result, new requests cannot be submitted for the same environment until the current one is completed. |
|
|
||
| 7. Click **Submit Request** to submit your plan change request. After submission, the request appears in the [Control Center](/control-center/entitlements/#plan-change-requests-tab) for the [Mendix Admin](/control-center/company-settings/#mendix-admins) review. To view the list of approvers, click **Mendix Admin** at the bottom of the **New Plan** form. As a Technical Contact, you can [track and manage](#manage-plan-requests) your plan change requests from the [Request Overview](/developerportal/deploy/environments/#request-overview) tab on your app's environment's page. | ||
|
|
||
| The app environment will remain on its current plan until the request is approved by a Mendix Admin. |
There was a problem hiding this comment.
I think we could be clearer that the Admin approval only allocates the new plan to the environment. The actual environment will remain on the current plan until the upgrade is scheduled and completed.
| * Select a preferred date. | ||
| * The system will apply the change during the first available maintenance window after that date. For example, if you select May 22 and the next window is May 28, the change will occur on May 28. | ||
|
|
||
| After scheduling, the status changes to **Scheduled**. You can still click **Execute Now** at any time before the scheduled window to apply the change immediately. |
There was a problem hiding this comment.
Does Execute Now override the maintenance window? I don't think it does, I think it just puts it in the next maintenance window. But perhaps it does act immediately - in which case I think we should mention that it doesn't use the maintenance window?
There was a problem hiding this comment.
Yes, it overrides the maintenance window. Changes made to reflect that explicitly.
|
|
||
| #### New Features | ||
|
|
||
| * We have added a new beta feature in the [environment UI](/developerportal/deploy/environments/). This feature allows Technical Contacts to [change app's environment plan](/developerportal/deploy/change-plan/) to a higher-instance plan. |
There was a problem hiding this comment.
It isn't necessarily more instances - it can be just more memory or database size.
You use resources in your other release note, and that seems better.
|
I'm happy with the changes after my review. I'll leave it to you to publish this when the feature is ready. |
…mendix/docs into nc-olu-self-service-plan-change
|
Confirmed via Slack that the docs are ready for publishing. |
Feature to be released in the first week of June (~June 6).
Documentation to be provided for review by May 30.