VP not refreshing after process runs

rbross

Hello,

I created a new VP using the Column Layout. Query on top, Small query on bottom just displays a total field from SystemSettings. Set option to have the calc process run when the VP is initialized. Also have process run when user check a certain field in the edit form of the top query and saves the form. I have the refresh option set on the total query so it will refresh anytime the calc total process is run, but the total displayed never changes.

What am I missing?

Roger

tford

Did you also set the BO SystemSettings to trigger auto refresh?

rbross

In the query that uses SystemSettings, Yes. Is there some place else I need to look?

Roger

tford

Also have process run when user check a certain field in the edit form

What BO is this form editing?

rbross

The Edit form is for the AVX Sales Ledger BO.
Line 1 of The VP has a query of AVX Sales Ledger
Line 2 of the VP has a query of SystemSetting with one Attribute on it Total Credit Due.

When the user checks the Box that the Credit has been reported and clicks Save & Close I trigger the process Calc_Total_AVX_Credit.
I have refresh set in both querys to refresh after this process has run.

Roger

rbross

GOT IT!
I had to put the Rule on the AVX Sales Ledger BO.
IF AVX_Sales_Ledger IS NEW OR AVX_SalesLedger WAS CHANGED Then
SystemSettings.TotalAVXCreditDue=SUM AVX_Sales_Ledger.CreditAvailable WHERE (AVX_Sales_Ledger.ReportedToAVX IS UNDEFINED OR AVX_Sales_Ledger.ReportedToAVX='No')

Then in the Query of the AVX Sales Ledger Credit I set the Refresh properties to refresh when AVX_Sale_Ledger BO was changed.
Watching the log I can see the Rule Execute to update the SystemSetting.TotalCreditDue. I have the box ticked to run the process calc Credit Due after saving the AVX Sales Ledger Form but the process never ran, not sure why?

Looks like don't need to call the process anyway as I have the same SUM expression as a Rule on the AVX Sales Ledger BO.

Not sure if this was the best way to do this but it is working 😃

Roger

tford

This absolutely looks like the best way to do this, Roger.

Getting your mind around rules based approach of AwareIM takes a while, but in the end if you put the correct rule in on a BO, you don't have to constantly be including it in various processes like in old COBOL structured-programming days.

Re:

IF AVX_Sales_Ledger IS NEW OR AVX_SalesLedger WAS CHANGED Then

You don't really need this in your rule because this is implied in every rule that is put under a BO. If you look at the Config tool tree, you will see that there are two places to put a rule for a BO ... one is for when an instance if new and changed instances and the second is for deleted instances.

Good work, Roger!

rbross

So are you saying I can take out the IF statement on the Rule and just have the "Then" portion on this Rule and it will still execute when needed?

Roger

tford

That's correct Roger

rbross

Tom,

So on all my Rules for the AVX Sales Ledger BO that have IF( AVX_Sales_Ledger IS NEW OR UNDEFINED OR
AVX_Sales_Ledger.Attribute IS UNDEFINED I can get rid of those If Statements and just have the "Then" statements correct?

Roger

tford

Basically this is implied:

IF AVX_Sales_Ledger IS NEW or AVX_Sales_Ledger IS CHANGED

any additional IF's that you add to a rule on a BO are implied to have this condition as well.

I'm not even sure what this bold part below would do .. it's the UNDEFINED part that I don't understand:

IF( AVX_Sales_Ledger IS NEW OR UNDEFINED OR AVX_Sales_Ledger.Attribute IS UNDEFINED

You might however want to have a rule that has an IF AVX_Sales_Ledger.Attribute IS UNDEFINED

rbross

I do have BO.Attribute IS UNDEFINED for some of the rules. But it looks like I Can take off the IS NEW for the BO line in the IF STATEMENTS.

Thanks for the assistance.... 🙂
Roger