Live publish

Author: buck1ey

powerapps-docs/developer/data-platform/best-practices/business-logic/remove-unsupported-code-using-reflection-workflow-activities.md

@@ -63,7 +63,7 @@ The underlying issue about supporting strong types has been fixed, but this code
 
 ## Additional information
 
-Currently reflection is not allowed. This code references an internal assembly that was included in a white list so that internal code could reflect on it. This is why it does not currently throw an error. But when general restrictions are lifted in the future, this will cause the workflow activity to break.
+Currently reflection is not allowed. This code references an internal assembly that was included in an allow list so that internal code could reflect on it. This is why it does not currently throw an error. But when general restrictions are lifted in the future, this will cause the workflow activity to break.
 
 In order to provide greater capabilities within custom workflow activities without breaking people's business logic, we need everyone to review their code base and remove references like this.
 

powerapps-docs/developer/data-platform/includes/data-service-errors.md

@@ -2097,7 +2097,7 @@
 |0x8004F050<br />-2147159984|Name: **LayerDesiredOrderInvalidXMLDetail**<br />Message: The LayerDesiredOrder parameter contains an invalid XML schema. Check the property [{0}].|
 |0x8004F052<br />-2147159982|Name: **LayerDesiredOrderNotAllowedOnPatch**<br />Message: The LayerDesiredOrder parameter cannot be used when importing a Patch. The parameter can only be used while importing a solution.|
 |0x8004F048<br />-2147159992|Name: **LayerDesiredOrderNotSamePublisher**<br />Message: The solution [{0}] was used in the LayerDesiredOrder parameter, but its publisher [{1}] does not match the publisher of the solution being installed: [{2}]. This parameter can be used only by solutions from the same publisher.|
-|0x8004F065<br />-2147159963|Name: **LayerDesiredOrderNotWhitelist**<br />Message: The LayerDesiredOrder parameter is present in the import request of [{0}], but this solution is not allowed to use it. Solutions must be whitelisted to use this feature.|
+|0x8004F065<br />-2147159963|Name: **LayerDesiredOrderNotWhitelist**<br />Message: The LayerDesiredOrder parameter is present in the import request of [{0}], but this solution is not allowed to use it. Solutions must be allow listed to use this feature.|
 |0x8004F047<br />-2147159993|Name: **LayerDesiredOrderPendingUpgrade**<br />Message: The solution [{0}] used in LayerDesiredOrder parameter has a pending upgrade. Please complete its upgrade before retrying this operation.|
 |0x8004F056<br />-2147159978|Name: **LayerDesiredOrderPublisherNotAllowed**<br />Message: The publisher [{0}] is not allowed to use the LayerDesiredOrder parameter.|
 |0x8004F058<br />-2147159976|Name: **LayerDesiredOrderRestrictedSolution**<br />Message: The LayerDesiredOrder parameter cannot be used on [{0}].|

powerapps-docs/developer/data-platform/reference/entities/datalakeworkspace.md

@@ -306,7 +306,7 @@ These columns/attributes return true for either **IsValidForCreate** or **IsVali
 
 |Property|Value|
 |--------|-----|
-|Description|Application Id that is white listed in AAD Tenant ID to access the Graph API.|
+|Description|Application Id that is allow listed in AAD Tenant ID to access the Graph API.|
 |DisplayName|Whitelisted App Id|
 |IsValidForForm|True|
 |IsValidForRead|True|

powerapps-docs/developer/data-platform/reference/entities/datalakeworkspacepermission.md

@@ -306,7 +306,7 @@ These columns/attributes return true for either **IsValidForCreate** or **IsVali
 
 |Property|Value|
 |--------|-----|
-|Description|Application Id that is white listed in AAD tenant id to access the Graph API.|
+|Description|Application Id that is allow listed in AAD tenant id to access the Graph API.|
 |DisplayName|Whitelisted App ID|
 |IsValidForForm|True|
 |IsValidForRead|True|

