-
Notifications
You must be signed in to change notification settings - Fork 594
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
I can deploy a DMN decision #8067
Comments
@saig0 We could consider to drop the |
We'll also need to consider the intents we want to support for these record types: |
EDIT: I had not yet seen #8065, but it's already covered. |
The process record has only one intent: The distribution is happening on the deployment record. But not on the process records. Does this make sense for you? |
Yes, the naming is not fixed yet 👍
|
@saig0 can you help me to understand the following topics?
|
@nazlikaya regarding your questions:
Yes. Thank for the hint 👍 I updated the description.
Yes. The |
Description
I can use a Zeebe client to deploy a DMN decision. As a result of the deployment, Zeebe produces records on the log stream to reflect the deployed decisions.
DecisionRecord
with the properties:decisionId
decisionName
version
decisionKey
decisionRequirementsKey
decisionRequirementsId
DecisionRequirementsRecord
decisionRequirementsKey
decisionRequirementsId
decisionRequirementsName
decisionRequirementsVersion
namespace
resourceName
resource
checksum
DecisionRequirementsDefinitionRecord
for each DMN resource (i.e. represents the DRG - aka. DRD)DecisionRecord
for each decision within a DRGNote that the resources of the DMN are only stored in
DecisionRequirementsDefinitionRecord
and not inDecisionRecord
to avoid duplication of the resource (and reaching the max. message size).blocked by #8060
blocked by #8063
Edit: I changed the names from
DecisionRequirementsDefinition*
toDecisionRequirements*
(removed theDefinition
part).The text was updated successfully, but these errors were encountered: