Overriding rules

vinsnash · Post by **vinsnash** » Mon Dec 07, 2009 5:00 pm

I have a set of two rules that cover 90% of situations. When creating an instance the rules set two attributes depending on a third which is calculated first. This is working nicely. There are occasions when the 'rule' values need to be overridden during creation.

The two dependent attribute are list boxes with the allowed values. After the values are calculated by the rules, if I change them by selecting another value from the list box they revert to the 'rule' values as soon as I visit another attribute field.

Can I somehow have my cake and eat it too?

Thanks for any help.

Vins Nash

tford · Post by **tford** » Mon Dec 07, 2009 5:06 pm

Sounds like you should add IS NEW condition to this rule.

vinsnash · Post by **vinsnash** » Mon Dec 07, 2009 6:11 pm

The rule does use the "IS NEW" condition. The attributes can be changed after the instance is saved.

I have a thought. Can a "Yes/No" be added to a form that is not an attribute but is only there to aid data entry decisions?

Vins Nash

tford · Post by **tford** » Mon Dec 07, 2009 8:42 pm

Can a "Yes/No" be added to a form that is not an attribute but is only there to aid data entry decisions?

Not sure what you mean by this.

You can have a Yes/No attribute that does not appear on the form.

BobK · Post by **BobK** » Mon Dec 07, 2009 8:46 pm

In the conditions of your rules add something like the following

BO.Attribute IS UNDEFINED

vinsnash · Post by **vinsnash** » Tue Dec 08, 2009 10:18 am

Back in my procedural language programming days I could put a button or check box on a form that wasn't included in the "record" but only served to aid in decisions about data being entered or changing the focus to another field out of the tab order etc.

My solution was to add a yes/no attribute with an initial value of 'No'. If the user sets it to 'Yes' then the rule is ignored i.e. If 'YesNo' = 'No' If age < 13 Then MemberType is 'X' ...

Thanks

Vins Nash

RocketRod · Post by **RocketRod** » Tue Dec 08, 2009 9:45 pm

How about you put your Yes/No attribute on the regularuser BO and have a process (buttton) that first sets the attribute to Yes then updates (saves) the BO and resets the attribute to NO. You can use the LoggedInRegularUser in your rules on the BO.

Cheers Rod

vinsnash · Post by **vinsnash** » Tue Dec 08, 2009 10:29 pm

That sounds like a good idea. It gives a little more security. I can limit overrides by user.

Thanks

Vins Nash