Using Reference Attributes on Form Button Applicability

kklosson

For a form button operation, I want to use the Applicability. But I need to know the value of a reference parent attribute. It does not seem that AwareIM can reconcile this. I have also tried creating a shortcut with the same negative result. Really? So it seems that AwareIM does not join all tables when a form object is opened. Seems logical. But perhaps there could be an option to bring one or more related parent objects into context so that this sort of thing could be done. I'm not sure how I'm going to accomplish this task now.

ACDC

If you had a Yes/No Attribute pointing to the reference Object.attribute, and then refer the Yes/No attribute in your applicability rule, surely that would work. I use this method all the time for applicability on references

kklosson

Well I'm-a-tellin'-ya it doesn't.

kklosson

ACDC: do you do this in an applicability rule to show/hide a form element? It simply appears to me that AwareIM has no ability to look above the current object of the form for these rules.

BenHayat

kklosson wrote
ACDC: do you do this in an applicability rule to show/hide a form element? It simply appears to me that AwareIM has no ability to look above the current object of the form for these rules.

This is a limitation in Aware not to be able to see the objects further down the object graph. To solve this so I can access the data for applicability rule, I had to create a chain of Shortcuts to get to the data I needed for the rule to apply.

The biggest problem with shortcut is that, once created even for one attribute, then that connected objects falls into "Eager loading", meaning, every time you loop through the main object, all the shortcut objects will get loaded into server memory. That means slower response time to get more data from DB and more memory usage on the server side.

Hidden Areas like this, can cause app performance once data grows.

kklosson

My parent is only one reference up the chain. Even when I create a shortcut in the form object, no joy. So I don't get how you resolved your issue at all, Ben.

BenHayat

kklosson wrote
My parent is only one reference up the chain. Even when I create a shortcut in the form object, no joy. So I don't get how you resolved your issue at all, Ben.

This was a long time ago and I needed to get to grand parent. I was able to get to the parent from rule but not to grand parent. So in the parent, I created a SC to grand parent and used the SC in grand child.

ACDC

ACDC: do you do this in an applicability rule to show/hide a form element? It simply appears to me that AwareIM has no ability to look above the current object of the form for these rules.

Yes, create a rule on the Object that sets a Yes/No (made for the applicability rule)and then refer to that in the applicability rule

kklosson

I'm not sure what you mean. Are you saying to create an attribute in the primary object and cascade the changes via a rule? That sounds awful...

ACDC

If that's the only way then why not ? besides don't be scared to use the rules engine that's what it's there for.

4xjbh

It sounds awful but once I understood the performance hit sc's have I have avoided them as much as possible. Relying on rules, processes and stored procedures.

Instead of adding the suffix SC to the attribute I use AttributeTXT to keep track of which are which.

kklosson

I'm afraid the last two posts haven't clarified for me what approach you are using. Are you saying to put the attributes I need into the main object and set them based on the parent using a rule?

4xjbh

Yes that is correct. The rule can be in the parent or on the object one level down. It will just depend on how your objects are related.

Is the value you want to monitor likely to change often in the 'grandparent' if not duplicate to the parent when the parent is first created.