Merge branch 'development' into db-agents-kit-versioning

Author: Karuna-Mendix

content/en/docs/control-center/maia-resources.md

@@ -0,0 +1,77 @@
+---
+title: "Maia Resources"
+url: /control-center/maia-resources/
+description: "Describes how to provision and deprovision Maia Resources using self-service."
+weight: 25
+---
+
+## Introduction
+
+Maia Resources is your access point to increase the capacity of Maia Units for using Maia Make in Studio Pro. It allows admins to provision, upgrade, downgrade, and deprovision Maia Units and manage the resources for Maia Make for their company. For more information on Maia Make’s capabilities, refer to [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/).
+
+## Prerequisites
+
+1. Sufficient token entitlements – The user should have an adequate number of available Mendix Cloud Tokens to allocate for Maia Unit provisioning.
+2. Valid subscription plan – The user's Mendix subscription must be based on the FY21 price list or newer. Older subscription plans are not eligible for provisioning.
+3. Single account ownership – The user must have a single account. Owning multiple accounts is not supported for Maia Unit provisioning.
+4. Enterprise platform subscription – The user must have a single active enterprise platform subscription.
+
+## Overview of Maia Units
+
+The overview page provides a centralized view of all Maia Units currently provisioned for your company.
+
+* Type – The type or resources; either Free or Provisioned
+* Cloud Tokens – The number of Cloud Tokens used
+* Capacity (Maia Units) – The number of Maia Units per month your organization can use
+* State – Whether the resources is active, or ready to be downgraded or deprovisioned
+
+{{< figure src="/attachments/control-center/maia-resources/overview.jpeg" alt="" >}}
+
+## Increasing Your Maia Units Capacity {#increase-maia-units}
+
+1. **Make sure you have Cloud Tokens available**
+Cloud Tokens are purchased through your Mendix subscription. If your organization already has Cloud Tokens allocated to other services, you can reassign them. Check your available balance in the Control Center. If you need to purchase more, contact your Mendix account manager.
+2. **Convert Cloud Tokens to Maia Units**
+In the Control Center, go to Maia Resources and select Provision Resource. Choose how many Cloud Tokens to allocate. Each Cloud Token gives you 100 Maia Units per month.
+3. **Use Maia in Studio Pro**
+Your new capacity is active immediately. Studio Pro unblocks and Maia Make becomes available again.
+
+### Key Considerations
+
+* Monthly cycle – Your Maia Units reset each month. Unused units do not roll over.
+* Upgrades – Upgrades take effect immediately. Downgrades and cancellations take effect at the end of the current month; you keep access until then.
+* Free allowance – Every Mendix account includes a base allocation each month before any Cloud Tokens are needed.
+
+## Provisioning Maia Units {#provisioning-maia-units}
+
+You can provision any Maia resources directly within the Control Center using the self-service capability. To do this, select **Provision Resource**. 
+
+This allows you to select how many Cloud Token to use to provision Maia Units. Every Cloud Token provisions 100 Maia Units per month.
+
+{{< figure src="/attachments/control-center/maia-resources/provision.jpeg" alt="" >}}
+
+Click **Provision** to select an amount of cloud tokens. An pop-up shows the Maia Units capacity that will be added. Clicking **Provision** again completes the process. You are taken back to the **Maia Resource** page where the newly provisioned Maia Units appear in the list.
+
+{{< figure src="/attachments/control-center/maia-resources/resource-summary.jpeg" alt="" width="300" >}}
+
+## Upgrading Maia Units {#upgrading-maia-units}
+
+To upgrade your provisioned Maia Units, select a plan of type **Provisioned** from your resources overview and click **Edit Resource**. This opens the page of your current resource, showing the amount of allotted Cloud Tokens. Increase the amount of Cloud Tokens to upgrade your provisioned Maia Units, then click **Save Changes**. Upgrades will take effect immediately.
+
+{{< figure src="/attachments/control-center/maia-resources/upgrade.jpeg" alt="" >}}
+
+## Downgrading Maia Units {#downgrading-maia-units}
+
+To downgrade your amount of provisioned Maia Units, select a plan of type **Provisioned** from your resources overview and press **Edit Resource**. This opens the page for your current resource, showing the amount of allotted Cloud Tokens. Decrease the amount of Cloud Tokens to downgrade your provisioned Maia Units, then click **Save Changes** to confirm.
+
+{{% alert color="info" %}}
+Your subscription plan operates on a monthly bundle cycle. When you downgrade, the new plan takes effect at the start of the new month. Until that date, you can still use the resource, and the status in the overview reads **Plan Downgrade Scheduled**.
+{{% /alert %}}
+
+## Deprovisioning Maia Units {#deprovisioning-maia-units}
+
+To deprovision, select a plan of type **Provisioned** from your resources overview and click **Deprovision**. A confirmation pop-up window appears. Click **Deprovision** to confirm.
+
+{{% alert color="info" %}}
+Your subscription plan operates on a monthly bundle cycle. When you deprovision a resource, the deprovisioning takes effect at the end of the current subscription month. Until that date, you can still use the resource and status in the overview reads **Plan Deprovision Scheduled**.
+{{% /alert %}}

