Merge pull request mendix#9018 from mendix/RoelandSalij-patch-2

Update mendix-ai-assistance/_index.md

Author: MarkvanMents

content/en/docs/apidocs-mxsdk/apidocs/deployment/deploy-api-1.md

@@ -399,11 +399,11 @@ An object with the following key-value pairs:
 
 | HTTP Status | Error code | Description |
 | --- | --- | --- |
+| 200 | ALREADY_STARTED | Cannot start app. App is already running. |
 | 400 | INVALID_APPID | Invalid AppId |
 | 404 | APP_NOT_FOUND | App not found |
 | 500 | NO_MDA_HAS_BEEN_DEPLOYED | Cannot start app. There is no MDA deployed. |
 | 500 | APP_ALREADY_HAS_A_STARTING_JOB | Cannot start app. There is already a starting job id found. |
-| 500 | ALREADY_STARTED | Cannot start app. App is already running. |
 
 ##### Example Output
 

content/en/docs/appstore/use-content/platform-supported-content/modules/SAML/_index.md

@@ -599,4 +599,4 @@ Your SAML IdP can consume the following endpoints at your app. Typically the SP-
     {{% alert color="info" %}}You must log into the Mendix Platform to see the lecture above.{{% /alert %}}
 * [Advanced configuration for SAML](/appstore/modules/saml/advanced-configuration/)
 * [Reference Guide for SAML IdP Configuration](/appstore/modules/saml/idp-attributes/)
-* [OIDC SSO](/appstore/modules/oidc/)
+* [OIDC SSO](/appstore/modules/oidc/)

content/en/docs/appstore/use-content/platform-supported-content/modules/SAML/advanced_configuration.md

