SOLVED: A size limitation exists for conditionals

JonP

How is this possible? I have an attribute that the log viewer separately evaluates to true and false for the same comparison when the value is UNDEFINED. I just included the lines that matter and rearranged the sequence for ease of comparison.

Evaluating condition AssessmentStateSurvey.sc_Priority>0
Condition evaluated to false: <UNDEFINED>>0
Condition evaluated to true: <UNDEFINED>>0

Evaluating condition AssessmentStateSurvey.sc_Priority=0
Condition evaluated to false: <UNDEFINED>=0
Condition evaluated to true: <UNDEFINED>=0

UNDEFINED issue.png

PointsWell

I am assuming that sc_Priority is a shortcut?

If so try doing your evaluation to the referenced object directly

eg IF BO.ps_Priority.Code>20 THEN xxxx

I've had issues with evaluating shortcuts in HTML (different to what you are doing I know) but I found that evaluating against the actual referenced item worked whereas the shortcut didn't.

BobK

Every where the condition evaluated to true, like
Condition evaluated to true: <UNDEFINED>>0
you were using "NOT (AssessmentStateSurvey.sc_Priority>0)"
So the condition evaluated to false and the NOT changed to to true

It may not be in your code, but if your actual condition uses ELSE, Aware might be generating the NOT

JonP

Good catch, Bob. That's embarrassing. I'm actually not using NOT in my conditions, but for some reason, AIM does when it evaluates them.

