You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello. I have two questions...
#1: If you have 5 "ConfiForms Rules for Field Definition" defined in a form are they evaluated in sequence?
#2: In regards to the lookup filter in "ConfiForms Rules for Field Definition", is the left side of the filter the source form? I'm having some issues where a lookup is always true and setting the value I want set. But it should not always return. I'm doing a date lookup in another form and whatever I do it always set the value even if the searched value is NOT in the form.
Form1:
Field1: Text
Field2: Date Picker (yyyy-MM-dd)
Form2:
Field1: Date Picker: (yyyy-MM-dd)
Rules for Field Def:
Value to set: Support=Yes
Lookup filter: Field2:[entry.Field1]
Source Form: Form1:<pageid>
In Form1 data I have:
Field1 Field2
Test3 2021-12-20
Test2 2021-11-08
Test1 2021-09-13
So if the datepicker is setup for 2021-09-06 it still sets the value and it should not. I expect when I put in the datepicker 2021-09-13 it would only set the value.
Not sure what I'm doing wrong.
The filter is not working as I expect. Maybe I have the filter incorrect. Just banging my head against the wall. Can anyone help?
Hi
Could you provide storage format of the page with your form?
That would be easier to troubleshoot
Alex
I have tried to design the form like you have and I can confirm that for this setup the lookup will not work.
This seems to be a bug in ConfiForms - to be more precise, the bug is related to setting the static values from the lookup and set "field definition rule"
We will look into this asap
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Alex, I just found that out myself. I can set a value from the form but not a static value like I did above.
Glad you found this. Make me feel better I"m not losing my mind. :-)
I think for now I'll go ahead and just place someone in the form to fill this value in as static.
Thanks!
Glen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry about that.
Confirmed to be a bug and we have fixed that now. Will publish an update for app shortly
Alex
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.
The version that has this bug fixed is available in the Atlassian marketplace
https://wiki.vertuna.com/display/CONFIFORMS/Release+Notes#ReleaseNotes-Version2.20
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.