@@ -60,4 +60,4 @@ If you are using a custom URL, see [How Do I Get my SAML Metadata or CommunityCo
 ## Read More
 
 * [OIDC SSO](/appstore/modules/oidc/)
-* [Reference Guide for SAML IdP Configuration](/appstore/modules/saml/idp-attributes/)
+* [Reference Guide for SAML IdP Configuration](/appstore/modules/saml/idp-attributes/)

content/en/docs/appstore/use-content/platform-supported-content/modules/SAML/idp_attributes.md

@@ -201,4 +201,4 @@ For information, see the [User Provisioning](/appstore/modules/saml/#user-provis
 ## Read More
 
 * [SAML](/appstore/modules/saml/)
-* [Advanced configuration for SAML](/appstore/modules/saml/advanced-configuration/)
+* [Advanced configuration for SAML](/appstore/modules/saml/advanced-configuration/)

content/en/docs/appstore/use-content/platform-supported-content/modules/aws/amazon-bedrock.md

@@ -31,7 +31,6 @@ You must have the latest [GenAI Commons](/appstore/modules/genai/commons/) versi
 
 To ensure that your app can connect to Bedrock, you must also install and configure the [Encryption module](/appstore/modules/encryption/#configuration). 
 
-
 ### Licensing and Cost
 
 This connector is available as a free download from the Mendix Marketplace, but the AWS service to which is connects may incur a usage cost. For more information, refer to AWS documentation.
@@ -118,7 +117,7 @@ To build a simple microflow that uses the ChatCompletions operation to send a si
 2. Create a new microflow and name it, for example, *AmazonBedrockChatCompletions*.
 3. Add a **Microflow call** from the **Toolbox** and choose microflow *AmazonBedrockConnector.BedrockDeployedModel_Get*
 4. Double-click it to configure its parameters.
-    1.  For the **ModelID** parameter, enter the model id of the LLM you want to send a message to. The model id of Claude 3.5 Sonnet is *anthropic.claude-3-5-sonnet-20240620-v1:0*.
+    1. For the **ModelID** parameter, enter the model id of the LLM you want to send a message to. The model id of Claude 3.5 Sonnet is *anthropic.claude-3-5-sonnet-20240620-v1:0*.
     2. Click **OK**.
 5. In the **Toolbox**, search for the **Chat Completions (without history)** activity in the *GenAI (Generate)* and drag it onto your microflow.
 6. Double click on the activity to see its parameters.

content/en/docs/appstore/use-content/platform-supported-content/modules/database-connector-mx10.md

@@ -255,4 +255,4 @@ Execute queries as you would with supported databases, and retrieve responses in
 
 {{% alert color="info" %}}
 By default, autocommit is set to false for design time queries.
-{{% /alert %}}
+{{% /alert %}}

content/en/docs/appstore/use-content/platform-supported-content/modules/mobile-sso.md

@@ -150,7 +150,7 @@ When you are building the native mobile app using **Build Native Mobile App** op
 
 The following subsections show how to configure your *Entra ID or Okta IdP*:
 
-#### Configuring IdP for Entra ID
+#### Configuring IdP for Entra ID {#idp-for-intra}
 
 1. On the [Microsoft Entra ID](https://portal.azure.com/#home) portal, select **App Registrations**.
 2. Click **New registration**, provide required information, and click **Register**.
@@ -255,7 +255,7 @@ The following subsections show how to configure your *Entra ID or Okta IdP*:
 1. Add the required scopes such as, `openid`, `profile`, and `email`.
 1. Save the configuration and you can login into the application using Okta SSO.
 
-## Testing and Troubleshooting
+## Testing
 
 ### IdP Integration
 
@@ -265,6 +265,12 @@ After adding the IdP details to the web page, the IdP sign in tab is visible on
 
 Click **IdP login** to redirect to the IdP sign in page. After successful authentication, you will be directed to the user landing page, indicating successful integration of the Mobile SSO module.
 
+## Troubleshooting
+
 ### Sign-in Failure Error
 
 When tryin to sign in multiple times, you may receive a sign-in failure error message. To resolve this error, check your network connection and try signing in again.
+
+### 401 Error
+
+If you encounter a 401 error, follow the process described in the [Configuring IdP for Entra ID](#idp-for-intra) section above for applications deployed using the **Build Native Mobile App**.

content/en/docs/appstore/use-content/platform-supported-content/modules/oidc.md

@@ -252,6 +252,9 @@ If you are configuring navigation for web/responsive apps and want to allow your
 
 In addition, administrators will need to have access to configure OIDC and also manage end-users. You can do this by including the pages `Administration.Account_Overview` and `OIDC.OIDC_Client_Overview` into the app navigation, or a separate administration page.
 
+If you are testing phone web and phone web offline locally, use the URLs `http://localhost:8080/?profile=Phone` and 
+`http://localhost:8080/?profile=PhoneOffline`, respectively. For more information, see the [Example of profile selection](/refguide/mobile/introduction-to-mobile-technologies/progressive-web-app/#example-of-profile-selection) section of *Progressive Web App*.
+
 ### Setting Encryption Key
 
 Follow the instructions to [set an encryption key in the Encryption module](/appstore/modules/encryption/#configuration). The constant to set is called `Encryption.EncryptionKey` and should be a random value 32 characters long. This key will be used to encrypt and decrypt values.

content/en/docs/community-tools/mendix-exams/manage-exam-seats.md

@@ -55,11 +55,11 @@ In the **Invited Students** section, you can check the status of the invitations
 
 An invitation can have one of the following statuses:
 
-- **NOT ACCEPTED YET**: The student has not accepted the invitation. You can still [remind the student](#remind-student) or [withdraw the invitation](#withdraw-invitation).
-- **REGISTERED**: The student has registered but has not yet completed the exam.
-- **UNDISCLOSED**: The student has taken the exam but has not shared the result. A student can choose not to share the result with the exam admin when they register for the exam.
-- **CERTIFIED**: The student has passed the exam and is certified.
-- **FAILED**: The student has taken the exam and failed. 
+* **NOT ACCEPTED YET**: The student has not accepted the invitation. You can still [remind the student](#remind-student) or [withdraw the invitation](#withdraw-invitation).
+* **REGISTERED**: The student has registered but has not yet completed the exam.
+* **UNDISCLOSED**: The student has taken the exam but has not shared the result. A student can choose not to share the result with the exam admin when they register for the exam.
+* **CERTIFIED**: The student has passed the exam and is certified.
+* **FAILED**: The student has taken the exam and failed. 
 
 ### Reminding Students to Accept an Invitation {#remind-student}
 

content/en/docs/deployment/mendix-cloud-deploy/backups/restore-backup.md

@@ -163,6 +163,8 @@ This folder contains the *db.backup* file, which is a PostgreSQL dump file creat
 If the dump does not use the custom format, then the restore will fail.
 
 The dump must be created with `pg_dump` version 1.14 or below, which is currently bundled with PostgreSQL 13, 14, and 15. If it is created with a later version, then the upload will fail.
+
+You can find the exact version of PostgreSQL each environment of your application is using on the [General](/developerportal/deploy/environments-details/#general-tab) tab of each environment's  **Environment Details** page.
 {{% /alert %}}
 
 #### tree Folder{#tree-folder}