BO Form dynamic re-calculation problem

marc

AwareIM 3.0 Build 1027
If have a BO with a DropDown Field and a Textual rule
IF package.payment='Cash'
THEN
READ PROTECT package.creditcard FROM ALL

I have also checked the Use rule in dynamic re-calculation on forms in the Advanced Tab

The fileds:
DropDown Field payment with vaules (Cash, Creditcard)
DropDown Field creditcard

With the a.m. rule i would like to hide the creditcard field if i choose cash in the payment field while filling in the form. If i save the form and reopen the form with Cash selected the creditcard field is hidden.

How can i hide the creditcard field depending on the selected value in the payment field without saving and reopen the form?
The Use rule in dynamic re-calculation on forms does not do anything in a.m. case.

Rem

This is a post from Pete: http://www.iportcentral.com/DynamicTest.zip

Download it and test it, it worked for me maybey it can help you as well.

/Rem

marc

Hi Rem,

works perfectly, thank you for the suggestion.
Do you have an idea how i can hide the AdminUseOnly field in the example, if i remove the AdminUseOnly field from the form the recalculation does not work.

Rem

Well, sorry!

I have taken that issue with the support but they did not understand why it was needed (or what I meant) and neither do I, but obviously it is.

So if someone knows how to get rid of it please drop a line!

/Rem

pbrad

Hi Guys,
As best that I can figure it out, it seems that a non-calculated field cannot be hidden in response to a dynamic rule unless a calculated field that is visible on the form is also impacted in some way by the same dynamic rule. You can get rid of the label so that only a checkbox shows but of course, that is still not perfect.

Although thinking about it, it doesn't need to be a distinct calculated field and it probably doesn't need to be a checkbox so if you have any other calculated fields on the same form already, try using that field and just set it to its current value so that nothing actually changes. I suspect that this will work, I didn't think to try this approach originally. Please let me know if you have any luck with this approach.

Cheers,
Pete

tford

All,

I took Pete's BSV and tried some things per his suggestion.

New test bsv: http://www.iportcentral.com/BSVs/DynamicTest2.bsv

Conclusions so far:

1- "Other" atttibute does NOT have to be a CALCULATED attribute nor a checkbox attribute. The other field can be ANYTHING. See Test.AnyOtherField in the attached BSV.

2- 1st key is to have Test.AnyOtherField NOT effected by READ PROTECT rules.

3- 2nd key is to have a dynamic rule that triggers Test.AnyOtherField to change whenever the Visible/Invisible attribute changes. See 2 rules named AnyOtherField and AnyOtherField2 in attached BSV. I used Pete's suggestion to try making an attibute equal to itself & it worked.

4- Make sure you have "use rule during initialization" checked on the rules that effect visibility. See 2 rules in attached BSV: ReadProtect and ReadProtect2.

Maybe with these new clues, this bug can be found and fixed 🙂

Tom

tford

Support,

One more clue if you are trying to find and fix this:

In the BSV above I added one more condition in the two rules: AnyOtherField and AnyOtherField2. The new condition is AND 1=0 which will cause the action NEVER to be executed.

It seems that the mere EXISTENCE of these 2 rules: AnyOtherField and AnyOtherField2 causes this process to work. These 2 rules never even have to have the action execute.

If you want me to send you this test BSV, let me know.

Tom

tford

A couple of new learnings about dynamic rules & visibility:

1- Dynamic rules that have READ PROTECT actions should be in a rule that has no other actions other than READ PROTECT actions.

For example, this works:
If LoggedInRegularUser.ReportsCountry.Country<>'ALL' Then
READ PROTECT LoggedInRegularUser.Reports201 FROM ALL
READ PROTECT LoggedInRegularUser.Reports211 FROM ALL

This does not work:
If LoggedInRegularUser.ReportsCountry.Country<>'ALL' Then
Another non-READ PROTECT action goes here
READ PROTECT LoggedInRegularUser.Reports201 FROM ALL
READ PROTECT LoggedInRegularUser.Reports211 FROM ALL
Another non-READ PROTECT action goes here

2- To trigger dynamic READ PROTECT rules in a BO Attribute that has a PEER relationship to a BO presented as a drop-down:

a- you have to "look through" -- to the referenced attribute -- see bold below:
If LoggedInRegularUser.ReportsCountry.Country<>'ALL' Then
READ PROTECT LoggedInRegularUser.Reports201 FROM ALL
READ PROTECT LoggedInRegularUser.Reports211 FROM ALL

b- the associated "trigger" rule is as follows:
If LoggedInRegularUser.ReportsCountry WAS CHANGED Then
LoggedInRegularUser.AnyAttribute=LoggedInRegularUser.AnyAttribute

This may seen like common sense to some, but it took me a while to get it all to work together.

Tom

tford

Dynamic READ and READ PROTECT now work starting with build 1161.

No more triggers and extra attributes are needed like Pete described earlier in this thread.

All you need to do is a dynamic rule like:

If RegularUser.ShowIt2='No' Then READ PROTECT RegularUser.T2 FROM ALL

If RegularUser.ShowIt1='No' Then PROTECT RegularUser.T1 FROM ALL

In the Advanced tab of the rule, be sure to check "use rule in dynamic recalculation on forms"

With this new functionality, you can have attributes that appear / disappear on a form depending on the values that users put in another attribute.

Tom

marc

Hi Tom,

thank you for your follow up, and code samples...

himanshu

This is great feature which can help and solve many issues, it will give more flexibility on the UI.

Tom has provided a good help here regarding the DYNAMIC CALCULATION on the form.

Thanks Tom and keep it up!! 😃

himanshu

Hi tom,

with the above functionality can we make appear/disappear to the subdetails form in a master form. i tried but not get success..

suggestions!!

tford

Not sure what you mean by a "subdetails form". That's not really AwareIM terminology.

Tom

himanshu

Ooops!! sorry for the above,

Here is the example what i want to say...

i have one object customer
second object bankdetails

customer has one to many relationship with the bankdetails object.

i have a attribute showhidebank, with this attribute can i make bankdetails object visible or not visible as u had done in your last bsv.

difference is here we are using a subobject (bankdetails) form and in the last it was attribute only.

tford

Himanshu,

I tested & it looks like you can do that, but not dynamically.

Tom