diff --git a/content/en/docs/deployment/mendix-cloud-deploy/environments-details-new.md b/content/en/docs/deployment/mendix-cloud-deploy/environments-details-new.md index a84fd44b41a..861da5c6ab9 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/environments-details-new.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/environments-details-new.md @@ -14,7 +14,7 @@ This feature is in Public Beta. For more information, see [Beta Releases](/relea {{% /alert %}} {{% alert color="info" %}} -While this feature is in Beta, you can use the **New Theme** toggle to switch between this new UI and the [legacy UI](/developerportal/deploy/environments-details/). For apps running on Kubernetes, the new UI displays by default and cannot be toggled off. +While this feature is in Beta, you can switch to the new UI by clicking **Upgrade to the New Experience**. For apps running on Kubernetes, the new UI displays by default and you cannot switch back to the [legacy UI](/developerportal/deploy/environments-details/). {{% /alert %}} ## Introduction @@ -25,16 +25,18 @@ To open the **Environment Details** page, go to [Apps](https://sprintr.home.mend {{% alert color="info" %}}You must have permissions for **Transport Rights** or **Access to Monitoring** to view the **Environment Details** page. For details on configuring permissions, see [Node Permissions](/developerportal/deploy/node-permissions/).{{% /alert %}} -The **Environment Details** page shows information about the selected environment. You can use this page to manage and debug several aspects of the environment. The page has eight tabs: **General**, **Model Options**, **Network**, **Log Levels**, **Runtime**, **Maintenance**, **Tags**, and **Services**. +The **Environment Details** page shows information about the selected environment and includes eight tabs: **General**, **Model Options**, **Network**, **Log Levels**, **Runtime**, **Maintenance**, **Tags**, and **Services**. You can also use this page to manage and debug several aspects of the environment. ## Actions {#actions} -On the top right side of the screen, there are buttons and a **More Options** menu that you can use to perform various actions. Some action buttons are visible when your app is running, some are visible when your app is stopped, and some are always visible. +On the top right side of the screen, there are buttons and a **More Options** ({{% icon name="three-dots-menu-horizontal"%}}) menu that you can use to perform various actions. Some action buttons are visible when your app is running, some are visible when your app is stopped, and some are always visible. {{% alert color="info" %}}Depending on your permissions, you may see only some of the action buttons described below. You can adjust your permissions settings on the [Permissions](/developerportal/deploy/node-permissions/) tab of your app's **Environments** page.{{% /alert %}} {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/actions.png" alt="The buttons and More Options menu" >}} +### Running App Actions + When your app is running, you can perform the following actions: * **Deploy** – This deploys an application to the environment. @@ -43,49 +45,24 @@ When your app is running, you can perform the following actions: * **More Options**: * **Show Logged in Users** – This shows all users who are logged in to your app. * **Change Admin Password** – This changes the password for the built-in [administrator](/refguide/administrator/) account. The new password is applied immediately, without the need for a restart, and forces the administrator to pick up any new [roles](/refguide/administrator/#user-role) assigned in the app deployment package. - * **View Live Log** – This shows a live log for your application. It is identical to the **View Live Log** button on the [Logs](/developerportal/operate/logs/) page. - * **Show Debugger Information** – This shows the settings needed to connect the debugger in Studio Pro to your app. For more information on debugging in the cloud, see [How To Debug Microflows Remotely](/refguide/debug-microflows-remotely/). + * **View Live Logs** – This shows a live log of your application and performs the same action as the **View Live Log** button on the [Logs](/developerportal/operate/logs/) page. + * **Show Debugger Info** – This shows the settings needed to connect the debugger in Studio Pro to your app. For more information on debugging in the cloud, see [How To Debug Microflows Remotely](/refguide/debug-microflows-remotely/). * **Show Running Now** – You can use this to monitor all actions that are currently running in your environment. For more information, see [Running Now](/developerportal/deploy/mxcloud-runningnow/). -When your app is stopped, you can perform this set of action buttons instead: +### Stopped App Actions + +When your app is stopped, you can perform these actions: * **Deploy** – This deploys an application to the environment. * **Start App** – This starts the application. -* **Stop App** – This stops the application. * **More Options**: - * **Clear Environment** – This allows you to empty all the data from your database and, optionally, remove the app and file storage from the environment as well. For more information, see [Clearing an Environment](#clear-environment). - * **View Live Log** – This shows a live log for your application. It is identical to the **View Live Log** button on the [Logs](/developerportal/operate/logs/) page. + * **Clear Environment** – This allows you to empty all the data from your database and, optionally, remove the app and file storage from the environment. For more information, see [Clearing an Environment](#clear-environment). + * **View Live Logs** – This shows a live log of your application. {{% alert color="info" %}} During a [maintenance window](/developerportal/deploy/maintenance-windows/), you cannot start, restart, or stop your app. {{% /alert %}} -## The General Tab - -In the **Application Status** section of the **General** tab, you can find the following information about your environment: - -* **Status** - * {{% icon name="checkmark-circle-filled" color="green" %}} – The application in this environment is running. - * {{% icon name="subtract-circle-filled" color="gray" %}} – No application has been started yet in this environment, or it has been turned off. - * {{% icon name="alert-circle-filled" color="yellow" %}} – The application in this environment is experiencing some difficulties; check the alerts page or logs for more information. - * {{% icon name="remove-circle-filled" color="red" %}} – The application in this environment is unstable and probably not usable anymore. -* **Running since** – the date the app was started, if it is running -* **Name** – the type of environment (Acceptance, Production, Test, or the name of a [flexible environment](/developerportal/deploy/mendix-cloud-deploy/#flexible-environments)); for more information, see the [Naming of Environments](#naming) section below -* **Url** – the URL of the app -* **Project ID** – the unique identifier of the app -* **Environment ID** – the unique identifier of the environment -* **Custom domains** – any [custom domains](/developerportal/deploy/custom-domains/) of the app; to add a new domain, click **Add Custom Domain** -* **Java Version** – the JDK version selected for the MDA that is deployed to the environment -* **Studio Pro Target** – a **Yes** or **No** value indicating whether the environment is the designated deployment target from Studio Pro; for more information, see [Studio Pro Deployment Settings](/developerportal/deploy/studio-deployment-settings/). -* **Plan** – the type of plan covered by your license (for more information, see the [Overviews](/developerportal/deploy/environments-details/#overviews) section below) -* **Instances** – a summary of the number and memory allocation of instances of the environment (for more information, see the [Scaling](#scaling) section below) -* **Database Version** – the PostgreSQL version supporting the database -* **Region** – the region of the data center where the app is hosted (for the full list of Mendix Cloud regions, see [Outgoing IP](/developerportal/deploy/mendix-ip-addresses/#outgoing)) -* **Secondary Backup Location** – the region where the backup is stored (for more information, see [Data Location](/developerportal/operate/backups/#data-location) in the *Backups* documentation) -* **Mendix Cloud Version** – the version of Mendix Cloud where the app is hosted - -At the bottom of the page, there are three sections showing the deployment package details, plan details, and license. These are described in detail below in the [Overviews](#overviews) section. - #### Clearing an Environment {#clear-environment} The **Clear Environment** button lets you clear your environment so that you can use it for another purpose. This option is only available if the environment is stopped. @@ -110,7 +87,32 @@ To clear your environment, follow these steps: 3. Confirm that you want to clear your environment by typing the indicated text (*clear database* or *clear model and database*, depending on which option you selected). 4. Click **Clear Environment**. -### Naming of Environments – Flexible Environments in Mendix Cloud {#naming} +## The General Tab + +In the **General** tab, you can find four sections that provide information about the [application status](#application-status), [deployment package details](#deployment-package-details), [plan details](#plan-details), and [license](#license). + +### Application Status + +In the **Application Status** section of the **General** tab, you can find the following information about your environment: + +* **Status** + * {{% icon name="checkmark-circle-filled" color="green" %}} – The application in this environment is running + * {{% icon name="subtract-circle-filled" color="gray" %}} – No application has been started yet in this environment, or it has been turned off + * {{% icon name="alert-circle-filled" color="yellow" %}} – The application in this environment is experiencing some difficulties; check the alerts page or logs for more information + * {{% icon name="remove-circle-filled" color="red" %}} – The application in this environment is unstable and probably not usable anymore +* **Project ID** – the unique identifier of the app +* **Environment ID** – the unique identifier of the environment +* **Running Since** – the date the app was started, if it is running +* **Name** – the type of environment (Acceptance, Production, Test, or the name of a [flexible environment](/developerportal/deploy/mendix-cloud-deploy/#flexible-environments)); for more information, see the [Naming of Environments](#naming) section below +* **URL** – the URL of the app +* **Custom Domains** – any [custom domains](/developerportal/deploy/custom-domains/) of the app; to add a new domain, click **Add Custom Domain** +* **Studio Pro Target** – a **Yes** or **No** value indicating whether the environment is the designated deployment target from Studio Pro; for more information, see [Studio Pro Deployment Settings](/developerportal/deploy/studio-deployment-settings/) +* **Java Version** – the JDK version selected for the MDA that is deployed to the environment +* **Database Version** – the PostgreSQL version supporting the database +* **Region** – the data center region where the app is hosted (for the full list of Mendix Cloud regions, see [Outgoing IP](/developerportal/deploy/mendix-ip-addresses/#outgoing)) +* **Data Backup Secondary Location** – the region where the backup is stored (for more information, see [Data Location](/developerportal/operate/backups/#data-location) in the *Backups* documentation) + +#### Naming of Environments – Flexible Environments in Mendix Cloud {#naming} If you are the app's [Technical Contact](/developerportal/general/app-roles/#technical-contact), you can rename the environments. @@ -118,52 +120,56 @@ To rename an environment, follow these steps: 1. Click **Change** next to the name of the environment. 2. Enter the new name, which must meet the following requirements: - * Consists of at least two characters - * Consists of only alphanumeric characters and hyphens (`a-z`, `A-Z`, `0-9`, and `-`) - * Does not begin or end with a hyphen + * Consists of at least two characters. + * Consists of only alphanumeric characters and hyphens (`a-z`, `A-Z`, `0-9`, and `-`). + * Does not begin or end with a hyphen. {{% alert color="info" %}} After you rename an environment, it may take up to 15 minutes before you can access an app via its URL. This is because the URL includes the name of the environment, and the old value needs to be removed from the DNS cache. It may take considerably longer for the change to be visible worldwide. {{% /alert %}} -### Scaling {#scaling} - -To see the options for changing scaling, scroll down to the **Instances** row of the **Application Settings** section of the **General** tab, and then click **Change scaling**. +### Deployment Package Details -In the **Change scaling** dialog box, there are two sliders that you can control: - -* Use the **Instances** slider to increase or decrease the number of instances - * The instances are meant for improved resiliency and increased processing power - * The minimum amount of RAM per instance is 1 GiB; you can spread the RAM among four instances if you have more than 1 GiB of RAM -* Use the **Memory per instance** slider to increase or decrease the memory amount per instance +In this section, you can find information about the deployment package that is loaded into the environment: -The **Total Allocated Memory** is a process circle that shows how much memory is currently used for scaling. +* **Name** of the deployment package +* **Version** of the deployment package +* **Runtime** version of Mendix used to create the app +* **Size (MB)** of the deployment package +* **Upload Date** of the deployment package -{{% alert color="info" %}}The maximum value for **Memory per instance** equals the **Total Allocated Memory** of your plan, but it cannot exceed 32 GiB. The maximum number of instances depends on the **Memory per instance** you have chosen; the maximum number of instances equals the total allocated memory divided by the memory per instance.{{% /alert %}} +### Plan Details -If you have 1 GiB RAM of total allocated memory, you have one instance available to store your memory. To scale your memory over multiple instances, you need more memory. +This section shows details of the plan that applies to this environment: -For more information, see [Scaling Your Environment](/developerportal/deploy/scale-environment/). +* **Name** – the type of plan associated with your license +* **Instances** – the number and memory allocation of instances in the environment (for more information, see the [Scaling](#scaling)) +* **Memory** – the total allocated memory of the plan +* **Database Plan Cores** – the CPU cores allocated to the database +* **Database Plan Space** – the storage capacity of the database +* **Database Plan Memory** – the database's RAM size +* **File Storage** – available size for storing blobs +* **Backup Storage** – total size available for database backup files +* **Multi-AZ Enabled** – a **Yes** or **No** value indicating whether multiple availability zones are enabled -### Overviews {#overviews} +#### Scaling {#scaling} -At the bottom of the **General** tab, there are three sections showing the deployment package details, plan details, and license. +To see the options for changing scaling, click **Scale** on the **Instances** row. This will open the **Change Scaling** dialog box, which includes two sliders that you can control: -#### Deployment Package Details +* Use the **Instances** slider to increase or decrease the number of instances + * The instances are meant for improved resiliency and increased processing power + * The minimum amount of RAM per instance is 1 GiB; you can spread the RAM among four instances if you have more than 1 GiB of RAM +* Use the **Memory per instance** slider to increase or decrease the memory amount per instance -In this section, you can find information about the deployment package that is loaded into the environment: +The **Total Allocated Memory** is represented by a progress circle that shows how much memory is currently used for scaling. -* **Name** of the deployment package -* **Version** of the deployment package -* **Runtime** version of Mendix used to create the app -* **Size (MB)** of the deployment package -* **Upload date** of the deployment package +{{% alert color="info" %}}The maximum value for **Memory per instance** equals the **Total Allocated Memory** of your plan, and it cannot exceed 32 GiB. The maximum number of instances depends on the **Memory per instance** you have chosen; the maximum number of instances equals the total allocated memory divided by the memory per instance.{{% /alert %}} -#### Plan Details +If you have 1 GiB RAM of total allocated memory, you have one instance to use your memory. To scale your memory over multiple instances, you need more memory. -This section shows details of the plan that applies to this environment. +For more information, see [Scaling Your Environment](/developerportal/deploy/scale-environment/). -#### License +### License The license overview contains the following information: @@ -173,9 +179,9 @@ The license overview contains the following information: ## The Model Options Tab {#model-options} -On this tab, you can edit the following model options: constants and scheduled events. +On this tab, you can edit the model options for constants and scheduled events. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/model-options.png" class="no-border" >}} +{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/model-options.png" >}} ### Constants {#constants} @@ -183,11 +189,11 @@ In this section, you can view the configured constants. Constants are used to de To fill in a new value, select the constant and click **Edit** to bring up the **Edit Constant** dialog box. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/edit-constant.png" class="no-border" >}} +{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/edit-constant.png" >}} -In the **Edit Constant** dialog box, you can change the constant value using the **New value** field. +In the **Edit Constant** dialog box, you can change the constant value using the **New Value** field. -You can also set **Mask** to **Yes**. This changes the display settings for **Current value** and **New value**; if masking is enabled, all screens in the Mendix Portal (and in Excel if you export the constants) conceal these values and display a string of asterisks in their place. This lets you keep your constants secret from users who do not have edit rights. +You can also set **Mask** to **Yes** to change the display settings for **Current Value** and **New Value**. When masking is enabled, all screens in the Mendix Portal (and in Excel if you export the constants) conceal their values and display asterisks in their place. This keeps your constants secret from users with no edit rights. {{% alert color="info" %}} For the changes to take effect, you must restart your application. @@ -201,13 +207,13 @@ For more information, see [Constants](/refguide/constants/). #### Comparing Constants -You can export the constant values to an Excel file by clicking **Export to Excel**, or compare the values across different environments by clicking **Compare and Edit**. +You can export the constant values to an Excel file by clicking **Export To Excel**, or compare the values across different environments by clicking **Compare and Edit**. ### Scheduled Events In this section, you can view your configured scheduled events. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/edit-event.png" class="no-border" >}} +{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/edit-event.png" >}} If you select a scheduled event and click **Toggle**, you can switch the scheduled event off and on. @@ -223,19 +229,19 @@ For more information, see [Scheduled Events](/refguide/scheduled-events/). On the **Network** tab, you can manage the elements described below. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/network.png" class="no-border" >}} +{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/network.png" >}} ### Custom Domains {#custom-domains} -* **Domain name** +* **Domain Name** * **Certificate** * **Expire** date You can perform the following actions: * **Add** – provide the domain name and select the certificate from a drop-down menu -* **Edit** -* **Delete** +* **Edit** – update the domain details +* **Delete** – remove domain For more information, see [Certificates](/developerportal/deploy/certificates/) and [Custom Domains](/developerportal/deploy/custom-domains/). @@ -264,15 +270,15 @@ There are three types of values for these headers: * Choose a value from a drop-down menu: - {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/http-header-dropdown.png" alt="Selecting a value" width=350 class="no-border" >}} + {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/http-header-dropdown.png" alt="Selecting a value" width=450 >}} * Choose a value from a drop-down menu and specify a URL: - {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/http-header-url.png" alt="Specifying a URL" width=350 class="no-border" >}} + {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/http-header-url.png" alt="Specifying a URL" width=450 >}} * Enter the required values as a string: - {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/http-header-string.png" alt="Entering a value" width=350 class="no-border" >}} + {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/http-header-string.png" alt="Entering a value" width=450 >}} The changes to the headers are implemented when the app is redeployed. @@ -362,7 +368,7 @@ For each range where you define safelisted IP addresses and ports, you can enter * **Protocol** – Select whether the safelisting is for **TCP**, **UDP**, or **ALL** traffic. * **Description** – Enter an optional description of this IP range (for example, which API it supports). -Click **Save** to save your range. The new values are applied within a few minutes without needing an app restart. +Click **Save** to apply your range. The new values take effect within a few minutes without needing an app restart. #### Valid IP Ranges {#valid-ip} @@ -378,11 +384,11 @@ IP addresses must be within the following ranges: ### Path-Based Access Restrictions {#path-based-restrictions} -You can restrict access to your application by means of Client Certificates or IP ranges. +You can restrict access to your application using Client Certificates or IP ranges. -The root path (`/`) restricts access to the entire application. Settings for a specific path override the implicitly inherited profile from other non-root paths. +The root path (`/`) restricts access to the entire application. If a specific path has it own settings, those will override the profile inherited from other non-root paths. -Custom access restriction profiles are managed at the application level. They can be reused for all environments (acceptance, production, etc). +Custom access restriction profiles are managed at the application level and can be reused across all environments (acceptance, production, etc). The **Path Based Access Restrictions** overview contains the following information: @@ -405,9 +411,9 @@ Add client certificates (in the PKCS12 format) or certificate authorities (in th ## The Log Levels Tab {#log-levels} -Log levels are used to distinguish the log messages. Log levels highlight the highest-priority log messages so that they can be prioritized accordingly. +Log levels are used to distinguish log messages. Log levels highlight the highest-priority log messages so that they can be prioritized accordingly. -{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/log-levels.png" class="no-border" >}} +{{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/log-levels.png" >}} Custom log nodes appear in the list only after a message has been logged to them. For more information, see [Log Message](/refguide/log-message/#log-node-name). @@ -422,7 +428,7 @@ When using the **Log Levels** tab, bear in mind the following considerations: * For custom nodes, log nodes become visible when your app is restarted and after messages have been logged to them. * If you change the log level, this level will continue to be used even if you later restart your app. * If you change the log level, the startup logs (the logs that are created while starting the runtime, including the logs that the after-startup microflow generates) are not affected. It is not possible to change the log level of the startup logs for apps hosted on Mendix Cloud. -* For an application running a single instance, any changes are applied immediately to the application. +* For an application running a single instance, changes are applied immediately to the application. * For an application running more than one instance, the changes can only be applied after a restart of the app. This is because it is not possible to instruct the load balancer to set the log level for a specific running instance. * Log levels may not persist across restarts if you change them outside the Mendix Portal (for example, using an app module). @@ -432,7 +438,7 @@ The log level types are as follows: | -------- | ------ | ----------- | | Trace | | Provides highly detailed information. Trace level messages are written only to logs. | | Debug | | Provides detailed information, typically of interest only when diagnosing problems. | -| Info | | Confirms that things are working as expected. | +| Info | Blue | Confirms that things are working as expected. | | Warning | Orange | Indicates that something unexpected happened or warns about an upcoming problem (for example, "disk space low"). The application is still working as expected. | | Error | Red | Indicates a serious problem that prevented the application from performing some function. | | Critical | White text, red background | Indicates that a serious error has occurred; the application may be unable to continue running. | @@ -449,9 +455,9 @@ On the **Runtime** tab, you can add **Custom Runtime Settings** and **Custom Env Use the **Custom Runtime Settings** section to perform the following actions: -* **Add** a new runtime setting with a new value +* **Add** a new runtime setting * **Edit** the runtime setting -* **Delete** the runtime settings +* **Delete** the runtime setting For more information about runtime settings, read the [Runtime Customization](/refguide/custom-settings/) and [Advanced Custom Settings in Mendix Runtime](/refguide/tricky-custom-runtime-settings/) documentation. @@ -500,11 +506,11 @@ Click **Add** and select **Supported** to choose from the following variables: * The value of this variable is in the format `Module.Entity.Attribute`, where `Module` is the module of your app that contains the `Entity` that is a specialization of `System.User` and `Attribute` is the attribute that contains the email address of the user. * If you have multiple specializations of `System.User`, you can specify the values in comma-separated format (that is, `Module1.Entity1.Attribute1,Module2.Entity2.Attribute2,…,ModuleN.EntityN.AttributeN`). In the following example, there are two specializations identified: `Administration.Account.Email,MendixSSO.MendixSSOUser.EmailAddress`. -To support features that are in beta, click **Add** and select **Unsupported**. Then, you can add an unsupported environment variable. Unsupported environment variables can only be used for controlling Mendix beta features. If you are involved in using a beta feature, you will be informed what **Name** and **Value** to enter. +Unsupported environment variables can only be used to control Mendix beta features. To configure an unsupported variable, click **Add** and select **Unsupported**. If you are using a beta feature, you will be informed what **Name** and **Value** to enter. ## The Maintenance Tab {#maintenance-tab} -You can use the **Maintenance** tab to view information about planned maintenance, as well as configure your preferred maintenance window. +Use the **Maintenance** tab to view information about planned maintenance and configure your preferred maintenance window. {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/maintenance.png" alt="Viewing the Maintenance tab" >}} @@ -519,7 +525,7 @@ You can view and change the preferred maintenance. For more information about ma ### Planned Maintenance -When a maintenance operation is planned, it appears under **Planned Maintenance**. Each task card will show the purpose of the maintenance, when it is scheduled and its status. +When a maintenance operation is planned, it appears under **Planned Maintenance**. Each task card will show the purpose of the maintenance, when it is scheduled, and its status. {{% alert color="info" %}} Maintenance topics (for example, "PostgreSQL 14 Upgrade") have a predefined period (start date and deadline). Once the start date is reached, you will get the option to execute it immediately, regardless of the Maintenance Window configured for the environment, by clicking **Execute Now**. @@ -529,9 +535,9 @@ The status of a maintenance task can be one of: * **Succeeded** – the maintenance task was successful * **Failed** – the maintenance task failed and the environment requires intervention - * Our engineering team should already have been notified about the failed task. If you are still experiencing issues, please create a support ticket with [Mendix Support](https://support.mendix.com/hc/en-us) + * Our engineering team will have been notified about the failed task. If you are still experiencing issues, please create a support ticket with [Mendix Support](https://support.mendix.com/hc/en-us) * **Incomplete** – the maintenance task was unsuccessful and no changes were applied - * You can operate the environment as usual. Our engineering team should already have been alerted about the incomplete task and will take the appropriate action (which may involve rescheduling the task). + * You can operate the environment as usual. Our engineering team will have been alerted about the incomplete task and will take the appropriate action (which may involve rescheduling the task) * **Ineligible** – the maintenance task was unsuccessful because one or more starting criteria were not met * You can operate the environment as usual. This can happen, for example, if the database of your environment was scheduled to be upgraded but it is already on the target version @@ -556,9 +562,9 @@ If you want to add, edit, or delete a tag, make the change on the **Tags** tab a ## The Services Tab {#services} -You can enable and disable custom services for individual environments of your app. The service that you want to enable must have been enabled for the app by its [Technical Contact](/developerportal/general/app-roles/#technical-contact). For more information, see [Services](/developerportal/deploy/environments/#services). +In the **Services** tab, the [Technical Contact](/developerportal/general/app-roles/#technical-contact) decides the custom services for each environment. You can then enable and disable these services for individual environments as needed. -In the **Services** tab, the [Technical Contact](/developerportal/general/app-roles/#technical-contact) can decide which custom services can be used in each environment of this app. +The [Technical Contact](/developerportal/general/app-roles/#technical-contact) must first enable a service for the app before you can use it. For more information, see [Services](/developerportal/deploy/environments/#services). {{< figure src="/attachments/deployment/mendix-cloud-deploy/environments-details-beta/services.png" >}} diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/general.png b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/general.png index e923ec949f1..424d2137575 100644 Binary files a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/general.png and b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/general.png differ diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/http-header-string.png b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/http-header-string.png index 85bd03ce01f..781fc4fa17a 100644 Binary files a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/http-header-string.png and b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/http-header-string.png differ diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/log-levels.png b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/log-levels.png index dd2c4de5245..dd212f6ac4d 100644 Binary files a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/log-levels.png and b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/log-levels.png differ diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/model-options.png b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/model-options.png index c0398ecba88..8a9e851755e 100644 Binary files a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/model-options.png and b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/model-options.png differ diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/network.png b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/network.png index ed390447b95..4caed9f4789 100644 Binary files a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/network.png and b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/network.png differ diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/runtime.png b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/runtime.png index 32a65c01152..ae4c5e1df8e 100644 Binary files a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/runtime.png and b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/runtime.png differ diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/services.png b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/services.png index c8cefc8b1d9..c1a962fb076 100644 Binary files a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/services.png and b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/services.png differ diff --git a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/tags.png b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/tags.png index 5177b191f68..df5ba974e2c 100644 Binary files a/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/tags.png and b/static/attachments/deployment/mendix-cloud-deploy/environments-details-beta/tags.png differ