Merge branch 'main' into patch-3

melamriD365 · web-flow · commit 185fe3e09c21 · 2021-05-16T14:52:59.000+01:00
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/type-table.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/type-table.md
@@ -33,7 +33,6 @@ ms.assetid: 41ea27ac-65b6-45a4-ae03-5f8d02dfc67b
 |SingleLine.___URL|The text provides a hyperlink to open the page specified. Any text that does not begin with a valid protocol will have "https://" prepended to it.Only HTTP, HTTPS, FTP , FTPS, OneNote and TEL protocols are allowed in this column.|
 |TwoOptions|This column provides two options. Each option has a number value of 0 or 1 corresponding to a false or true value. Each option also has a label so that true or false values can be represented as "Yes" and "No", "Hot" and "Cold", "On" and "Off" or any pair of labels you want to display.|
 |Whole.None|This option simply displays a number.|
-|Lookup.Simple|Allows for a single reference to a specific table. All custom lookups are this type.|
 
 ## Value elements that are not supported
 
@@ -44,10 +43,11 @@ Following `of-type` property values are not supported currently:
 |Whole.Duration|This format option can be used to display a list of duration options. But the data stored in the database is always a number of minutes. The column looks like a drop-down list and provides suggested options like 1 minute, 15 minutes, 30 minutes all the way up to 3 days. People can choose these options. However, people can also just type in a number of minutes and it resolves to that period of time.|
 |Whole.Timezone|This option displays a select list of time zones such as (GMT-12:00) International Date Line West and (GMT-08:00) Pacific Time (US & Canada). Each of these zones is stored as a number. For example, for the time zone (GMT-08:00) Pacific Time (US & Canada), the TimeZoneCode is 4. More information: [TimeZoneCode Class (Sdk Assembly)](/previous-versions/dynamics-crm4/developers-guide/bb959779(v=msdn.10))|
 |Whole.Language|This option displays a list of the languages provisioned for your organization. The values are displayed as a drop-down list of language names, but the data is stored as a number using LCID codes. Language codes are four-digit or five-digit locale IDs. Valid locale ID values can be found at [Locale ID (LCID) Chart)](/previous-versions/windows/embedded/ms912047(v=winembedded.10)).|
+|Lookup.Simple|Allows for a single reference to a specific table. All custom lookups are this type.|
 |Lookup.Customer|Allows for a single reference to either an account or a contact record. These lookups are available for the Opportunity, Case, Quote, Order, and Invoice tables. These tables also have separate Account and Contact lookups that you can use if your customers are always one type. Or you can include both instead of using the Customer lookup.|
 |Lookup.Owner|Allows for a single reference to either a team or a user record. All team or user-owned tables have one of these.|
 |Lookup.PartyList|Allows for multiple references to multiple tables. These lookups are found on the Email table **To** and **Cc** columns. They're also used in the Phone and Appointment tables.|
 |Lookup.Regarding|Allows for a single reference to multiple tables. These lookups are found in the regarding column used in activities.|
 |Choices|You can customize forms (main, quick create, and quick view) and email templates by adding choices columns. When you add choices column, you can specify multiple values that will be available for users to select. When users fill out the form they can select one, multiple, or all the values displayed in a drop-down list.|
 |Status|A system column that has options that generally correspond to active and inactive status. Some system columns have additional options, but all custom columns have only Active and Inactive status options.|
-|Status Reason|A system column that has options that provide additional detail about the Status column. Each option is associated with one of the available Status options. You can add and edit the options.|
+|Status Reason|A system column that has options that provide additional detail about the Status column. Each option is associated with one of the available Status options. You can add and edit the options.|
diff --git a/powerapps-docs/developer/data-platform/workflow-custom-actions.md b/powerapps-docs/developer/data-platform/workflow-custom-actions.md
@@ -20,7 +20,7 @@ search.app:
 
 Custom Process Actions, also known as simply *Custom Actions*, are one of two ways to create custom messages for the Microsoft Dataverse. The other is *Custom APIs*. More information: [Create and use Custom APIs](custom-api.md).
 
