Q: An attribute READ-ONLY on one form, Editable on another?

BenHayat

I have a series of attributes that can only be edited on one special form but be READ_ONLY on other forms;

*) So, I can't use PROTECT to make them READ_ONLY, because I can't set in rule to Protect an attribute if user is a special form.

*) I was going to have another attribute as a flag in LoggedInUser when user goes into Special form or Normal form, since there is no event when a form starts, I can't set that flag.

*) I was going to create a series of ShortCuts to those attributes to use them as READ_ONLY, but shortCuts don't work with the attributes in the same BO.

*) If I make them CALCULATED, then user can't edit them.

Do you guys know a clean way to solve this problem.

BLOMASKY

Ben, how are you calling the "Special" Form? If you always call it via a "special" process, you can have the logic there to make it Protected, right?

bruce

tford

Similar to what Bruce said, I would set a flag in LoggedInRegularUser that controls whether READ PROTECT is applied or not. So you would have two different processes for calling the form(s) for this BO and each would set the flag appropriately.

BenHayat

BLOMASKY wrote
Ben, how are you calling the "Special" Form? If you always call it via a "special" process, you can have the logic there to make it Protected, right?

bruce

Thanks Bruce;
I had tried that to have PROTECT before calling EDIT/VIEW the form and I get Internal error "PROTECT Action seems to be executing outside of Entity Context", even though I had passed the object to Process.
I think you can only execute it from Rule.

But I think I can set the flag in the process and then apply the PROTECT in Rule based on the flag. Let you now soon!

BenHayat

When I had got the error before, I kind of gave up on using the PROTECT in the Process. Now with setting the flag in the process and doing the PROTECT in the rule works.
One little issue though. Even after Edit/View the form, I try to Rest the flag and update LoggedInUser, the flag stays as ON (meaning READ_ONLY). Now I have to find a way to rest it.
Thank you for putting me back on that Track again.

BenHayat

tford wrote
Similar to what Bruce said, I would set a flag in LoggedInRegularUser that controls whether READ PROTECT is applied or not. So you would have two different processes for calling the form(s) for this BO and each would set the flag appropriately.

Hi Tom;
As I was typing my solution, you had also presented yours that I didn't see. And that exactly the way that I have to do it with two different processes
Thank Tom!

BenHayat

Thanks Guys, works like a champ. No side effects.
I just have to make sure I open that form with Process and not "Edit Object" 🙂