-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update DMN related documentation on main-kogito #4515
Update DMN related documentation on main-kogito #4515
Conversation
This PRs brings DMN docs changes introduced on main in 1H2023 - https://github.com/kiegroup/kie-docs/pull/4464 (cherry-pick completely the same content) - https://github.com/kiegroup/kie-docs/pull/4512 (cherry-pick was not possible, we remove 'Business Modeler hub' term in this PR)
5030b56
to
c601567
Compare
doc-content/kogito-docs/src/main/asciidoc/dmn/chap-kogito-using-dmn-models.adoc
Outdated
Show resolved
Hide resolved
@@ -583,6 +583,8 @@ The following decision table hit policies are supported in DMN: | |||
** *Collect Min (C<):* Outputs the minimum value among the matches. The resulting values must be comparable, such as numbers, dates, or text (lexicographic order). | |||
** *Collect Max (C>):* Outputs the maximum value among the matches. The resulting values must be comparable, such as numbers, dates or text (lexicographic order). | |||
** *Collect Count (C#):* Outputs the number of matching rules. | |||
** *Rule Order (R):* Collects output from multiple rules into list ordered according to rules order. It is very similar as 'Collect' without any aggregation function, but with explicit consistent ordering in the final list as defined in the table. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
** *Rule Order (R):* Collects output from multiple rules into list ordered according to rules order. It is very similar as 'Collect' without any aggregation function, but with explicit consistent ordering in the final list as defined in the table. | |
** *Rule Order (R):* Collects output from multiple rules into a list ordered according to rules order. It is very similar to 'Collect' without any aggregation function, but with explicit consistent ordering in the final list as defined in the table. |
@@ -583,6 +583,8 @@ The following decision table hit policies are supported in DMN: | |||
** *Collect Min (C<):* Outputs the minimum value among the matches. The resulting values must be comparable, such as numbers, dates, or text (lexicographic order). | |||
** *Collect Max (C>):* Outputs the maximum value among the matches. The resulting values must be comparable, such as numbers, dates or text (lexicographic order). | |||
** *Collect Count (C#):* Outputs the number of matching rules. | |||
** *Rule Order (R):* Collects output from multiple rules into list ordered according to rules order. It is very similar as 'Collect' without any aggregation function, but with explicit consistent ordering in the final list as defined in the table. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
** *Rule Order (R):* Collects output from multiple rules into list ordered according to rules order. It is very similar as 'Collect' without any aggregation function, but with explicit consistent ordering in the final list as defined in the table. | |
** *Rule Order (R):* Collects output from multiple rules into a list ordered according to rules order. It is very similar to 'Collect' without any aggregation function, but with explicit consistent ordering in the final list as defined in the table. |
doc-content/kogito-docs/src/main/asciidoc/dmn/chap-kogito-using-dmn-models.adoc
Outdated
Show resolved
Hide resolved
doc-content/kogito-docs/src/main/asciidoc/creating-running/chap-kogito-creating-running.adoc
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jomarko Very minor suggestions. Otherwise your content looks good to me. Thank you!
…p-kogito-creating-running.adoc Co-authored-by: Kalyani Desai <[email protected]>
…g-dmn-models.adoc Co-authored-by: Kalyani Desai <[email protected]>
…g-dmn-models.adoc Co-authored-by: Kalyani Desai <[email protected]>
@kaldesai thank you, suggestions committed and pushed. |
@kiegroup/gatekeepers please merge |
squashing and merging as requested |
This PRs brings DMN docs changes introduced on main in 1H2023
Thank you for submitting this pull request
JIRA: (please edit the JIRA link if it exists)
link
referenced Pull Requests: (please edit the URLs of referenced pullrequests if they exist)
How to backport a pull request to a different branch?
In order to automatically create a backporting pull request please add one or more labels having the following format
backport-<branch-name>
, where<branch-name>
is the name of the branch where the pull request must be backported to (e.g.,backport-7.67.x
to backport the original PR to the7.67.x
branch).Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.