Do not make your attributes RO at object level
Determine the RW / RO / WO - ness on the window. Then you publish the window with the RO setting as the default window, and the window with the RW setting to the test group only
Thanks for the quick response Elizabeth.
This should work good but the problem I have is, there are lot of windows which I need to recreate. So I was looking for a Filter or BOO Script which I can use across all the windows.
if dynamic windows can over-ride a write-once, then you could use that in 7.6. you can reuse the same dynamic window calculation on multiple windows.
the only problem is, I don't think dynamic windows don't kick in until the user touches a field that triggers other fields to recalculate. So they might need to touch another field first before the calculation makes the field editable.
That is exactly the problem with Dynamic forms. They lack the ability to do something on Window creation based on the user or their group(s). Triggers are useful and solve several problems but some things can't wait for a user to do something.
Example: I have a SSN/DOB attribute on new account requests. Only 1 group should be able to see that attribute. As it works now, the SSN/DOB shows up until a trigger event hides it. Well, that's too late. The analyst has already seen (and written down) the SSN/DOB if they wanted to. That's bad. I ended up using a view rule and a second window so my standard analysts NEVER see the value. Dynamic forms would be far more useful if something happened "On creation" of the Window.
i agree 100%, i ran into that same thing.
there is also an issue where hidden fields can appear to be mandatory to the save-check, which is very confusing to users if they can't see the field in question!
I wonder if a copy rule targeting the trigger field would work to get the calculation to work right away?
A windows calculation can do this. You don't have to worry about the limitations described above because you only want to change the field's properties until AFTER the record is saved. From that point on dynamic calculations get triggered each time the window is launched.
The calculation would just need to use the GetCurrentGroupName() function and act accordingly.