You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/control-center/entitlements/approval-requests.md
+4-14Lines changed: 4 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,28 +21,18 @@ It is made up of the **Active Requests** and **Resolved Requests** tabs.
21
21
This tab displays all requests that have not yet been acted upon, with the following details for each request:
22
22
23
23
***Request ID** – The unique identification code of the request.
24
-
***Request Type** – The type of request being submitted, which can be one of the following:
25
-
26
-
***Plan Upgrade**
27
-
***Private Connectivity**
28
-
24
+
***Request Type** – The type of request being submitted.
29
25
***Requester** – The name of the person who made the request.
30
26
***Requested Date** – The date when the request was submitted.
31
27
***Actions** – Allows you to **Reject** or **Approve** the request.
32
-
Click the **Details** button next to the request to access further details, such as the request description, and the environment for which the request was made.
33
-
34
-
You can filter requests by status and type.
28
+
Click the **Details** button next to the request to access further details.
35
29
36
30
## Resolved Requests
37
31
38
32
This tab displays all requests that have been acted upon, with the following details for each request:
39
33
40
34
***Request ID** – The unique identification code of the request.
41
-
***Request Type** – The type of request being submitted, which can be one of the following:
42
-
43
-
***Plan Upgrade**
44
-
***Private Connectivity**
45
-
35
+
***Request Type** – The type of request being submitted.
46
36
***Requester** – The name of the person who made the request.
47
37
***Requested Date** – The date when the request was submitted.
48
38
***Status** – The status of the request, which can be one of the following:
@@ -54,7 +44,7 @@ This tab displays all requests that have been acted upon, with the following det
54
44
55
45
***Reviewer** – The name of the person who reviewed and approved, canceled, or rejected the request.
56
46
***Resolved Date** – The date when the request was acted upon, and its status was changed.
57
-
***Action** – Click the **Details** button next to the request to access further details, such as the request description, and the environment for which the request was made.
47
+
***Action** – Click the **Details** button next to the request to access further details.
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/change-plan.md
+34-6Lines changed: 34 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ To change an environment's plan, follow these steps:
48
48
3. On the **Environments** page, click the **Overview** tab to view your environments.
49
49
4. Find your target environment.
50
50
5. Use the **Expand** ({{< icon name="chevron-down" >}}) toggle to view detailed information about each environment, such as the environment resources and deployed package.
51
-
6. In the environment resource section, click **Change Plan**.
51
+
6. In the environment resources section, click **Change Plan**.
52
52
7. On the left side of the form that appears, review your current plan details. These include:
53
53
***Name** – Plan name.
54
54
***Environment** – Plan environment (such as, staging or acceptance).
@@ -69,6 +69,23 @@ To change an environment's plan, follow these steps:
69
69
Changing plan consumes [Mendix Cloud Tokens](/control-center/cloud-tokens/#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.
70
70
{{% /alert %}}
71
71
72
+
### Plan Change Request Status {#plan-change-status}
73
+
74
+
This diagram illustrates the lifecycle of a plan change request, from its submission to its final resolution (rejected, completed, or failed).
A Technical Contact initiates the process by submitting a plan change request.
79
+
80
+
1.**Pending Approval** – After submission, the request enters a **Pending Approval** status. The request is then sent to a Mendix Admin for review.
81
+
* If the Mendix Admin rejects the request, its status changes to **Rejected**.
82
+
* If the Mendix Admin approves the request, the status changes to **Pending Schedule**.
83
+
2.**Pending Schedule** – The plan change application is awaiting scheduling by the Technical Contact.
84
+
3.**Scheduled** – Plan change is scheduled for the next maintenance window.
85
+
4.**In Progress** – The plan change is actively being applied to the environment.
86
+
5.**Completed** – Plan change was successfully applied to the environment
87
+
6.**Failed** – The plan change did not complete successfully.
88
+
72
89
## Managing Plan Requests {#manage-plan-requests}
73
90
74
91
The **Change Requests** tab allows Technical Contacts to view all submitted plan change requests (both past and current) and track pending request status.
@@ -79,15 +96,26 @@ To access it:
79
96
2. Click **Environments** on your app.
80
97
3. Open the **Change Requests** tab.
81
98
82
-
For detailed information on the **Change Requests** tab, refer to the [Change Requests](/developerportal/deploy/environments/#change-requests) section in *Environments and Deployment*.
99
+
Plan change requests have **Plan Upgrade** as the **Request Type**. For more information on the **Change Requests** tab, refer to the [Change Requests](/developerportal/deploy/environments/#change-requests) section in *Environments and Deployment*.
83
100
84
-
This diagram shows the progress of the request status from plan change submission to fulfilled (approved, rejected, completed, or failed):
101
+
### Plan Change Requests Details {#change-requests-action}
Click **Details** on any plan change request to view the **name** of the requester, reviewer details and other request information, including:
104
+
105
+
* Status of the request
106
+
* Current plan
107
+
* Requested plan
108
+
* Reason for resizing
109
+
* Date of request creation
110
+
* Date the request was scheduled
111
+
* Request ID
112
+
* Request type
113
+
* App name
114
+
* Environment
87
115
88
-
### Available Actions by Status {#available-actions-by-status}
116
+
####Available Actions by Status {#available-actions-by-status}
89
117
90
-
Depending on the request's status, Technical Contacts can perform the following actions:
118
+
In the **Request Details** page, depending on the request's [status](#plan-change-status), Technical Contacts can perform the following actions:
91
119
92
120
***Pending approval** – Click **Cancel Request** to cancel the entire request.
93
121
***Pending schedule** – Click **Cancel Request** to cancel the entire request, or click **Schedule Change** to set execution timing for when the approved plan will be applied. For more details on how to schedule a plan change, see [Scheduling a Plan Change](#scheduling-a-plan-change).
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/environments.md
+3-27Lines changed: 3 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -176,39 +176,15 @@ If you are the [Technical Contact](/developerportal/general/app-roles/#technical
176
176
177
177
On the **Change Requests** tab, the Technical Contact can view details of all past and current [Change Plan](/developerportal/deploy/change-plan/) requests and perform certain actions based on the current request status.
178
178
179
-
For each submitted plan change request you can see the following information:
179
+
For each submitted request, the following information is available:
180
180
181
181
***Request Type** – Type of change requested
182
182
***Environment** – The environment the plan change was requested for (such as, acceptance or production)
183
183
***Current Plan** – The environment's existing plan
184
184
***Requested Plan** – The plan requested for change
***Pending schedule** – Approved by Mendix Admin, but plan change application not yet scheduled by the Technical Contact
189
-
***Scheduled** – Plan change scheduled for the next maintenance window
190
-
***In progress** – Plan change is being applied
191
-
***Completed** – Mendix Admin has approved the change, Technical Contact has scheduled and applied the changes, and the new plan has been successfully applied to the environment
192
-
***Rejected** – Request was denied
193
-
***Failed** – Plan change did not complete successfully
194
-
***Action** – Shows more details of each plan request and provides options based on the request status. For more information, see [Change Requests Action](#change-requests-action)
Click **Details** on any request to view the **name** of the requester and the reviewer and other request details, including:
199
-
200
-
* Status of the request
201
-
* Current plan
202
-
* Requested plan
203
-
* Reasons for resizing
204
-
* Date of request creation
205
-
* Date the request was scheduled
206
-
* Request ID
207
-
* Request type
208
-
* App name
209
-
* Environment
210
-
211
-
For more information, refer to the [Available Actions by Status](/developerportal/deploy/change-plan/#available-actions-by-status) section in *Changing Your Plan in Mendix Cloud*.
186
+
***Status** – Current request state
187
+
***Action** – Shows more details of each request and provides options based on the request status
Copy file name to clipboardExpand all lines: content/en/docs/releasenotes/control-center/_index.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,12 @@ To see the current status of the Mendix Control Center, see [Mendix Status](http
21
21
* We have introduced **Private Connectivity**, a zero-trust security infrastructure which helps you manage connections between your Mendix Cloud apps and internal resources, bypassing the public internet. It allows you to create secure networks through which your apps can safely access internal databases and services hosted on-premises or in cloud environments, without exposing them publicly.
22
22
Refer to [Private Connectivity](/control-center/private-connectivity/) for background details and architecture, then read through [Configuring and Using Private Connectivity](/control-center/configure-private-connectivity/) to learn how to create and manage your own private networks.
23
23
24
+
### November 9, 2025
25
+
26
+
#### Improvements
27
+
28
+
* The [Approval Requests](/control-center/approval-requests/) page is now divided into two distinct tabs: **Active Requests** and **Resolved Requests**. This allows you to easily stay on top of all approval requests created for your company.
0 commit comments