Merge branch 'mendix:development' into development

Author: strategicalliances

assets/js/anchor.js

@@ -1,46 +1,54 @@
-/*
-  * Copyright 2018 Google LLC
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-     https://www.apache.org/licenses/LICENSE-2.0
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
- */
+'use strict';
 
- (function ($) {
-     'use strict';
+document.addEventListener('DOMContentLoaded', () => {
+    // Append anchor links to headings in Markdown
+    const article = document.getElementsByTagName('main')[0];
+    if (!article) {
+        return;
+    }
 
-     // Headers' anchor link that shows on hover
-     $(function () {
-         // append anchor links to headings in markdown.
-         var article = document.getElementsByTagName('main')[0];
-         if (!article) {
-             return;
-         }
-         var headings = article.querySelectorAll('h1, h2, h3, h4, h5, h6');
-         headings.forEach(function (heading) {
-             if (heading.id) {
-                 var a = document.createElement('a');
-                 // set visibility: hidden, not display: none to avoid layout change
-                 a.style.visibility = 'hidden';
-                 // [a11y] hide this from screen readers, etc..
-                 a.setAttribute('aria-hidden', 'true');
-                 // material insert_link icon in svg format
-                 a.innerHTML = ' <svg xmlns="http://www.w3.org/2000/svg" fill="currentColor" width="24" height="24" viewBox="0 0 24 24"><path d="M0 0h24v24H0z" fill="none"/><path d="M3.9 12c0-1.71 1.39-3.1 3.1-3.1h4V7H7c-2.76 0-5 2.24-5 5s2.24 5 5 5h4v-1.9H7c-1.71 0-3.1-1.39-3.1-3.1zM8 13h8v-2H8v2zm9-6h-4v1.9h4c1.71 0 3.1 1.39 3.1 3.1s-1.39 3.1-3.1 3.1h-4V17h4c2.76 0 5-2.24 5-5s-2.24-5-5-5z"/></svg>';
-                 a.href = '#' + heading.id;
-                 heading.insertAdjacentElement('beforeend', a);
-                 heading.addEventListener('mouseenter', function () {
-                     a.style.visibility = 'initial';
-                 });
-                 heading.addEventListener('mouseleave', function () {
-                     a.style.visibility = 'hidden';
-                 });
-             }
-         });
-     });
+    // Select all headings in the article
+    const headings = article.querySelectorAll('h1, h2, h3, h4, h5, h6');
+    headings.forEach((heading) => {
+        if (heading.id) {
+            const a = document.createElement('a');
+            a.setAttribute('aria-hidden', 'true');
+            a.classList.add('anchor-icon'); // Add anchor-icon class (_styles_project.scss)
+            a.innerHTML = `<svg xmlns="http://www.w3.org/2000/svg" fill="var(--bs-body-color)" width="20" height="20" viewBox="0 0 32 32"><path d="M18.9001 7.22C20.5201 5.6 23.1601 5.6 24.7801 7.22C26.4001 8.84 26.4001 11.48 24.7801 13.1L20.4001 17.48L21.8101 18.89L26.1901 14.51C28.5901 12.11 28.5901 8.2 26.1901 5.8C23.7901 3.4 19.8801 3.4 17.4801 5.8L13.1001 10.18L14.5101 11.59L18.8901 7.21L18.9001 7.22Z"/><path d="M10.16 28C11.74 28 13.32 27.4 14.52 26.2L18.9 21.82L17.49 20.41L13.11 24.79C11.49 26.41 8.85002 26.41 7.23002 24.79C5.61002 23.17 5.61002 20.53 7.23002 18.91L11.61 14.53L10.2 13.12L5.82002 17.5C3.42002 19.9 3.42002 23.81 5.82002 26.21C7.02002 27.41 8.60002 28.01 10.18 28.01L10.16 28Z"/><path d="M9.44971 21.1336L21.124 9.45927L22.5383 10.8735L10.8639 22.5478L9.44971 21.1336Z"/></svg>`;
+            a.href = '#' + heading.id;
 
- }(jQuery));
+            // Append anchor element to heading
+            heading.appendChild(a);
+
+            // Show icon when hovering over heading
+            heading.addEventListener('mouseenter', () => {
+                a.style.display = 'inline-block';
+            });
+
+            // Hide icon when mouse leaves heading
+            heading.addEventListener('mouseleave', () => {
+                a.style.display = 'none';
+            });
+
+            // Initialize Bootstrap tooltip
+            const tooltip = new bootstrap.Tooltip(a, {
+                title: 'Copy link to clipboard',
+                placement: 'right',
+                trigger: 'hover focus'
+            });
+
+            // Add on-click behavior
+            a.addEventListener('click', (event) => {
+                event.preventDefault(); // Prevent scrolling
+                const href = a.href;
+                navigator.clipboard.writeText(href); // Copy to clipboard
+                window.history.pushState({}, document.title, href); // Update URL
+                // Update tooltip text
+                const tooltipInner = document.querySelector('div.tooltip-inner');
+                if (tooltipInner) {
+                    tooltipInner.textContent = 'Copied!';
+                }
+            });
+        }
+    });
+});

