You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I am not sure why the Condition for Fire Action parameter of the IFTTT rule macro stops working whenever there is an "AND".
I am intended to incorporate a ConfiForm Send Email IFTTT macro into a user macro so that I would be able to get all members from a certain group as a string by using the Velocity Template.
In addition, I wish to capture the condition from the macro user as a condition for Fire Action. However, the problem occurs whenever, on the parameter textbox of the user macro, the user gives multiple conditions with "AND" in-between.
The Template of the user macro is the following:
## @Param group:title=group|type=string|required=true|desc=The group that is selected as the email receipiants
## @Param condition:title=condition|type=string|required=true|desc=The condition that determines whether the action is going to fire
#set($group = $paramgroup)
#set($agents = "")
#set($separator="")
#foreach($user in $userAccessor.getMembers($userAccessor.getGroup($group)))
#set($agents=$agents + $separator + $user.name)
#set($separator=",")
#end
$agents
<p class="auto-cursor-target">ifttt</p>
<ac:structured-macro ac:name="confiform-ifttt" ac:schema-version="1">
<ac:parameter ac:name="condition">@paramcondition</ac:parameter>
<ac:parameter ac:name="extras3">true</ac:parameter>
<ac:parameter ac:name="action">Send Email</ac:parameter>
<ac:parameter ac:name="event">onCreated</ac:parameter>
<ac:parameter ac:name="title">New Worksheet Creation Request</ac:parameter>
<ac:parameter ac:name="who">$agents</ac:parameter>
<ac:rich-text-body>
<p>
<ac:structured-macro ac:name="confiform-field" ac:schema-version="1">
<ac:parameter ac:name="fieldName">worksheetName</ac:parameter>
<ac:parameter ac:name="withLabel">true</ac:parameter>
</ac:structured-macro>
</p>
<p>
<ac:structured-macro ac:name="confiform-field" ac:schema-version="1">
<ac:parameter ac:name="fieldName">file</ac:parameter>
</ac:structured-macro>
</p>
</ac:rich-text-body>
</ac:structured-macro>
And the conditions that the user gave were this two: (Neither of them works)
!file:[empty] AND [entry.reasonOptions]:0
!file:[empty] AND reasonOptions:0
Hi
Does it work when it is not with the user macro?
The construction like this is (syntactically) correct. As you check "field name" gains the value
!file:[empty] AND reasonOptions:0
What field type is "reasonOptions"?
Alex
Hi Community! We're thrilled to share that Team Calendars for Confluence is now a built-in feature for Confluence Data Center releases 7.11 and beyond. A long time favorite, Team Cale...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.