content/en/docs/howto/extensibility/pluggable-widgets/create-a-pluggable-widget-one.md

@@ -95,10 +95,6 @@ As part of the widget scaffolding, the generator builds the widget for the first
 
 There is also a watcher available that will rebuild your widget as you make changes to files. Start the watcher by running `npm start`.
 
-{{% alert color="info" %}}
-NPM version 7 changed the resolution behavior of peerDependencies. Try adding `--legacy-peer-deps` to your install command if it results in peer dependency resolution errors.
-{{% /alert %}}
-
 ### Using the Widget
 
 When the build script completes it will package your widget as a `.mpk` file and copy it to the `widgets/` directory in your Mendix app. Now that the generator has finished its job it is time to use the widget in Studio Pro. To use the widget, do the following:
@@ -118,9 +114,9 @@ Open the *(YourMendixApp)/myPluggableWidgets/textBox* folder in your IDE of choi
 1. Remove the file *src/components/HelloWorldSample.tsx*. Errors in *TextBox.editorPreview.tsx* will be dealt with in step 6 below.
 2. The generator creates the widget definition file `src/TextBox.xml` with preset properties. Replace the `sampleText` property following this snippet:
 
-    ```xml
+    ```xml {hl_lines=["7-15"]}
     <?xml version="1.0" encoding="utf-8" ?>
-    <widget id="mendix.textbox.TextBox" pluginWidget="true" needsEntityContext="true" supportedPlatform="Web" offlineCapable="true" xmlns="http://www.mendix.com/widget/1.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mendix.com/widget/1.0/ ../xsd/widget.xsd">
+    <widget id="mendix.textbox.TextBox" pluginWidget="true" needsEntityContext="true" supportedPlatform="Web" offlineCapable="true" xmlns="http://www.mendix.com/widget/1.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mendix.com/widget/1.0/ ../node_modules/mendix/custom_widget.xsd">
         <name>Text Box</name>
         <description>Edit text input</description>
         <icon/>
