Decision Management (ODM,ADS)

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?

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. 

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?

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-

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. 

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?

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

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-

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. 

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?

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-

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. 

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?

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?

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.

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?

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?