On my form once when record is created the user has the ability to edit their entry until they set a "submit" field to Yes. At that point the edit function is disabled. And all of this works fine.
However, it disables the edit function for everyone including form Admins.
I know I can still use the form admin UI to still edit a record as Admin regardless, but that option doesn't use the form layout (table format only) which for a large form is not the best option.
1. Is there a way to ensure that when you disable the edit function that it is retained for Admins (or superusers)?
or
2. Is there a way to force the edit on the Admin UI to use the form layout?
Update
What I have done for now is in the condition for hiding the edit function I have put
field1:CONDITION AND [entry._user]!=USERID
It seems to work but I will need to check it from other users screens, is this correct?
Update 2
Well I thought that would work but it doesn't so I may have the syntax wrong or it's just not possible. Be good to have an answer if anyone knows
Thanks
Hi
The conditions are written as ConfiForms filters
So it's gonna be something like this (as far as I understand your comment)
field1:CONDITION AND !ownedBy:[entry._user]
But it much wiser to use userInSecurityGroup functions and alike from ConfiForms Virtual functions to check user group
Alex
Hmmm, owned by won't work in this situation. Basically I am trying to block everyone from seeing the edit button except a specific USER. This suggestion would still allow the record owners to edit the record (which once submitted they cannot for audit reasons).
As for the groups, I did take a look, but again a similar issue. Since multiple people would be administrators it's the same issue, they all need to be blocked. There can only be one user who has the right to edit a record once a record has been submitted (i.e. field1 status changed to YES).
A side question here, how do I create a security group, maybe if I could create one then assign that specific user to that group I could use your suggested approach.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can try this
_user.username:hardcodedusername OR field1:[entry._user.fullName]
The first one checks for the logged in username and matches with the hardcodedusername
The second one checks for the logged in user's fullname against the value from another field (field1) in your form
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.