Skip to content

Self-service plan change documentation #9603

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 22 commits into from
Jun 12, 2025

Conversation

NicoletaComan
Copy link
Collaborator

@NicoletaComan NicoletaComan commented May 28, 2025

Feature to be released in the first week of June (~June 6).
Documentation to be provided for review by May 30.

@NicoletaComan NicoletaComan self-assigned this May 28, 2025
@NicoletaComan NicoletaComan changed the title Updated Entitlements page for self-service plan change Self-service plan change documentation May 28, 2025
@NicoletaComan NicoletaComan marked this pull request as ready for review May 30, 2025 11:49
Copy link
Collaborator

@MarkvanMents MarkvanMents left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I've made a few comments, but some may be irrelevant as I haven't actually played with the new pages.

Thanks.

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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be clear, but just for extra clarity I would say

Suggested change
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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@MarkvanMents
Copy link
Collaborator

I'm happy with the changes after my review. I'll leave it to you to publish this when the feature is ready.

@NicoletaComan
Copy link
Collaborator Author

Confirmed via Slack that the docs are ready for publishing.

@NicoletaComan NicoletaComan merged commit 7796b65 into development Jun 12, 2025
2 checks passed
Copy link
Collaborator

@OlufunkeMoronfolu OlufunkeMoronfolu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants