Johan Coetzee (Customer) asked a question.

Certain Rulesheets not executing the actions although conditions are met

Ive been having issues with Corticon JS. I have a project which I originally built in Corticon 6.3, it still works perfectly in 6.3 and 7.0. Recently I imported the same project into Corticon JS as a client want to use the JS version to do testing with, but suddenly some of the rulesheets in the project is not execuring correctly.

I have found that when I put something in the 0 column it still executes, but the issue is with the condition. The only condition is a age, but and the age is available on the system, but the actions for the condition is not executing.


  • Seth Meldon (Progress Software)

    Hi Johan,

    That's strange--definitely not normal behavior, so tough to diagnose the problem without looking closer. Could you upload a screenshot of/attach the rulesheet and ruletest? Some steps that come to mind to start:

    • If you haven't already, upgrade the rule assets in the same way (right click project name, upgrade rule assets) as you would when upgrading from 6.3 to 7.0
    • To test the simplest possible action, remove everything from the action rows, but create a rule statement that refers to the condition-only rule column, and test to see if that comes back in ruletest output
    • If all else fails, create a new rule project, and recreate a simple structure that mirrors the original project to see if you get this behavior once again. This will at least isolate out if the problem is in fact related to having been created in Corticon Studio for server deployments versus Corticon.js studio.
  • Johan Coetzee (Customer)

    Hi Seth, thank you for the quick response!

     

    I already upgraded all rule assets, as well as validating the project before running any tests.

     

    See the attached screenshots where I have somewhat isolated the issue. I have tested with the 0 column that the rulesheet will execute, and all actions in the 0 column does execute. The bottom two variables in Bold, iHasPPU and iHasWaiver is initiallly set in a defaults rulesheet to 'false'. then the attached rulesheet is supposed to execute. In condition 87 it evaluates whether pol.iHasPPU is 'false' (which it is), and just sets pol.iHasWaiver to 'true'. This is however not being done in as you can see in the output of the test.

     

    When the same project is in 6.3 and in 7.0 it executes perfectly though.

    RulesheetRuletest section 

     

  • Johan Coetzee (Customer)

    Hi Seth

    It seems that it is an importing issue. From what I could see there was issues with importing the scope of the rulesheet as well. One of the variables that is used in the conditions did not show in the scope as it normally would. I would expect for the condition to be showing red but is did not, so I initially also did not see it happening.

     

    Could you advise how I would be able to log a request to have something like this fixed by your developer team?