I have a question on how the local variables in a load expression behave when th

georgej over 8 years ago

I have a question on how the local variables in a load expression behave when the expression is invoked from SAIL (which are at times TEMPO SAIL Dashboards).It took long time for analysis as the issue was causing several production issues. Let me try to explain the issue with some a SIMPLE SAIL and Expression Rules. Attached is a simple SAIL which has a one section layout. When you enter input "IndSection1" text box and change the date value in "End Date Field", "Tst_LoadIssueExpr" (code snippet is below) is invoked and result is shown in "ResultSet" text box.
When you change the flip the value in "IndSection1" between blanks and non-blanks, as expected the Boolean result displayed in "ResultSet" text box is not changing. But if you modify the below "Tst_LoadIssueExpr" ri!input directly rather than saving to a local variable ,the result shown is as expected.
Can anyone explain what is causing this weird behavior. In actual production code ,this is a n...

Tst_LoadIssues.txt

Discussion posts and replies are publicly visible

Parents

0 georgej over 8 years ago

Thanks for the inputs Tim, every time the sub-rule is invoked isn't a fresh execution of the same. Could you please guide me to any documentation which specifically talks about how load() behaves in a sub-rule. The issue here is ,when you have a complicated report ,which has multiple girds being displayed depending on user action, it is not possible to modularize the same as separate SAIL rules. Grid requires load() variables and they are not refreshed. Is there some best practice on modularizing SAIL components while making complicated reports
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 georgej over 8 years ago

Thanks for the inputs Tim, every time the sub-rule is invoked isn't a fresh execution of the same. Could you please guide me to any documentation which specifically talks about how load() behaves in a sub-rule. The issue here is ,when you have a complicated report ,which has multiple girds being displayed depending on user action, it is not possible to modularize the same as separate SAIL rules. Grid requires load() variables and they are not refreshed. Is there some best practice on modularizing SAIL components while making complicated reports
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data