-Both of these capabilities allow for creating new messages that can be called from web services. Custom Process Actions will continue to provide a no-code way to declaratively define synchronous business logic. Custom actions have always been synchronous 'real-time' workflows and therefore not suitable to be converted to use Power Automate.
+Both of these capabilities allow for creating new messages that can be called from web services. Custom Process Actions will continue to provide a no-code way to declaratively define synchronous business logic. Custom process actions have always been synchronous 'real-time' workflows and therefore not suitable to be converted to use Power Automate.
 
 For a comparison of the capabilities of Custom Process Actions and Custom APIs, see [Compare Custom Process Action and Custom API](custom-actions.md#compare-custom-process-action-and-custom-api).
   
@@ -29,13 +29,13 @@ The business logic of a custom process action is implemented using a workflow. W
 For developers, the creation of a new message means you can use the message in code with either the Web API or the Organization service.
 
 - With the Web API, the new messages created with Custom Process Actions are always OData actions. For information about calling actions using the Web API, see [Use Web API actions](webapi/use-web-api-actions.md).
-  - Custom actions can be used in client-side JavaScript in model-driven apps by using the [Xrm.WebApi.online.execute method](../model-driven-apps/clientapi/reference/Xrm-WebApi/online/execute.md).
+  - Custom process actions can be used in client-side JavaScript in model-driven apps by using the [Xrm.WebApi.online.execute method](../model-driven-apps/clientapi/reference/Xrm-WebApi/online/execute.md).
 - With the Organization service, the messages can be called generically in a late-bound style by using the <xref:Microsoft.Xrm.Sdk.OrganizationRequest> class or by using early-bound request and response classes generated by the code generation tool (CrmSvcUtil.exe).
   - More information: 
     - [Generate early-bound classes for the Organization service](org-service/generate-early-bound-classes.md)
     - [Use messages with the Organization service](org-service/use-messages.md)
 
-For information about creating a Custom Process Action using the workflow designer see: [Create a custom action](../../maker/data-platform/create-actions.md)
+For information about creating a Custom Process Action using the workflow designer see: [Create a custom process action](../../maker/data-platform/create-actions.md)
 
 ## Extend Custom Process Actions
 
@@ -67,7 +67,7 @@ If you register any plug-in steps on a Custom Process Action it will establish a
 
 ## Watch out for long running actions
 
-If one of the steps in the action’s real-time workflow is a custom workflow activity, that custom workflow activity is executed inside the isolated sandbox run-time environment and will be subject to the two minute timeout limit, similar to how plug-ins are managed. However, there are no specific restrictions on the amount of overall time the action itself can take. This is not an advantage. The workflow cannot run indefinitely. It will eventually fail for various reasons. For example, if an action participates in a transaction, where rollback is enabled, SQL Server timeouts will apply. Take care to ensure that your custom actions can complete with a clear success or failure in a reasonable period of time. Anything longer than 2 minutes is probably too long.
+If one of the steps in the action’s real-time workflow is a custom workflow activity, that custom workflow activity is executed inside the isolated sandbox run-time environment and will be subject to the two minute timeout limit, similar to how plug-ins are managed. However, there are no specific restrictions on the amount of overall time the action itself can take. This is not an advantage. The workflow cannot run indefinitely. It will eventually fail for various reasons. For example, if an action participates in a transaction, where rollback is enabled, SQL Server timeouts will apply. Take care to ensure that your custom process actions can complete with a clear success or failure in a reasonable period of time. Anything longer than 2 minutes is probably too long.
 
 The existing <xref:Microsoft.Xrm.Sdk.IExecutionContext.Depth> platform checks ensure an infinite loop does not occur. For more information on depth limits see <xref:Microsoft.Xrm.Sdk.Deployment.WorkflowSettings.MaxDepth>. 
 
@@ -76,7 +76,7 @@ The existing <xref:Microsoft.Xrm.Sdk.IExecutionContext.Depth> platform checks en
   
 ### See also  
 
- [Create a custom action](../../maker/data-platform/create-actions.md)<br />
+ [Create a custom process action](../../maker/data-platform/create-actions.md)<br />
  [Use actions](../../maker/data-platform/actions.md)<br />
  [Classic Dataverse workflows](/flow/workflow-processes)<br />
 
diff --git a/powerapps-docs/maker/TOC.yml b/powerapps-docs/maker/TOC.yml
@@ -1960,9 +1960,9 @@
           href: ./data-platform/actions.md
         - name: Create a custom process action
           href: ./data-platform/create-actions.md
-        - name: Configure actions from a real-time workflow
+        - name: Configure custom process actions from a real-time workflow
           href: ./data-platform/configure-actions.md    
-        - name: Invoke actions from a real-time workflow
+        - name: Invoke custom process actions from a real-time workflow
           href: ./data-platform/invoke-custom-actions-workflow-dialog.md
   - name: Work with solutions
     items:
diff --git a/powerapps-docs/maker/canvas-apps/test-studio.md b/powerapps-docs/maker/canvas-apps/test-studio.md
@@ -15,7 +15,7 @@ search.app:
   - PowerApps
 ---
 
-# Test Studio (experimental) 
+# Test Studio 
 
 Build end-to-end UI tests for your canvas app using Test Studio. Maintain your app quality by continually validating that your app works as expected when new changes or updates are deployed. 
 
@@ -29,9 +29,6 @@ Power Apps Test Studio is a low-code solution to write, organize, and automate t
 
 ![Test Studio](./media/test-studio/test-studio.png "Test Studio")
 
-> [!NOTE]
-> This feature is still experimental and we recommend you use it to write tests for non-production apps. For more information, see [Experimental and preview features](working-with-experimental-preview.md).
-
 ## Test Studio terminology
 
 The following section explains key Test Studio terminology.
@@ -105,4 +102,4 @@ While work to provide full control coverage in Power Apps Test Studio is in prog
 - [Automate tests with Azure Pipelines using classic editor](test-studio-classic-pipeline-editor.md)
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/maker/canvas-apps/working-with-test-studio.md b/powerapps-docs/maker/canvas-apps/working-with-test-studio.md
@@ -15,13 +15,10 @@ search.app:
   - PowerApps
 ---
 
-# Working with Test Studio (experimental)
+# Working with Test Studio
 
 In this quickstart, you'll create tests for a canvas app called Kudos. You can also explore and discover testing concepts and apply them to writing tests for your own canvas apps. The sample Kudos app is part of a suite of employee engagement apps available to download from [Employee Experience Starter Kit](https://powerapps.microsoft.com/en-us/blog/powerapps-employee-experience-starter-kit).
 
-> [!NOTE]
-> This feature is still experimental and we recommend you use it to write tests for non-production apps. For more information, see [Experimental and preview features](working-with-experimental-preview.md).
-
 ## Open Test Studio
 
 You don't need to enable this feature in your app like other experimental features. Test Studio is available by default for all canvas apps.
@@ -392,4 +389,4 @@ In addition to the [functions](formula-reference.md) available in Power Apps, th
 - [Automate tests with Azure Pipelines using classic editor](test-studio-classic-pipeline-editor.md)
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/maker/data-platform/actions.md b/powerapps-docs/maker/data-platform/actions.md
@@ -30,23 +30,25 @@ Custom process actions provide the ability to define a single verb (or message)
 
 ## Configurable messages
 
-Once an custom process action is defined and activated, a developer can use that message like any of the other messages provided by the platform. However, a significant difference is that now someone who is not a developer can apply changes to what should be done when that message is used. You can configure the custom process action to modify steps as your business processes change. Any custom code that uses that message does not need to be changed as long as the process arguments do not change.  
+Once an action is defined and activated, a developer can use that message like any of the other messages provided by the platform. However, a significant difference is that now someone who is not a developer can apply changes to what should be done when that message is used. You can configure the action to modify steps as your business processes change. Any custom code that uses that message does not need to be changed as long as the process arguments do not change.  
   
-Workflow processes and plug-ins continue to provide similar capabilities for defining automation. Workflow processes still provide the capability for a non-developer to apply changes. But the difference is in how the business processes are composed and how a developer can write their code. A custom process action is a message that operates on the same level as any of the messages provided by the platform. Developers can register plug-ins for actions.  
+Workflow processes and plug-ins continue to provide similar capabilities for defining automation. Workflow processes still provide the capability for a non-developer to apply changes. But the difference is in how the business processes are composed and how a developer can write their code. An custom process action is a message that operates on the same level as any of the messages provided by the platform. Developers can register plug-ins for actions.  
 
 > [!NOTE]
-> If you intend to write a plug-in to implement your logic for a custom process action instead of using the workflow designer, you should use Custom API instead. More information: [Compare Custom Process Action and Custom API](../../developer/data-platform/custom-actions.md#compare-custom-process-action-and-custom-api)
-
+> Custom API is a newer way to define custom messages with many advantages for developers. If you do not intend to use the no-code capabilities that custom process actions provide to configure business logic, Custom API provides better capabilities for developers to create their own messages. More information: 
+>
+> - [Compare Custom Process Action and Custom API](../../developer/data-platform/custom-actions.md#compare-custom-process-action-and-custom-api)
+> - [Create and use Custom APIs](../../developer/data-platform/custom-api.md)
   
 <a name="BKMK_GlobalMessages"></a>
 
 ## Global messages 
  
-Unlike Microsoft Dataverse workflows, an action doesn’t have to be associated with a specific table. You can define global actions that can be called on their own.
+Unlike Microsoft Dataverse workflows or [plug-ins](../../developer/data-platform/apply-business-logic-with-code.md?branch=master#create-a-plug-in), an custom process action doesn’t have to be associated with a specific table. You can define global custom process actions that can be called on their own.
 
 ## Next steps
 
-[Create a custom action](create-actions.md)  
+[Create a custom process action](create-actions.md)  
   
 
 
diff --git a/powerapps-docs/maker/data-platform/create-actions.md b/powerapps-docs/maker/data-platform/create-actions.md
@@ -1,6 +1,6 @@
 ---
 title: "Create a custom process action | MicrosoftDocs"
-description: "Use custom actions when you want to automate a series of commands in the system. Actions expand the vocabulary available for developers to express business processes."
+description: "Use custom process actions when you want to automate a series of commands in the system. Actions expand the vocabulary available for developers to express business processes."
 ms.custom: ""
 ms.date: 04/28/2021
 ms.reviewer: "matp"
@@ -166,7 +166,7 @@ The **Is Custom Processing Step Allowed for Other Publishers** managed property
   
 ## Next steps
 
-[Invoke custom actions from a workflow](invoke-custom-actions-workflow-dialog.md)   
+[Invoke custom process actions from a workflow](invoke-custom-actions-workflow-dialog.md)   
 
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/maker/data-platform/create-edit-entities-solution-explorer.md b/powerapps-docs/maker/data-platform/create-edit-entities-solution-explorer.md
@@ -78,7 +78,7 @@ In the **General** tab, some of the options are required before you can save the
 |**Display Name**|This is the singular name for the table that will be shown in the app.<br />This can be changed later.|
 |**Plural Name**|This is the plural name for the table that will be shown in the app.<br />This can be changed later.|
 |**Name**|This column is pre-populated based on the display name you enter. It includes the solution publisher customization prefix.|
-|**Ownership**|You can choose either user or team-owned or organization owned. More information: [Standard table ownership](types-of-entities.md#standard-tables)|
+|**Ownership**|You can choose either user or team-owned or organization owned. More information: [Table ownership](types-of-entities.md#table-ownership)|
 
 ## Edit a table
 
@@ -91,20 +91,12 @@ While [viewing tables](#view-tables), select the table you want to edit, or cont
 
 The following options can be set once and cannot be changed after you set them. Take care to only set these options when you need them.
 
-<!-- 
-Same data is presented in edit-tables.md
-Both should point to this include
- -->
 [!INCLUDE [cc_entity-set-once-options-table](../../includes/cc_entity-set-once-options-table.md)]
 
 #### Options that you can change
 
 The following properties can be changed at any time.
 
-<!-- 
-Same data is presented in edit-tables.md
-Both should point to this include
- -->
 [!INCLUDE [cc_entity-changeable-options-table](../../includes/cc_entity-changeable-options-table.md)]
 
 You can also make the following changes:
@@ -121,11 +113,11 @@ As someone with the system administrator security role, you can delete custom ta
 > - When you delete a custom table, the database tables that store data for that table are deleted and all data they contain is lost. Any associated rows that have a parental relationship to the custom table are also deleted. For more information about parental relationships, see [Create and edit relationships between tables](create-edit-entity-relationships.md).
 > - The only way to recover data from a table that was deleted is to restore the database from a point before the table was deleted. More information: [Backup and restore environments](/power-platform/admin/backup-restore-environments)
 
-While [viewing tables](#view-tables), click the ![Delete command](media/delete.gif) command in the toolbar.
+While [viewing tables](#view-tables), select the ![Delete command on toolbar](media/delete.gif) command on the toolbar.
 
-While viewing a table use the delete command in the menu bar.
+While viewing a table use the delete command on the menu bar.
 
-![Delete command](media/delete-custom-entity-solution-explorer.png)
+![Delete command on menu bar](media/delete-custom-entity-solution-explorer.png)
 
 > [!WARNING]
 > Deleting a table that contains data will remove all the data. This data can only be retrieved by backup of the database.
diff --git a/powerapps-docs/maker/data-platform/define-alternate-keys-reference-records.md b/powerapps-docs/maker/data-platform/define-alternate-keys-reference-records.md
diff --git a/powerapps-docs/maker/data-platform/types-of-entities.md b/powerapps-docs/maker/data-platform/types-of-entities.md
diff --git a/powerapps-docs/maker/data-platform/update-solutions.md b/powerapps-docs/maker/data-platform/update-solutions.md
diff --git a/powerapps-docs/maker/model-driven-apps/design-productive-forms.md b/powerapps-docs/maker/model-driven-apps/design-productive-forms.md