Regardless, I'm still having a problem with AIM evaluating the conditions properly. I have a sequence of 6 If/Then statements. AIM steadfastly refuses to evaluate one of them (2nd from last). I've tried changing the order and rewording the if statement (including using Mark's suggestion of not using the shortcut shown below) to no avail.

If AssessmentStateSurvey.Factor.AverageRelevance>0 AND AssessmentStateSurvey.Type IN 'Opportunity', 'Threat' Then
  LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: 0,y: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',size: '+AS_STRING(AssessmentStateSurvey.sc_Priority)+',category: `'+AS_STRING(AssessmentStateSurvey.sc_Factor)+'`,color: `blue`},' 
 Else If AssessmentStateSurvey.Factor.AverageRelevance>0 Then
  LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',y: 0,size: '+AS_STRING(AssessmentStateSurvey.Factor.AverageRelevance)+',category: `'+AS_STRING(AssessmentStateSurvey.sc_Factor)+'`,color: `blue`},' 
 Else If AssessmentStateSurvey.Factor.AverageRelevance=0 AND AssessmentStateSurvey.Type IN 'Opportunity', 'Threat' Then
  LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: 0,y: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',size: 0.05,category: `'+AS_STRING(AssessmentStateSurvey.sc_Factor)+'`,color: `blue`},' 
 Else If AssessmentStateSurvey.Factor.AverageRelevance=0 Then
  LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',y: 0,size: 0.05,category: `'+AS_STRING(AssessmentStateSurvey.sc_Factor)+'`,color: `blue`},' 
 Else If AssessmentStateSurvey.Type IN 'Opportunity', 'Threat' Then
  LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: 0,y: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',size: 3,category: `'+AS_STRING(AssessmentStateSurvey.sc_Factor)+'`,color: `blue`},' 
 Else
  LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',y: 0,size: 3,category: `'+AS_STRING(AssessmentStateSurvey.sc_Factor)+'`,color: `blue`},'

The weird thing is, if I change the instance that is being bypassed from "Threat" to "Weakness", it gets evaluated. If I change it back to "Threat" and switch the if/then so that I check for "IN Strength, Weakness" and have Opportunity/Threat as the catch-all "Else", there is no difference in the result. I checked the FIND statement (shown below) and there is no reason for that instance not to be included.

FIND AssessmentStateSurvey WHERE (AssessmentStateSurvey.AssessmentState=AssessmentState AND AssessmentStateSurvey.Person=LoggedInPerson AND AssessmentStateSurvey.ScoreValue IS DEFINED AND AssessmentStateSurvey.Type IS DEFINED AND AssessmentStateSurvey.Type<>'Not Sure')

Jaymer

Hey Jon,

weird thing is, if I change the instance that is being bypassed from "Threat" to "Weakness", it gets evaluated. If I change it back to "Threat" and switch the if/then so that I check for "IN Strength, Weakness" and have Opportunity/Threat as the catch-all "Else", there is no difference in the result. I checked the FIND statement (shown below) and there is no reason for that instance not to be included.

When you say you check the FIND statement.
Do you mean you looked in the logging window and you see that after the FIND statement there are the correct number of instances found?

JonP

Hey Jaymer,

I said that wrong. Yeah, FIND found 6 objects (the screenshot only shows 1 because I was trying IN BATCHES OF 1 to see if that would help) and actually did evaluate all 6. But it refused to trigger the condition when sc_Priority (or equivalent) IS UNDEFINED and Type = Opportunity or Threat. Oddly, it has no problem when Type = Strength or Weakness and/or sc_Priority is a number. All 6 should render because I have a catch-all Else condition. I used a DISPLAY MESSAGE to verify that only 5 are included in DataForSWOT.

BobK

IMO AIM does not handle multiple Else If statements very well, I try to avoid them.

JonP

What's the alternative?

PointsWell

JonP wrote
FIND found 6 objects (the screenshot only shows 1 because I was trying IN BATCHES OF 1 to see if that would help) and actually did evaluate all 6. But it refused to trigger the condition when sc_Priority (or equivalent) IS UNDEFINED and Type = Opportunity or Threat.

If you have multiple items returned from a FIND it is better to evaluate them in a sub process otherwise it will evaluate the last item in the FIND.

As for sc and undefined I would try evaluating against the actual referred item instead of the shortcut.

BobK

Multiple rules.

Rule 1
If AssessmentStateSurvey.Factor.AverageRelevance>0 AND AssessmentStateSurvey.Type IN 'Opportunity', 'Threat' Then
LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: 0,y: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',size: '+AS_STRING(AssessmentStateSurvey.sc_Priority)+',category: '+AS_STRING(AssessmentStateSurvey.sc_Factor)+',color: blue},'
Else If AssessmentStateSurvey.Factor.AverageRelevance>0 Then
LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',y: 0,size: '+AS_STRING(AssessmentStateSurvey.Factor.AverageRelevance)+',category: '+AS_STRING(AssessmentStateSurvey.sc_Factor)+',color: blue},'

Rule 2
If AssessmentStateSurvey.Factor.AverageRelevance=0 AND AssessmentStateSurvey.Type IN 'Opportunity', 'Threat' Then
LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: 0,y: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',size: 0.05,category: '+AS_STRING(AssessmentStateSurvey.sc_Factor)+',color: blue},'
Else If AssessmentStateSurvey.Factor.AverageRelevance=0 Then
LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',y: 0,size: 0.05,category: '+AS_STRING(AssessmentStateSurvey.sc_Factor)+',color: blue},'

Rule 3
If AssessmentStateSurvey.Factor.AverageRelevance<0 AND AssessmentStateSurvey.Type IN 'Opportunity', 'Threat' Then
LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: 0,y: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',size: 3,category: '+AS_STRING(AssessmentStateSurvey.sc_Factor)+',color: blue},'
Else If AssessmentStateSurvey.Factor.AverageRelevance<0 Then
LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',y: 0,size: 3,category: '+AS_STRING(AssessmentStateSurvey.sc_Factor)+',color: blue},'

edit
REMOVED

edit 2
disregard edit 1, it did not make mush sense. My only excuse is that I was in a hurry and not thinking clearly.

PointsWell

BobK wrote
Multiple rules.

Rule 1
If AssessmentStateSurvey.Factor.AverageRelevance>0 AND AssessmentStateSurvey.Type IN 'Opportunity', 'Threat' Then
LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: 0,y: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',size: '+AS_STRING(AssessmentStateSurvey.sc_Priority)+',category: '+AS_STRING(AssessmentStateSurvey.sc_Factor)+',color: blue},'
Else If AssessmentStateSurvey.Factor.AverageRelevance>0 Then
LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',y: 0,size: '+AS_STRING(AssessmentStateSurvey.Factor.AverageRelevance)+',category: '+AS_STRING(AssessmentStateSurvey.sc_Factor)+',color: blue},'

Rule 2
If AssessmentStateSurvey.Factor.AverageRelevance=0 AND AssessmentStateSurvey.Type IN 'Opportunity', 'Threat' Then
LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: 0,y: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',size: 0.05,category: '+AS_STRING(AssessmentStateSurvey.sc_Factor)+',color: blue},'
Else If AssessmentStateSurvey.Factor.AverageRelevance=0 Then
LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',y: 0,size: 0.05,category: '+AS_STRING(AssessmentStateSurvey.sc_Factor)+',color: blue},'

Rule 3
If AssessmentStateSurvey.Factor.AverageRelevance<0 AND AssessmentStateSurvey.Type IN 'Opportunity', 'Threat' Then
LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: 0,y: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',size: 3,category: '+AS_STRING(AssessmentStateSurvey.sc_Factor)+',color: blue},'
Else If AssessmentStateSurvey.Factor.AverageRelevance<0 Then
LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',y: 0,size: 3,category: '+AS_STRING(AssessmentStateSurvey.sc_Factor)+',color: blue},'

This will be very inefficient as it will trigger three rules instead of one. Each one checking everything. If the Business Rule is not working with multiple if/else if then define the condition for a process and pass it off to that, then it would trigger only once.

Using this multiple Business Rule approach can have multiplying effects if you have forgotten to switch off Referred Rules on the related Business Objects.

On rereading the issue I have another question.

Are you trying to use FIND in a business rule? If so you are setting yourself up for a world of pain especially if it returns more than one BO. Definitely pass this off to a Process.

Also if the IN ‘Threat’, ‘Weakness’ is not working have you checked using BO.attribute=‘Threats’ OR Bo.attribute =‘Opportunity’

JonP

Thanks Mark,

Yeah, I'm using processes, not rules in this case. If all I did was add-to DataForSWOT with each new instance, then I could use rules. But sometimes I have to wipe DataForSWOT and re-populate it for an updated instance, so processes work better.

I've been using a sub-process after the FIND for that conditional. There's no other way to do it that I know of since you can't place an If statement directly after a FIND statement (without stuffing it in a sub-process) I don't think. I tried it with and without batches of 1.

I also tried replacing the IN syntax with the clunkier OR syntax. No luck.

PointsWell

I’m Sean. Mark is Eagle99

I’m out of ideas then. My suggestion of last resort is a debug with DISPLAY MESSAGE and checking the values of expected attributes at various stop points.

JonP

Sorry Sean, brain fart. Thanks for your efforts.

JonP

I decided to split the conditional sub-process into two sub-sub-processes and it worked. The sub-process was changed to this:

If AssessmentStateSurvey.Type IN 'Opportunity', 'Threat' Then
 BuildIndExtSWOT_Matrix
Else 
 BuildIndIntSWOT_Matrix

The first sub-sub-process (BuildIndExtSWOT_Matrix) looks like this:

If AssessmentStateSurvey.Factor.AverageRelevance>0 Then
 LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: 0,y: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',size: '+AS_STRING(AssessmentStateSurvey.sc_Priority)+',category: `'+AS_STRING(AssessmentStateSurvey.sc_Factor)+'`},' 
Else If AssessmentStateSurvey.Factor.AverageRelevance=0 Then
 LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: 0,y: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',size: 0.05,category: `'+AS_STRING(AssessmentStateSurvey.sc_Factor)+'`},' 
Else
 LoggedInPerson.DataForSWOT=LoggedInPerson.DataForSWOT+'{x: 0,y: '+AS_STRING(AssessmentStateSurvey.ScoreValue)+',size: 3,category: `'+AS_STRING(AssessmentStateSurvey.sc_Factor)+'`},'

The logic for this approach vs the previous approach is EXACTLY THE SAME. Therefore I can only conclude that there is a size limitation for conditionals above which they become unstable. Bob, I can see why you stick to rules. Now I'm getting a little paranoid about my other conditionals.