powerapps-docs/maker/data-platform/data-platform-create-business-rule.md

@@ -3,10 +3,9 @@ title: Create a business rule in Microsoft Dataverse | Microsoft Docs
 description: Step-by-step instructions for how to create a business rule in Microsoft Dataverse.
 author: lancedMicrosoft
 manager: kvivek
-
 ms.component: cds
 ms.topic: how-to
-ms.date: 03/21/2018
+ms.date: 04/05/2022
 ms.subservice: dataverse-maker
 ms.author: lanced
 ms.reviewer: matp
@@ -38,7 +37,7 @@ By combining conditions and actions, you can do any of the following with busine
 
 ## Differences between canvas and model-driven apps
 
-Model driven apps can use all actions available on business rules, however not all business rule actions are available for canvas apps at this time. The following actions are **not** available on Canvas apps :
+Model driven apps can use all actions available on business rules, however not all business rule actions are available for canvas apps at this time. The following actions are **not** available on canvas apps:
 
 * Show or hide columns  
 * Enable or disable columns  
@@ -96,7 +95,7 @@ Business rules work with most column types including text, number, choice, date,
 
 8. **Add actions.** To add an action:  
 
-    1. Drag one of the action components from the **Components** tab to a plus sign next to **Condition** component. Drag the action to a plus sign next to a check mark if you want the business rule to take that action when the condition is met, or to a plus sign next to an  x if you want the business rule to take that action if the condition is not met.
+    1. Drag one of the action components from the **Components** tab to a plus sign next to **Condition** component. Drag the action to a plus sign next to a check mark if you want the business rule to take that action when the condition is met, or to a plus sign next to an  x if you want the business rule to take that action if the condition isn't met.
 
         ![Drag an action to a business rule.](./media/data-platform-cds-create-business-rule/drag-an-action-business-rule.png "Drag an action to a business rule")  
 
@@ -106,7 +105,7 @@ Business rules work with most column types including text, number, choice, date,
 
 9. **Add a business recommendation (model-driven apps only)**. To add a business recommendation:  
 
-    1. Drag the **Recommendation** component from the **Components** tab to a plus sign next to a **Condition** component. Drag the **Recommendation** component to a plus sign next to a check mark if you want the business rule to take that action when the condition is met, or to a plus sign next to an  x if you want the business rule to take that action if the condition is not met.  
+    1. Drag the **Recommendation** component from the **Components** tab to a plus sign next to a **Condition** component. Drag the **Recommendation** component to a plus sign next to a check mark if you want the business rule to take that action when the condition is met, or to a plus sign next to an  x if you want the business rule to take that action if the condition isn't met.  
 
     2. To set properties for the recommendation, select the **Recommendation** component in the designer window, and then set the properties in the **Properties** tab.  
 
@@ -128,26 +127,55 @@ Business rules work with most column types including text, number, choice, date,
     > - To take a snapshot of everything in the **Business Rule** window, select **Snapshot** on the action bar. This is useful, for example, if you want to share and get comments on the business rule from a team member.  
     > - Use the mini-map to navigate quickly to different parts of the process. This is useful when you have a complicated process that scrolls off the screen.  
     > - As you add conditions, Actions, and business recommendations to your business rule, Dataverse builds the code for the business rule at the bottom of the designer window. This code is read only.  
