I have a tracker created through ConfiForms that has a "Status" dropdown field with three options - Open, In Progress, Closed. When ever a new record is created, by default the status is set to Open. But as we work on the record, we use inline editing on a TableView to change multiple fields of the record.
My requirement is, can we send a custom mail using IFTTT only when the Status field specifically is modified (i.e. from OPEN to IN PROGRESS and then to CLOSED). We might make other changes within the record but that shouldn't trigger a mail.
I have seen this Checkbox Approach in the documentation but since we do inline editing on a TableView, this won't work for us.
I have also seen the Change Log example in the documentation which talks about using the "hasChanged(propertyname)" method and was wondering is there a way to use this in the Condition field for IFTTT?
Any other approach is equally welcomed!
Of course you can use hasChanged(fieldname) in conditions!
You can also have a condition that tracks the transition from one value to another - https://wiki.vertuna.com/display/CONFIFORMS/Virtual+functions
See the documentation for "hasChanged" function
Hi Alex, as always you are a saviour.
This works exactly has needed!
But now I have another question for you.
I tried using the "_previousState" function mentioned in the link you shared, to add from which Status is the request transitioning to. So I simply added "_previousState.Status" in the Field Name for a Form Field Macro to reference the previous state as you can see below.
Now it did work correctly but since the Status field in my form uses the "Status" field type itself which at the back end is saved using its constant value (i.e. - red is "error", green is "success"), the "_previousState" function displays the constant value and not the actual value of the field.
In the below example, I transitioned the status from Completed (green i.e. success) to Open ( red i.e. error). But in the final example as you can see, the previous state shows the constant value and the normal field works correctly. Is there anyway to fix this?
Hello Community! Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events