Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,555,206
Community Members
 
Community Events
184
Community Groups

Restricting Confiform fields with CSS not working for all field types

Hi Alex,

I have a form where entries are created by one person and updated by another person. At different stages we want some fields to be locked down to certain people, but available at other times. 

The CSS code "pointer-events: none;" works for most field types, but we're finding that for Date fields, User fields (including multi select) and Smart Drop down fields the restricted user can still action the fields.

We can't use the "Editable By" field attribute as it needs to be restricted sometimes, but not all the time.

Are you aware of any other way to restrict fields?

1 answer

0 votes
Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 22, 2023

Hi @Erin Smith 

"Editable By" could accept a value from another field, via [entry.field_name]

Basically you can control who can edit through "another field" in the form... if that makes sense

Alex

Hi Alex, 

Except we only want to restrict who can edit under certain circumstances, so using the Editable By field wouldn't work.

For example, we want the Requestor to be able to edit the field while it is in Draft or New Request Status, but once it's in Submitted to Governance Status we want the field locked down to everyone but the Governance team.

Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 23, 2023 • edited

And that is what my proposed solution supports... You use another field that manages the "edit permissions" on this field... 

Little demo: http://recordit.co/Wjgx5wGl7J

Bah, TD has that link blocked, lol. Can you send a screen print, or paste the code here? My brain just isn't quite getting what you're saying.

Alex Medved _ConfiForms_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 24, 2023

screen.gif

How about this animated gif?

Alex

Unfortunately that didn't work (at least it didn't work as far I I understand the gif). Do you have time on Monday to jump on a quick call and I can show you what I'm doing and you can tell me what I'm doing wrong?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events