assets/scss/_styles_project.scss

@@ -100,6 +100,19 @@
     padding-bottom: 0px;
 }
 
+// Anchor icon styling for anchor.js
+
+.anchor-icon {
+    display: none;
+    padding: 0rem .3rem .1rem .3rem;
+    margin: -.5rem 0rem -.5rem .3rem;
+    border-radius: 4px;
+}
+
+.anchor-icon:hover {
+    background: $gray-light;
+}
+
 // _code.scss -  Code formatting
 
 .td-content {
@@ -574,7 +587,6 @@ nav.foldable-nav {
 // _tables.scss - from https://github.com/twbs/bootstrap/blob/v4.6.2/scss/_tables.scss
 
 .table {
-    width: 90%; // NK - adjusted width to match rest of content
     margin-bottom: $spacer;
     color: $table-color;
     background-color: $table-bg; // Reset for nesting within parents with `background-color`.

assets/scss/_variables_project.scss

@@ -165,5 +165,8 @@ $navbar-dark-hover-color: rgba($white, 0.5) !default;
 $navbar-dark-active-color: $white !default;
 $navbar-dark-disabled-color: rgba($white, 0.25) !default;
 
+// Tooltip
+$tooltip-bg: $secondary;
+
 // The yiq lightness value that determines when the lightness of color changes from "dark" to "light".
 $yiq-contrasted-threshold: 200 !default;

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

@@ -951,22 +951,36 @@ To solve this issue, follow these steps:
 
 After the status of the models changes to **Access Granted**, you can use it with the Amazon Bedrock connector.
 
-### 5.2 Error code 404 - Resource Not Found
+### 5.3 Error code 403 - AccessDeniedException
 
-When invoking a model the error code *404 - Resource Not Found* indicates that the targeted resource was not found.
+When invoking a model, the error code *403 - Access denied* indicates that you do not have access to the targeted resource.
 
-#### 5.2.1 Cause
+#### 5.3.1 Cause
 
 Possible root causes for this error include the following:
 
 * You do not have access to the model in the specified AWS region.
+
+#### 5.3.2 Solution
+
+To solve this issue, ensure that you have selected an AWS Region where you have model access. You can see an overview of the models accessible to you in the AWS Management Console, in the [Model Access](https://us-west-2.console.aws.amazon.com/bedrock/home?#/modelaccess) section of your Amazon Bedrock environment.
+
+### 5.4 Error code 404 - ResourceNotFoundException
+
+When invoking a model, the error code *404 - Resource not found* indicates that the targeted resource was not found.
+
+#### 5.4.1 Cause
+
+Possible root causes for this error include the following:
+
+* The model which you are trying to invoke is not available in your specified AWS region.
 * The model which you are trying to invoke is deprecated.
 
-#### 5.2.2 Solution
+#### 5.4.2 Solution
 
 To solve this issue, verify the following:
 
-1. Ensure that you have selected an AWS Region where you have model access. You can see an overview of the models accessible to you in the AWS Management Console, in the [Model Access](https://us-west-2.console.aws.amazon.com/bedrock/home?region=us-west-2#/modelaccess) section of your Amazon Bedrock environment.
+1. Ensure that you have selected an AWS Region where the targeted model exists. You can see an overview of the models accessible to you in the AWS Management Console, on the [Overiew page](https://us-west-2.console.aws.amazon.com/bedrock/home?#/overview) of your Amazon Bedrock environment. Make sure the region specified in the AWS Console matches the region you have configured in Mendix. 
 2. Ensure that the model that you have selected is not deprecated and that the *model-id* is currently available in Amazon Bedrock.
 
 ## 6 Appendix
@@ -1011,3 +1025,16 @@ The guardrail feature will allow you to:
 The watermark detection feature will make it possible to tell if an image has been created using Amazon Titan.
 
 More information about guardrails can be found in this [AWS blogpost](https://aws.amazon.com/blogs/aws/guardrails-for-amazon-bedrock-helps-implement-safeguards-customized-to-your-use-cases-and-responsible-ai-policies-preview/) and in the [AWS documentation](https://aws.amazon.com/en/bedrock/guardrails/).
+
+#### 6.3 Advanced Prompts for Agents
+
+By default, an agent is configured with the following base prompt templates, one for each step in the agent sequence:
+
+* Pre-processing
+* Orchestration 
+* Knowledge base response generation 
+* Post-processing
+  
+By customizing the prompt templates and modifying these configurations, you can fine-tune your agent's accuracy. Additionally, you can provide custom examples for a technique known as few-shot prompting. This involves providing labeled examples for specific tasks, which further enhances the model's performance in targeted areas. For more information about advanced prompts, see [Advanced prompts](https://docs.aws.amazon.com/bedrock/latest/userguide/advanced-prompts.html) in the AWS documentation.
+
+You can also use placeholder variables in agent prompt templates. For example, in the orchestration prompt template, the *$prompt_session_attributes$* placeholder variable can be used to ingest the information from the `PromptSessionAttribute` entity into the prompt, if it was specified as part of the `InvokeAgentRequest`. For more information about placeholder variables available in agent prompt templates, see [Prompt placeholders](https://docs.aws.amazon.com/bedrock/latest/userguide/prompt-placeholders.html) in the AWS documentation.

content/en/docs/appstore/modules/document-generation.md

@@ -22,7 +22,7 @@ The [PDF Document Generation](https://marketplace.mendix.com/link/component/2115
 ### 1.2 Limitations
 
 * Currently, PDF is the only supported document export format.
-* For deployment, currently we support [Mendix Public Cloud](/developerportal/deploy/mendix-cloud-deploy/), [Mendix for Private Cloud Connected](/developerportal/deploy/private-cloud/), and [On-Premises](/developerportal/deploy/on-premises-design/). Other deployment scenarios will be supported at a later stage.
+* For deployment, currently we support [Mendix Public Cloud](/developerportal/deploy/mendix-cloud-deploy/), [Mendix Cloud Dedicated](/developerportal/deploy/mendix-cloud-deploy/), [Mendix for Private Cloud Connected](/developerportal/deploy/private-cloud/), and [On-Premises](/developerportal/deploy/on-premises-design/). Other deployment scenarios will be supported at a later stage.
 
     {{% alert color="info" %}}For all deployment types except for on-premises, we only support apps that allow bi-directional communication with the PDF Service in the Mendix Public Cloud.{{% /alert %}}
 
@@ -66,6 +66,7 @@ Follow the instructions in [Using Marketplace Content](/appstore/overview/use-co
 
     1. [Running on Mendix Cloud](#run-on-mendix-cloud) using the PDF service in the Mendix Public Platform. This option is available for apps that are deployed to the following environments:
         * [Mendix Public Cloud](/developerportal/deploy/mendix-cloud-deploy/)
+        * [Mendix Cloud Dedicated](/developerportal/deploy/mendix-cloud-deploy/)
         * [Mendix for Private Cloud Connected](/developerportal/deploy/private-cloud/)
 
     2. [Running On-Premises](#run-on-premises) using a local version of the PDF service. This option is available for apps that are deployed to the following environments:
@@ -96,7 +97,7 @@ To allow the module to send and receive document generation requests on your Men
 
 1. Enable the DocGen request handler.
 
-   {{% alert color="info" %}}This step is only for licensed apps on the Mendix Public Cloud. If your app is deployed on [Mendix for Private Cloud Connected](/developerportal/deploy/private-cloud/), skip this step and make sure that the */docgen/* path is accessible.{{% /alert %}}
+   {{% alert color="info" %}}This step is only for licensed apps on the Mendix Public Cloud or Mendix Cloud Dedicated. If your app is deployed on [Mendix for Private Cloud Connected](/developerportal/deploy/private-cloud/), skip this step and make sure that the */docgen/* path is accessible.{{% /alert %}}
 
 2. Register your app environments.
 
@@ -108,7 +109,7 @@ The steps for each procedure are described in the sections below.
 
 1. Make sure that you have configured the **DocumentGeneration** module as described in the [Configuration](#configuration) section.
 
-2. Make sure that you have the application [deployed to Mendix Public Cloud](/developerportal/deploy/mendix-cloud-deploy/#deploy-app-mendix-cloud).
+2. Make sure that you have the application [deployed to the desired Mendix Cloud](/developerportal/deploy/mendix-cloud-deploy/#deploy-app-mendix-cloud).
 
 3. To allow the module to send and receive document generation requests in your Mendix Cloud environments, enable the DocGen request handler as follows:
 
@@ -361,6 +362,7 @@ In case you encounter any issues while [registering your app environment](#regis
 | **Invalid Developer Credentials** | "Invalid developer credentials" | The developer information as provided in the **Email** and **API key** fields is incorrect. | Verify that the provided email address in the **Email** field matches the username in your Mendix developer profile, and also that the API key that is being used is correct and still active. |
 | **Invalid App** | <ul><li>"Invalid app"</li></ul><ul><li>"App not found for the given user"</li></ul> | The provided apple ID is either incorrect or the developer (based on the **Email** and **API key** fields) does not have access to this app. | Verify that the **App ID** field is correct, and also that the developer account corresponding to the details entered in the **Email** and **API key** fields has access to the given app. |
 | **Invalid Application URL** | "Application URL does not match any of the environment URLs" | The app corresponding to the **App ID** field does not contain any environment that matches the URL given in the **Application URL** field. | Verify that the **App ID** and **Application URL** fields are correct. |
+| **Invalid Deployment Type** | <ul><li>"Application should be deployed on Mendix Public Cloud"</li></ul><ul><li>"Deployment type should be Mendix Public Cloud"</li></ul> | The provided **Application URL** is either incorrect or the chosen **Deployment type** is incorrect for this app. | Verify that the entered **Application URL** is correct and that you have chosen the correct **Deployment type**. |
 | **Unable to Reach App** | <ul><li>"Domain verification failed, unable to reach app"</li></ul><ul><li>"Domain verification failed, unable to reach verification endpoint"</li></ul><ul><li>"Domain verification failed, verification endpoint inactive" </li></ul>| The cloud service was unable to reach your app. | Verify that you enabled the `ASu_DocumentGeneration_Initialize` after startup microflow and also allowed access to the DocGen request handler. For more information, see [Enabling the DocGen Request Handler](#enable-docgen). |
 | **Invalid Token** | "Domain verification failed, invalid token" | The cloud service was able to reach your app, but could not verify that this app is currently trying to register. | Verify that the application URL matches the current environment. |
 | **Other Errors** |<ul><li>"Project verification failed"</li></ul><ul><li>"Domain verification failed, invalid response from verification endpoint"</li></ul><ul><li>"Domain verification failed for unknown reason"</li></ul> | An unexpected error occurred. | Verify that your app was not restarted by someone else during the registration process. If not, submit a ticket in the Mendix Support Portal. |
@@ -395,7 +397,7 @@ We recommend that you temporarily set the log level of the `DocumentGeneration`
 
 #### 6.2.3 Cloud Service Errors
 
-In case you encounter the message "Unable to generate document, service response code: 401" in the logs of your cloud environment, the request was rejected by the document generation service. This could be caused by the following reasons:
+In case you encounter the message "Unable to generate document for request `<requestId>`, service response code: 401" in the logs of your cloud environment, the request was rejected by the document generation service. This could be caused by the following reasons:
 
 * The scheduled event **SE_AccessToken_Refresh** is not enabled, which caused the registration to expire. Enable the scheduled event and [register](#register-app) the affected app environment again.
 * The URL of the app environment does not match the URL that was provided during registration. This could be the case when you requested a change to the URL of your app, or after restoring a database backup from one environment to another. [Register](#register-app) the affected app environment (or environments) again.

content/en/docs/appstore/modules/mobile-sso.md

@@ -38,7 +38,7 @@ This module has the following limitations:
 
 * Mendix sessions in the mobile app do not time out.
 * Mobile SSO module does not support any other protocol except OIDC.
-* It doesn not support IdPs that lack Custom callback URLs, such as Facebook.
+* IdPs that lack support for Custom callback URLs, such as Facebook, are not supported.
 * Private use URI Schemes as per [RFC8252, section 7.1](https://datatracker.ietf.org/doc/html/rfc8252#section-7.1) are not used.
 * Approximately 5% of sign in attempts for the iOS app are unsuccessful, resulting in an error message indicating failure to sign in. However, a subsequent attempt usually leads to successful sign in.
 

content/en/docs/community-tools/contribute-to-mendix-docs/indentation-spacing-test.md

@@ -24,7 +24,7 @@ Paragraph text here.
 
 Another paragraph here.
 
-## 1 Indents and Spacing
+## 1 Indents and Spacing 123456 12345678
 
 See [Section Spacing Tests](#spacing) for multiple examples of spacing. 
 

content/en/docs/developerportal/deploy/mendix-cloud-deploy/environments-details.md

@@ -24,9 +24,9 @@ The **Environment Details** page shows information about the selected environmen
 In the **General** tab, you can find the following information about your environment:
 
 * **Status**
-    * {{% icon name="checkmark-circle" color="green" %}} – the application in this environment is running
-    * {{% icon name="subtract-circle" color="gray" %}} – no application has been started yet in this environment, or it has been turned off
-    * {{% icon name="remove-circle" color="red" %}} – the application in this environment is unstable and probably not usable anymore
+    * {{% 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="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