When to apply UI Policy(Eureka) "On load"

Stephen W_
Giga Guru

In Eureka UI Policies now have a little checkbox to "Apply the catalog UI policy actions when the form is loaded or when the user changes values on the form"

The description is incorrect, stating that it is one or the other.     But it seems like they forgot to add another checkbox.

The effect is actually onLoad and onUpdate when "On load" is checked, and onUpdate when it is not checked.  

How can I set it to fire only onLoad, and not also onUpdate?

Thanks,

-Stephen

1 ACCEPTED SOLUTION

//Uncheck the Option Reverse if false, and it will not run on update//



Reverse If False means it will literally do the opposite to the fields if the conditions are not met.   Think of it like a toggle.



UI Policy: "Hide field if Status is Closed"


Reverse if false = "Show field if Status is not Closed"



Either way, it still runs when you change a field value.



The original post is absolutely correct.   They should have given us two checkboxes: On Load, and On Field Change.   A third would be nice: "On Before Save"


View solution in original post

6 REPLIES 6

ghsrikanth
Tera Guru

Hi Stephen,



I checked both the fuji and eureka environments, there is no option that you have mentioned. I may be missing something - all i see is this -



Screen Shot 2015-04-24 at 1.52.33 AM.png



Uncheck the Option Reverse if false, and it will not run on update



Apart from the UI policy, if possible its always advisable to use Client Scripts as they give more control over forms with scripting.



--


Sri


//Uncheck the Option Reverse if false, and it will not run on update//



Reverse If False means it will literally do the opposite to the fields if the conditions are not met.   Think of it like a toggle.



UI Policy: "Hide field if Status is Closed"


Reverse if false = "Show field if Status is not Closed"



Either way, it still runs when you change a field value.



The original post is absolutely correct.   They should have given us two checkboxes: On Load, and On Field Change.   A third would be nice: "On Before Save"


Paul, I didn't realize reverse if false was ALSO tied to updates.     Seems like another design mistake, since I may want it to reverse if false on load only(probably not necessary though), or not want it to reverse but still affect updates..   (By that logic, if "On load" and "reverse if.." are both unchecked, then the policy would never fire at all. )



Might work in this case though.   Thanks!


Srikanth, your screenshot looks like Calgary to me.(Did they revert back to that look in Fuji?)  
This is how it looks in Eureka:onload.JPG