Decision Management (ODM,ADS)

 View Only
  • 1.  Auditing track on business rules edition

    Posted 20 days ago

    Hi experts, we have a requirement for an auditing track to report issues when the business user enters a non-compliant value in a rule. For instance, imagine that user is creating a discount rule with a 200% discount. User should be warned in edition time and rule marked as erroneous, preventing the deployment of the service until it has a reasonable value.

    It's like having meta-rules to check business-rules.

    I can imagine:

    • creating a value editor to checks discount limits in edition-time. But requires DC customization, and customer does not want any DC customization.
    • defining an excel domain with allowed values: {0.5, 0.75, 1.0, 1.25, ....., 10.0} (this is kind of ugly) 

    ¿Any other idea? ¿ever had a similar requirement?



    ------------------------------
    Eduardo Izquierdo Lázaro
    Automation Architect
    DECIDE
    Madrid
    609893677
    ------------------------------


  • 2.  RE: Auditing track on business rules edition

    Posted 19 days ago

    There is an interesting project in DecisionsDev  https://github.com/DecisionsDev/odm-transformation-advisor. Here the DC repository is loaded into memory and rules are run against those objects to identify the characteristics of the rule projects.

    I wonder if you could do the same  with you own rules to check the content of the repository. 



    ------------------------------
    Alain Robert
    ------------------------------



  • 3.  RE: Auditing track on business rules edition

    Posted 19 days ago

    Hi Eduardo,

    Using BOM domains is the way to go with this. Domains prevent a rule author entering an invalid value in a rule. 

    See the ODM documentation here:

    https://www.ibm.com/docs/en/odm/8.12.0?topic=domains-



    ------------------------------
    Peter Warde
    peterwarde@rulearchitect.com
    ------------------------------



  • 4.  RE: Auditing track on business rules edition

    Posted 19 days ago

    You can also use the rule authoring extension ValueChecker which can validate input for a business-specific BOM type. 

    See the ODM documentation here:

    https://www.ibm.com/docs/en/odm/8.12.0?topic=extensions-integrating-value-checker



    ------------------------------
    Peter Warde
    peterwarde@rulearchitect.com
    ------------------------------



  • 5.  RE: Auditing track on business rules edition

    Posted 19 days ago

    Yes, buy customer don't want extensions / customizations in DC



    ------------------------------
    Eduardo Izquierdo Lázaro
    Automation Architect
    DECIDE
    Madrid
    609893677
    ------------------------------



  • 6.  RE: Auditing track on business rules edition

    Posted 19 days ago

    This was my first option, but it may work in some cases, in other the domain would be endless. For instance if the rule set a limit (Double) that cannot be in any case higher than 1.000.000. No way to set a domain here for the limits that can be set. You need to check the compliance in the XOM or in another rule in the same service, that should not be visible or editable y the user.       



    ------------------------------
    Eduardo Izquierdo Lázaro
    Automation Architect
    DECIDE
    Madrid
    609893677
    ------------------------------



  • 7.  RE: Auditing track on business rules edition

    Posted 19 days ago

    Or you can run a set of validation rules at the end to check the values - only accessible by an admin user.
    I use a rule like this to validate some input data. e.g. for a mortgage loan-to-value the rules expect a percentage in the range 0 to 100. So if the value passed in is 0.5 for example then I know the user/system has used 0..1 for the LTV percentage so I multiple the value by 100 and add a warning.



    ------------------------------
    Andy Macdonald
    ------------------------------



  • 8.  RE: Auditing track on business rules edition

    Posted 19 days ago

    Thanks Andy, yes this is a way, that make more complicated the design of the service, but may work.

    The idea of Alain is more complex, but also interesting.



    ------------------------------
    Eduardo Izquierdo Lázaro
    Automation Architect
    DECIDE
    Madrid
    609893677
    ------------------------------



  • 9.  RE: Auditing track on business rules edition

    Posted 18 days ago

    I'd suggest that the issue is bigger than just ensuring that the business user has entered legitimate values. One must ensure that the user has entered correct values. If the user can't be trusted to enter legitimate values, what does that say about the your confidence that they'll enter correct values?

    I think the real solution involves some level of validation -- be it test scenarios, simulations or approval chains (@see Validating and testing decision model services)



    ------------------------------
    Raj Rao
    Principal Consultant
    RuleScape Consulting LLC raj.rao@rulescape.biz
    ------------------------------