Simpler Library Benefits DMN implementation

[prestoncabe]

Can a benefit's definition be declarative only?

• Name
• Description
• Version (eventually, when we support versioning per benefit and per eligibility check)
• List of Eligibility Checks
  • Each check:
    • Default alias for this benefit (e.g. PersonMinAge -> "Client is at least 60 years old")
    • Parameters

Need to look at the existing library benefits and test the above.

• one possible caveat: should every check be part of the library or can the benefit itself have a "custom check" that is invisible to the rest of the library? Maybe such a check would also be importable to the builder somehow as a custom check for the given user?