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/deployment/mendix-cloud-deploy/connecting-external-resources.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,8 +57,8 @@ Contact your Mendix Admin if the resource you want is not available on the list.
57
57
{{% /alert %}}
58
58
59
59
6. Select the specific resource you want your application environment to connect to.
60
-
7. Click **Send Request** to submit your connection request for approval. All submitted connection requests appear in the [Control Center](/control-center/configure-private-connectivity/) for the Mendix Admin review.
61
-
8.[Track and manage](#manage-connection-requests) your connection requests from the [Connections](/developerportal/deploy/environments-details/#connections) section on the application's **Network** tab.
60
+
7. Click **Save** to submit your connection request for approval. All submitted connection requests appear in the [Control Center](/control-center/configure-private-connectivity/) for the Mendix Admin review.
61
+
8.[Track and manage](#manage-connection-requests) your connection requests from the [Change Requests](/developerportal/deploy/environments/#change-requests) tab on your app's environment's page.
62
62
63
63
{{% alert color="info" %}}
64
64
If this is the first connection approved for an application environment, you must redeploy that environment for the connection to become active and usable.
@@ -73,11 +73,11 @@ This diagram shows the progress of the request status from when the connection r
73
73
Once a Technical Contact submits a connection request, it enters a **Pending Approval** status. The request is then sent to a Mendix Admin for review:
74
74
75
75
* If the Mendix Admin rejects the request, its status becomes **Rejected**.
76
-
* If the Mendix Admin approves the request, its status becomes **Approved**, and the connection becomes active.
76
+
* If the Mendix Admin approves the request:
77
+
* In the **Change Requests** tab of the Environments page, the status becomes **Completed**.
78
+
* In the **Connections** section of the **Network** tab, its status becomes **Approved**.
77
79
* A Mendix Admin can also revoke an already approved connection, which will change its status back to **Rejected**.
78
80
79
-
The connection status is visible in the **Connections** section of the **Network** tab.
The [Connections](/developerportal/deploy/environments-details/#connections) section on the application's **Network** tab allows Technical Contacts to view all connections for the environment, track pending request statuses, and delete established connections.
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/environments.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -174,14 +174,12 @@ If you are the [Technical Contact](/developerportal/general/app-roles/#technical
174
174
175
175
### Change Requests Tab {#change-requests}
176
176
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.
177
+
On the **Change Requests** tab, the Technical Contact can view details of all past and current requests for either the [Plan](/developerportal/deploy/change-plan/)or [Connection](/developerportal/deploy/connecting-to-external-resource/)requests and perform certain actions based on their current status.
178
178
179
179
For each submitted request, the following information is available:
180
180
181
181
***Request Type** – Type of change requested
182
-
***Environment** – The environment the plan change was requested for (such as, acceptance or production)
183
-
***Current Plan** – The environment's existing plan
184
-
***Requested Plan** – The plan requested for change
182
+
***Environment** – The environment the change was requested for (such as, acceptance or production)
185
183
***Submitted on** – Request submission date
186
184
***Status** – Current request state
187
185
***Action** – Shows more details of each request and provides options based on the request status
0 commit comments