-  
+
+## Example: Create a business rule for tasks older than 30 days
+
+ This business rule example creates a condition that triggers a message in the task description field when a task is more than 30 days old.
+
+1. Sign in to [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), on the left navigation pane expand **Data**.
+1. In the list that appears, select **Tables**.
+1. Open the **Task** table, and then select the **Business rules** tab.
+1. Select **Add business rule**.
+1. Select **New Condition** on the business process flow canvas, and enter or select the following properties:
+   - **Display name**: *Task is more than 30 days old*
+   - **Entity**: **Task**
+   - **Rule 1**
+      - **Source**: **Entity**
+      - **Field**: **Created On**
+      - **Operator**: **+**
+      - **Type**: **Value**
+      - **Days**: *30*
+   - **Condition Expression** (automatically created): **(Created On Is greater than [Created On + 30])**
+1. Select **Apply**.
+1. Select **Add** > **Add Show Error Message**.
+1. In the **Show Error Message Properties** tab, enter the following properties: 
+   - **Display Name**: *Task is more than 30 days old*
+   - **Entity**: **Task**
+   - **Error Message**:
+      - **Field**: **Description**
+      - **Message**: *This task is more than 30 days old!*
+1. Select **Apply**.
+1. Select **Save**.
+
 ## Localize error messages used in business rules
 
- If you have more than one language provisioned for your organization, you will want to localize any error messages that you have set. Each time you set a message, a label is generated by the system. If you export the translations in your organization, you can add localized versions of your messages and then import those labels back into the Dataverse, so that people using languages other than your base language can view the translated messages.
+ If you've more than one language provisioned for your organization, you'll want to localize any error messages that you have set. Each time you set a message, a label is generated by the system. If you export the translations in your organization, you can add localized versions of your messages and then import those labels back into the Dataverse, so that people using languages other than your base language can view the translated messages.
 
 ## Common issues
 
 This section describes common issues that may occur when you use business rules.
 
 ### Composite attributes not supported with Unified Interface apps
 
-Actions or conditions that use [Composite attributes](../../developer/model-driven-apps/clientapi/reference/composite-attributes.md) are not supported in apps based on the Unified Interface.  Alternatively, you can use actions or conditions on the attributes that comprise the composite attributes. For example, instead of using the **Full Name** (fullname) attribute, you can use the **First Name** (firstname) and **Last Name** (lastname) attributes. 
+Actions or conditions that use [Composite attributes](../../developer/model-driven-apps/clientapi/reference/composite-attributes.md) aren't supported in apps based on the Unified Interface.  Alternatively, you can use actions or conditions on the attributes that comprise the composite attributes. For example, instead of using the **Full Name** (fullname) attribute, you can use the **First Name** (firstname) and **Last Name** (lastname) attributes. 
 
 ### Is your business rule not firing for a form?
 
 A business rule may not execute because the field referenced in the business rule isn’t included with the form. 
 1.	Open [solution explorer](../model-driven-apps/advanced-navigation.md#solution-explorer). Expand the entity that you want and then select **Forms**. 
 2.	Open the form that you want and then on the form designer ribbon select **Business Rules**. 
 3.	In the form designer, open the business rule. 
-4.	In the business rule designer select each condition and action to verify all the fields referenced in each condition and action. 
+4.	In the business rule designer, select each condition and action to verify all the fields referenced in each condition and action. 
 
      > [!div class="mx-imgBorder"] 
      > ![Field referenced in business rule exists in entity.](media/data-platform-cds-create-business-rule/business-rule-field.png "Field referenced in business rule exists in entity")
@@ -163,13 +191,13 @@ A business rule may not execute because the field referenced in the business rul
 - Yes, a business rule can unlock fields and edit actions on a read-only form.
 
 *How do I troubleshoot a business rule that isn't working?* 
-- See [Is your business rule not firing for a form?](#is-your-business-rule-not-firing-for-a-form) in this topic.
+- See [Is your business rule not firing for a form?](#is-your-business-rule-not-firing-for-a-form) in this article.
 
 *Do business rules react to changes made by an onLoad script?*
-- No, they will execute before an onload script is executed.
+- No, they'll execute before an onload script is executed.
 
 *When I update a business rule, is it executed against all existing records?*
-- No. Business rules are run on clients. For example, they run when a form is opened by a user and when a field value changes on that open form. They are not executed inside Dataverse.
+- No. Business rules are run on clients. For example, they run when a form is opened by a user and when a field value changes on that open form. They aren't executed inside Dataverse.
 
 ### See also