@@ -141,7 +137,7 @@ Open the *(YourMendixApp)/myPluggableWidgets/textBox* folder in your IDE of choi
     Explaining the code:
 
     * *TextBox.xml* is the [widget definition file](/apidocs-mxsdk/apidocs/pluggable-widgets/#widget-definition) used in Studio Pro which reads the widget's capabilities
-    * The property `pluginWidget=true` will make the widget work with the new widget API
+    * The property `pluginWidget=true` will make the widget work with the [Pluggable Widgets API](/apidocs-mxsdk/apidocs/pluggable-widgets/)
     * The property `needsEntityContext=true` is set up to allow the attribute to be taken from context
     * The property of the [type attribute](/apidocs-mxsdk/apidocs/pluggable-widgets-property-types/#attribute) only allows the selection of string attributes from the domain model
 
@@ -156,7 +152,7 @@ Open the *(YourMendixApp)/myPluggableWidgets/textBox* folder in your IDE of choi
     Paste the following [React function component](https://react.dev/learn/your-first-component) into the newly create `TextInput.tsx` file.
 
     ```tsx
-    import { createElement, ReactElement } from "react";
+    import { ReactElement } from "react";
 
     export interface TextInputProps {
         value: string;
@@ -172,14 +168,14 @@ Open the *(YourMendixApp)/myPluggableWidgets/textBox* folder in your IDE of choi
 5. The container component *src/TextBox.tsx* receives the properties in the runtime, and forwards the data to the display component. The container works like glue between the Mendix application and the display component. In *TextBox.tsx* update the component to look like this:
 
     ```tsx
-    import { createElement, ReactElement } from "react"; 
+    import { ReactElement } from "react"; 
     import { TextBoxContainerProps } from "../typings/TextBoxProps";
     import { TextInput } from "./components/TextInput";
 
     import "./ui/TextBox.css";
 
     export function TextBox(props: TextBoxContainerProps): ReactElement {
-        const value = props.textAttribute.value || "";
+        const value = props.textAttribute.value ?? "";
         return <TextInput value={value} />;
     }
     ```
@@ -193,7 +189,7 @@ Open the *(YourMendixApp)/myPluggableWidgets/textBox* folder in your IDE of choi
 6. Pluggable Widgets also have a Preview component, which is used in the design mode of the Studio Pro page editor. Update *src/TextBox.editorPreview.tsx* such that the deleted `HelloWorldSample` component is replaced by our `TextInput` component. This will resolve the errors thrown by `npm start`.
 
     ```tsx
-    import { ReactElement, createElement } from "react";
+    import { ReactElement } from "react";
     import { TextBoxPreviewProps } from "../typings/TextBoxProps";
     import { TextInput } from "./components/TextInput";
 
@@ -224,7 +220,7 @@ The input works, but the styling could be improved. In the next code snippets, y
 
     ```tsx
     export function TextBox(props: TextBoxContainerProps): ReactElement {
-        const value = props.textAttribute.value || "";
+        const value = props.textAttribute.value ?? "";
         return <TextInput 
             value={value} 
             style={props.style} 
@@ -239,7 +235,7 @@ The input works, but the styling could be improved. In the next code snippets, y
 2. Until we update the type of our TextInputProps, Typescript will display errors in *TextBox.tsx*. In *src/components/TextInput.tsx*, add the missing properties to the interface and pass them to the `input` component:
 
     ```tsx
-    import { createElement, CSSProperties, ReactElement } from "react";
+    import { CSSProperties, ReactElement } from "react";
 
     export interface TextInputProps {
         value: string;
@@ -282,8 +278,11 @@ Comparing our widget to the Mendix text input widget we are still missing a labe
 
 1. Open *src/TextBox.tsx* and remove the `style` and `className` props from `TextInput`. Now that the widget is a labeled input, it should no longer have the layout styling applied to it. In fact, the `pluggable-widget-tools` removed them from the type definition in *typings/TextBoxProps.d.ts*.
 
-    ```tsx
-    return <TextInput value={value} tabIndex={props.tabIndex} />;
+    ```tsx {hl_lines=[3]}
+    export function TextBox(props: TextBoxContainerProps): ReactElement {
+        const value = props.textAttribute.value ?? "";
+        return <TextInput value={value} tabIndex={props.tabIndex} />;
+    }
     ```
 
 1. **Synchronize** your project and **update** all widgets. Now open the widget **Properties** and open the **Label** tab.
@@ -344,7 +343,7 @@ Our widget now looks like a Mendix widget, but does not behave like one yet. Whi
 
     ```tsx {hl_lines=5}
     export function TextBox(props: TextBoxContainerProps): ReactElement {
-        const value = props.textAttribute.value || "";
+        const value = props.textAttribute.value ?? "";
         return <TextInput 
             value={value} 
             onChange={props.textAttribute.setValue} 

content/en/docs/howto/extensibility/pluggable-widgets/create-a-pluggable-widget-two.md

@@ -76,7 +76,7 @@ To add these restrictions, follow the instructions below:
 4. In *components/TextInput.tsx*, add the `disabled` property to the `TextInputProps` interface and set the HTML input attribute to `disabled`:
 
     ```tsx
-    import { createElement, CSSProperties, ReactElement } from "react";
+    import { CSSProperties, ReactElement } from "react";
 
     export interface TextInputProps {
         value: string;
@@ -146,7 +146,7 @@ This section teaches you how to add validation to your TextBox widget. Using mic
 3. To render the message, create a new component *components/Alert.tsx*:
 
     ```tsx
-    import { FunctionComponent, createElement, ReactNode } from "react";
+    import { FunctionComponent, ReactNode } from "react";
 
     export interface AlertProps {
         alertStyle?: "default" | "primary" | "success" | "info" | "warning" | "danger";
@@ -194,7 +194,7 @@ This section teaches you how to add validation to your TextBox widget. Using mic
 5. Add `Fragment` to the current React import (shown below), and add a new `Alert` import underneath the existing imports in *TextBox.tsx*:
 
     ```tsx
-    import { createElement, ReactElement, Fragment } from "react";
+    import { ReactElement, Fragment } from "react";
     import { Alert } from "./components/Alert";
     ```
 
@@ -314,7 +314,7 @@ Until now the components did not keep any state. Each keystroke passed through t
 2. In *TextBox.tsx*, check if `onChangeAction` is available and call the execute function `onLeave` when the value is changed. When doing this, replace the `onUpdate` function with your new `onLeave` function:
 
     ```tsx
-    import { createElement, Fragment, ReactElement, useEffect } from "react";
+    import { Fragment, ReactElement, useEffect } from "react";
     import { TextBoxContainerProps } from "../typings/TextBoxProps";
     import { TextInput } from "./components/TextInput";
 
@@ -357,7 +357,7 @@ Until now the components did not keep any state. Each keystroke passed through t
 3. In *components/TextInput.tsx*, introduce a state for input changes and use the `onBlur` function to call the `onLeave` function by replacing the `onUpdate` function:
 
     ```tsx
-    import { createElement, CSSProperties, ReactElement, useEffect, useState } from "react";
+    import { CSSProperties, ReactElement, useEffect, useState } from "react";
 
     export interface TextInputProps {
         value: string;
@@ -546,7 +546,7 @@ To easily view changes to your widget while in Studio Pro's **Design mode**, you
 To add preview mode functionality, create a new file *src/TextBox.editorPreview.tsx* and add this code to it:
 
    ```tsx
-   import { createElement, ReactElement } from "react";
+   import { ReactElement } from "react";
    import { TextBoxPreviewProps } from "../typings/TextBoxProps";
    import { TextInput } from "./components/TextInput";
 

content/en/docs/private-platform/nist-controls/ma/_index.md

@@ -0,0 +1,15 @@
+---
+title: "NIST 800-53 Maintenance Compliance for Private Mendix Platform"
+linktitle: "Maintenance"
+url: /private-mendix-platform/nist-controls-ma/
+description: "Documents the Private Mendix Platform's compliance with the Maintenance (MA) category of the NIST 800-53 security framework."
+weight: 10
+no_list: false 
+simple_list: true
+---
+
+## Introduction
+
+Documents in this section provide more information about Private Mendix Platform's compliance with the Maintenance (MA) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect.
+
+In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below.

content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma01.md

@@ -0,0 +1,59 @@
+---
+title: "MA-01 System Maintenance Policy And Procedures"
+linktitle: "MA-01"
+url: /private-mendix-platform/nist-controls/ma-01/
+description: "Documents the Private Mendix Platform's compliance with the MA-01 control of the NIST 800-53 framework."
+weight: 20
+---
+
+## Introduction
+
+This document describes how Private Mendix Platform fulfills the MA-01 control.
+
+| Control ID | MA-01 |
+| --- | --- |
+| Control category | MA - Maintenance |
+| Requirement baseline | FEDRAMP MODERATE |
+| Responsibility and ownership | Customer - Infra, Customer - Org |
+
+## Control
+
+The organization:
+
+* Develops, documents, and disseminates to organization-defined personnel or roles:
+
+    * A system maintenance policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance
+    * Procedures to facilitate the implementation of the system maintenance policy and associated system maintenance controls
+
+* At an organization-defined frequency, reviews and updates the current:
+
+    * System maintenance policy at an organization-defined frequency
+    * System maintenance procedures.
+
+### Supplemental Guidance
+
+This control addresses the establishment of policy and procedures for the effective implementation of selected security controls and control enhancements in the MA family. Policy and procedures reflect applicable federal laws, Executive Orders, directives, regulations, policies, standards, and guidance. Security program policies and procedures at the organization level may make the need for system-specific policies and procedures unnecessary. 
+
+The policy can be included as part of the general information security policy for organizations or conversely, can be represented by multiple policies reflecting the complex nature of certain organizations. The procedures can be established for the security program in general and for particular information systems, if needed. The organizational risk management strategy is a key factor in establishing policy and procedures. 
+
+The following controls are related to this control:
+
+* PM-9.
+
+For more information, refer to the NIST Special Publications 800-12, 800-100.
+
+## Responsibility
+
+### Customer Responsibility
+
+System maintenance plans and schedules for the Private Mendix Platform, Mendix applications, and their underlying infrastructure are the responsibility of the customer and associated Infra and App Implementers and Operators.
+
+## Guidance
+
+### Customer Responsibility
+
+This is not a Mendix responsibility. It is the responsibility of the customer to implement a system maintenance policy and procedures. 
+
+It is the responsibility of the Infra Implementer to ensure that the infrastructure and Private Mendix Platform is implemented in such a way that they comply with and support the customer's system maintenance policy and procedures. It is the responsibility of the App Implementer to ensure that the Mendix App is implemented in such a way that it complies with and supports the customer's system maintenance policy and procedures. 
+
+It is the responsibility of the Infra Operator and App Operator to perform maintenance and updates in such a way that they ensure ongoing compliance with the customer's system maintenance policy and procedures.