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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Confiforms: Allow status dropdown to only be updated by rules and disable edit via inline edit



I have a form with 2 dropdowns and 1 Status dropdown.

I have a field rules that set the Status dropdown based on values from other 2 dropdowns.

Desired outcome

I want Status value to appear in my TableView, but I do not want Status dropdown to be manually edited in my Table View with in-line editing enabled.

What I've tried

If I set edit restrictions on the Status field, then it will prevent the Status dropdown from showing when in In-line edit mode (this is what i want), however, the rules will not update Status (this is not what i want).


Are there other settings that can help prevent editing the Status dropdown via In-line editing, but still allowing to rules to update Status dropdown?

2 answers

1 accepted

0 votes
Answer accepted

This is how I solved it.  I changed from in-line editing to a modal dialog and only included the specific form fields that are editable within the Edit Controls.  This way, Status would not be editable when user edits entry, but the Table View would display Status after the Rules Definition performed the Lookup and set value.


You can set edit permissions on your status field (definition) - allowing it to be updated directly only by user in a certain group (group also can be set to something that "dont exist" and this will basically disable edits for everyone, as no one is in that "not existent" group).

And have an IFTTT rule to update it on form submit (create/modify), with enabled flag to bypass field permissions 

So, the rule will be able to update the field... but it won't be possible through UI


Hi @Alex Medved _ConfiForms_ , 

I am using Field Definition Rule "Lookup and set value" to set Status.  If switching to IFTTT rule, would I use IFTTT Copy Confiforms Data instead of Create(Update) Confiforms Entry?  I don't see options to bypass the editing restrictions on Copy Data IFTTT macro.

In original field definition rule (on form A), I am looking up a value in form B, with filter having conditions based on fields in form A entry.

Original "Lookup and set value" Rule:

<ac:structured-macro ac:macro-id="5a0b1ba8-3f26-48bb-a283-47c85286bc58" ac:name="confiform-field-definition-rules" ac:schema-version="1">
<ac:parameter ac:name="condition">!consequence:[empty] AND consequence:&gt;0 AND !probability:[empty] AND probability:&gt;0</ac:parameter>
<ac:parameter ac:name="fieldName">riskstatus=[entry.riskstatus]&amp;riskstatus.label=[entry.riskstatus.label]</ac:parameter>
<ac:parameter ac:name="values">consequence:[entry.consequence] AND probability:[entry.probability]</ac:parameter>
<ac:parameter ac:name="action">Lookup and set value</ac:parameter>
<ac:parameter ac:name="actionFieldName">consequence,probability</ac:parameter>
<ac:parameter ac:name="values2">riskmatrix:1022198450</ac:parameter>

I'm not positive that Copy Confiforms Data is the right rule to use to replace Lookup and set value.

Thanks in advance!

OK, this is something more complicated and it looks like you are looking up for some value to be set on the record

So, why not to use a dropdown for status if all you do is really looking up a label from some other form?

May be instead of a dropdown field type you can use something like hidden or readonly?


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events