WAS Changed To Rule

leopdurr

I have this rule to prohibit the use of Multiple Admin user with the same User Rights

If ThisSystemUser.UserRights WAS CHANGED TO 0 AND (ThisSystemUser.LoginName<>'admin' OR ThisSystemUser.LoginName<>'Admin') Then
REPORT ERROR 'User Right 0 is only for System Developer.'

The rule only Evaluate the WAS CHANGED TO condition it does not Evaluate the entire condition and make display the result base on the entire condition.

Is my rule correct. If the Value "0" exist in the "admin" user profile it will work. but if the Value never exist and I change the value to "0" it will not accept the change. it will Trigger the Result, which is the REPORT ERROR message.

pbrad

I don't really understand your question as it is worded a little awkwardly however you might consider creating a BO called Administrator and adding it to the SystemUser group. Then define a new Visual Perspective for the Administrator access level that calls this BO to edit the user rather than the RegularUser BO. Now you have a method to set attributes such as UserRights as visible only to the Administrator if desired or limit the dynamic choice lists to include '0' for administrators or not include that choice for all other users. That way your rule is not required at all.

I often use this same approach so that no user other than a user with an administrator access level is allowed to create another user of access level administrator. It also allows me to make sure that no client users can ever have access to processes that only I want to have access to as a 'Super User'.
Cheers,
Pete

leopdurr

Let me explain further

What I did is that within the BO RegularUser I add a new attribute call UserRights with Choices (0-5) where 0 is SuperAdmin. When I am setting up users or editing users I want only 1 user to have the UserRights 0 assign to them. If someone else is assign UserRights 0 then an error should be generated. The Rules that I use in this post is what I use to control this function.

I hope this is more clearer. I use this UserRights for other Function because of the Type of application I am creating.

Is there an other Function that I can use to give the same result or what is wrong with my rule? I don't want to use the Visual Prospective method because I am using the UserRights option in Query, Buttons, Processes, etc.

pbrad

A bulletproof method would be to create a new BO called userrightlevel with two attributes; status (unlocked,locked) and value. make default value of status='unlocked'. Then create your six instances of this object (0,1,2,3,4,5).

Change your SystemUser.UserRights to use 'Dynamic Choices' based on userrightlevel and filter the values with a query WHERE userrightlevel.status='unlocked'. When 0 is chosen for the first time, have a rule that sets the status of 0 to 'locked' and it will not show up as an available value in the dropdown list anymore.

There are almost always a variety of ways to approach a problem in AwareIM, you will just need to decide which is the best.

Pete

leopdurr

I will use that method and update this post to let you know how it goes.

thanks so much.

leopdurr

Thanks for you suggestion. I implement you idea and it is perfect. thanks again.