Merge pull request #6458 from MicrosoftDocs/2739608

Component library GA updates - 2739608

Author: tapanm-MSFT

powerapps-docs/maker/TOC.yml

@@ -1208,7 +1208,7 @@
           href: ./canvas-apps/map-component-input-fields.md
         - name: Add multimedia to a component
           href: ./canvas-apps/component-multimedia.md
-        - name: Behavior formulas
+        - name: Behavior formulas (preview)
           href: ./canvas-apps/component-behavior.md
   - name: Performance and optimization
     items:

powerapps-docs/maker/canvas-apps/component-behavior.md

@@ -1,5 +1,5 @@
 ---
-title: Behavior formulas for components
+title: Behavior formulas for components (preview)
 description: Do one or more tasks in canvas app when a component-based action occurs.
 author: hemantgaur
 ms.subservice: canvas-developer
@@ -16,12 +16,21 @@ contributors:
   - tapanm-msft
 ---
 
-# Behavior formulas for components
+# Behavior formulas for components (preview)
 
-Specify one or more [behavior formulas](working-with-formulas-in-depth.md) that run when an event triggers a change in component instances. 
+[This article is pre-release documentation and is subject to change.]
+
+> [!IMPORTANT]
+> - This is a preview feature.
+> - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)]
+
+Specify one or more [behavior formulas](working-with-formulas-in-depth.md) that run when an event triggers a change in component instances.
 
 For example, set a component's **OnReset** property to one or more formulas that do initialization and clear input. Reset values when the **Reset** function runs on the component instances.
 
+> [!NOTE]
+> The capability of using **OnReset** property for behavior formulas inside components is generally available. All other custom behavior properties for canvas components are still in preview.
+
 ## OnReset
 
 With a component master selected, select **OnReset** in the drop-down list of properties (on the left side of the formula bar), and then enter one or more formulas.

powerapps-docs/maker/canvas-apps/component-library-alm.md

@@ -20,7 +20,7 @@ contributors:
 
 A [component library](component-library.md) is a special type of canvas app that can contain one or more canvas components. These library components can then be used by all the other canvas apps in the environment. This capability enables you to create reusable shared components across all apps in an environment, unlike [app-level components](create-component.md#components-in-canvas-apps) that are restricted to one app.
 
-To use a component from a component library, you have to first import the component into the canvas app. Once imported, you can then add the component to the app screen. Any updates in the component definition from the component library will prompt you to review and incorporate the change [on demand](component-library.md#method-2-proactive-check-for-updates) or when the [app is opened for editing](component-library.md#method-1-component-update-notification-on-app-edit). Component libraries and dependent apps can also be moved to another environment using standard [Microsoft Dataverse solutions](/power-platform/alm/solution-concepts-alm).
+To use a component from a component library, you have to first import the component into the canvas app. Once imported, you can then add the component to any app screen. Any updates in the component definition from the component library will prompt you to review and incorporate the change [on demand](component-library.md#method-2-proactive-check-for-updates) or when the [app is opened for editing](component-library.md#method-1-component-update-notification-on-app-edit). Component libraries and dependent apps can also be moved to another environment using standard [Microsoft Dataverse solutions](/power-platform/alm/solution-concepts-alm).
 
 > [!NOTE]
 > In this article, the term "import" refers to importing a component from a component library to an app, and shouldn't be confused with importing a solution into Dataverse.
@@ -32,7 +32,7 @@ In order to maintain the relationship from the app to the component library, ens
 
 ## Canvas apps and component libraries solution support
 
-Consistent with the other solution object dependencies, if a canvas app uses a control from a component library, it will have a dependency on that component library. In order to move an app to the new environment, you'll need to either package the component library inside the same solution or install it as a pre-requisite. App to component library dependency is maintained in the target environment. At a later point, when a component library with the updated component is imported using a solution into the target environment, existing apps will get the new component definitions using the regular [component update flow](component-library.md#update-a-component-library).
+Consistent with the other solution object dependencies, if a canvas app imports a canvas component from a component library, it will have a dependency on that component library. In order to move an app to the new environment, you'll need to either package the component library inside the same solution or install it as a pre-requisite. App to component library dependency is maintained in the target environment. At a later point, when a component library with the updated component is imported using a solution into the target environment, existing apps will get the new component definitions using the regular [component update flow](component-library.md#update-a-component-library).
 
 ### Creating and exporting component library in a solution
 
@@ -90,7 +90,7 @@ Dependencies are calculated based on the latest published state of an app. If yo
     - If you're consuming the solution, check that the canvas app has properly identified the component libraries as [solution dependencies](/power-platform/alm/solution-concepts-alm#solution-dependencies). If the solution doesn't properly identify the component libraries as solution dependencies, that means the app dependency to the component library link hasn't been created properly. In that case, check with the solution provider to resolve the issue.
     - If you're the solution publisher, check that the component libraries are saved with the library logical name in the solution, and that it's same as the one referenced in the component library .msapp package.
 
-- Solution export always exports the latest version of the component library. Hence, always update the apps with the latest component version before exporting them though solutions. This action ensures that the apps have the same component version as available in the latest version of the component library. Apps and library are considered to be synchronized with each other when they're moved to a target environment for the first time; and hence, you're not prompted for any update being available when editing the app.
+- Solution export always exports the latest version of the component library. Hence, always update the apps with the latest component version before exporting them through solutions. This action ensures that the apps have the same component version as available in the latest version of the component library. Apps and library are considered to be synchronized with each other when they're moved to a target environment for the first time; and hence, you're not prompted for any update being available when editing the app.
 
 ### See also