Skip to content

Commit 76ea5c1

Browse files
authored
Merge pull request #299968 from haroldcampos/RulesBuild
Adding content for Rules engine GA
2 parents d5d5089 + 1ca46fc commit 76ea5c1

23 files changed

+196
-203
lines changed

articles/logic-apps/rules-engine/add-rules-control-functions.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,10 @@ ms.date: 01/27/2025
1212
#CustomerIntent: As a developer, I want to understand how to optimize rules execution by adding control functions to actions in rules using Microsoft Rules Composer.
1313
---
1414

15-
# Add control functions in actions to optimize rules execution using Microsoft Rules Composer (Preview)
15+
# Add control functions in actions to optimize rules execution using Microsoft Rules Composer
1616

1717
[!INCLUDE [logic-apps-sku-standard](../../../includes/logic-apps-sku-standard.md)]
1818

19-
> [!IMPORTANT]
20-
> This capability is in preview and is subject to the
21-
> [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
2219

2320
This guide describes how to optimize rules execution by adding control functions to actions in your rules using the Microsoft Rules Composer. Control functions help your application or ruleset control the facts in the rules engine's working memory. These functions include the **Assert**, **Clear**, **Halt**, **Retract**, **RetractByType**, **Reassert**, and **Update** functions for the .NET object and **TypedXmlDocument** entities that you can use as facts. The existence of facts in working memory drives the conditions that the engine evaluates and the actions that execute.
2421

articles/logic-apps/rules-engine/add-rules-operators.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,10 @@ ms.date: 01/27/2025
1212
#CustomerIntent: As a developer, I want to understand how use arithmetic and logic operators in the rules that I create for my Azure Logic Apps Rules Engine project.
1313
---
1414

15-
# Add arithmetic and logical operators to rules using Microsoft Rules Composer (Preview)
15+
# Add arithmetic and logical operators to rules using Microsoft Rules Composer
1616

1717
[!INCLUDE [logic-apps-sku-standard](../../../includes/logic-apps-sku-standard.md)]
1818

19-
> [!IMPORTANT]
20-
> This capability is in preview and is subject to the
21-
> [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
2219

2320
This guide describes how to add arithmetic and logical operators to the rules in your ruleset using the Microsoft Rules Composer.
2421

@@ -134,6 +131,11 @@ As another possible solution, you can create a rule such as the following exampl
134131

135132
In the preceding example, the `<CheckQuantityAndDoSomething>` function checks the parameter value and executes if the condition is met.
136133

134+
To determine whether an existing argument is null, use the composer:
135+
136+
`argument is equal to <null>`
137+
138+
137139
> [!NOTE]
138140
>
139141
> Alternatively, you can modify the **XPath Field** property for the

articles/logic-apps/rules-engine/build-fact-creators-retrievers.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,10 @@ ms.date: 01/27/2025
1212
#CustomerIntent: As a developer, I want to understand how to build fact creators and retrievers so that I can test my rules and rulesets in Microsoft Rules Composer and use those rulesets with my Azure Logic Apps Rules Engine project.
1313
---
1414

15-
# Build fact creators and retrievers to use with rules and rulesets (Preview)
15+
# Build fact creators and retrievers to use with rules and rulesets
1616

1717
[!INCLUDE [logic-apps-sku-standard](../../../includes/logic-apps-sku-standard.md)]
1818

19-
> [!IMPORTANT]
20-
> This capability is in preview and is subject to the
21-
> [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
2219

2320
To create facts for your rules engine to use during business rules development and testing, you can build a *fact creator*, which provides your engine with an array of .NET objects. You can also build a *fact retriever* that inserts long-term or slowly changing facts into your rules for evaluation during execution.
2421

articles/logic-apps/rules-engine/create-manage-vocabularies.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,10 @@ ms.date: 01/27/2025
1212
#CustomerIntent: As a developer, I want to build vocabularies so I can use them with rulesets for my Azure Logic Apps Rules Engine project.
1313
---
1414

15-
# Create and manage vocabularies to use with rulesets using the Microsoft Rules Composer (Preview)
15+
# Create and manage vocabularies to use with rulesets using the Microsoft Rules Composer
1616

1717
[!INCLUDE [logic-apps-sku-standard](../../../includes/logic-apps-sku-standard.md)]
1818

19-
> [!IMPORTANT]
20-
> This capability is in preview and is subject to the
21-
> [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
2219

2320
A *vocabulary* is a collection of *vocabulary definitions* that use friendly names for the facts used in rule conditions and actions. Vocabulary definitions make rules in your ruleset easier to read, understand, and shareable by multiple people in a specific business domain. For example, tool developers responsible for integrating rule authoring into new or existing applications can consume vocabularies. Vocabularies bridge the gap between business semantics and implementation.
2421

0 commit comments

Comments
 (0)