[Epic] Evaluate DMN decisions

[saig0]

Description

This issue represents the epic Evaluate DMN decisions. All required issues are listed below:

• Deployment:
  • In the model API, a business rule task can reference a DMN decision  #8060
  • Reject the deployment if the decisionId is invalid #8061
  • Reject the deployment if the result variable is missing #8172
  • Reject the deployment if a business rule task references a DMN and have a job type  #8173
  • Create a new module for DMN evaluation #8063
  • I can deploy a DMN decision #8067
  • Store DMN decision in the state #8069
  • Assign the correct version for deployed decisions and DRGs #8174
  • Extend the deployment record for DMN decisions #8072
  • Export deployed decisions and DRGs to ES #8077
  • Distribute DMN decision to other partitions #8567
  • Align deployment rejection message for DMN resources #8806 ¹
• Response include decisions: ¹
  • Create a new gRPC deploy request for DMN resources  #8065
  • Handle the new gRPC deploy request  #8074
  • In the Java client, I can deploy DMN resources #8075
  • In the Go client, I can deploy DMN resources #8076
• Execution:
  • Reuse the FEEL value mapper and function provider for the DMN module #8081
  • DMN module exposes API to evaluate decisions #8082
    • I can set the value mapper and function provider in the builder dmn-scala#104 ¹
  • A business rule task can evaluate a DMN decision #8080
    • Avoid parsing DMN decisions for every evaluation #8571 ¹
  • I can define the decision id of a business rule task as expression #8779
  • Use Zeebe's clock for evaluating decisions #8093 ¹
    • I can set the clock in the builder dmn-scala#105 ¹
  • Fetch variables by name when evaluating a decision #8092 ¹
    • Fetch the variables lazy from a given context dmn-scala#106 ¹
  • Store a temporal value from an expression as variable  #7054 (to return a temporal output value of a decision)
• Incidents:
  • Create an incident if the referenced decision is not deployed #8094
  • Create an incident if the evaluation of a decision fails #8095
• History/Audit/Monitoring/Metrics:
  • DMN module returns the history of a decision evaluation #8112
    • I can read the index of a rule from the parsed decision table dmn-scala#136 ¹
  • Write an event for a decision evaluation #8115
  • Export the evaluated decision result to ES #8116
  • Write an event if a decision evaluation failed #8235
  • The event of a decision evaluation references to the evaluated decisions #8643 ¹
  • Add version to the evaluated decisions referred from a evaluated decision record #8867 ¹
  • https://github.com/camunda-cloud/zeebe-analytics/issues/22 ¹
  • Export evaluated DMN decisions/elements to Prometheus/Grafana #8805
• Documentation:
  • I can read how to evaluate DMN decisions with a business rule task camunda-docs#421
  • I can read how to model a DMN camunda-docs#422
• Clean up:
  • Ensure backwards compatibility for DMN with further versions #8653 ¹
  • Add property-based tests for business rule tasks with DMN #8807 ¹
  • Verify that the evaluation of DMN decisions doesn't pollute the state #8808 ¹

¹ - not required for MVP. It should be done but can be postponed if necessary.

[korthout]

@saig0 I think we're missing an issue to cover deployment rejection for missing resultVariable as described in #8060.

[korthout]

#8069 implies updating the decision and decision requirements using a version number, but this should probably be an additional issue, in which we introduce the UPDATED (or similar) intents.

[saig0]

The epis is done. All major issues were implemented. 🚀