Aggregate operations are not allowed as presentation conditi

weblike

hi,

I have a form where I want to hide a button depending on a condition. This is simple in other scenarios, but here is mine:

I have a support ticket app, and I want to add the ability that other users can subscribe to follow a ticket discussion like in this forum. I have made the process to INSERT the user in followers list.
My concern is to not allow duplicates in this list. I want to hide the subscribe button after the user subscribes and change it to "unsubscribe button".

but this kind of conditions are not allowed in forms

I guess this is easy to do, but in my approach seems it can't be done.
Any advice would be much appreciated.
thx,

customaware

I got around it using html/css buttons and IF SHOW SECTION_START / SECTION_END George.

<<IF Booking.TicketStatus='WAITLISTED' THEN SHOW SECTION_START>>
<button onClick="AwareApp.startProcessFromForm ('SetBookingTicketStatus_RESERVED','main', this, false)" type="button" class="agent_button" role="button"><i class="fa fa-flag-o">  </i> Set Ticket As Reserved</button>
<button onClick="AwareApp.startProcessFromForm ('SetBookingTicketStatus_CANCELLED','main', this, false)" type="button" class="agent_button" role="button"><i class="fa fa-minus-circle">  </i>Set Ticket As Cancelled</button>
<<SECTION_END>>

<<IF (Booking.TicketStatus='CAN BE ISSUED' OR Booking.TicketStatus='RESERVED') THEN SHOW SECTION_START>>
<button onClick="AwareApp.startProcessFromForm ('AgentUploadeTicket','main', this, false)" type="button" class="agent_button" role="button"><i class="fa fa-upload">  </i> Upload eTicket</button>
<button onClick="AwareApp.startProcessFromForm ('SetBookingTicketStatus_ISSUED','main', this, false)" type="button" class="agent_button" role="button"><i class="fa fa-flag">  </i> Set Ticket As Issued</button>
<button onClick="AwareApp.startProcessFromForm ('SetBookingTicketStatus_CANCELLED','main', this, false)" type="button" class="agent_button" role="button"><i class="fa fa-minus-circle">  </i>Set Ticket As Cancelled</button>
<<SECTION_END>>

tford

One workaround is to run a process that determines if the LoggedIn user is already a subscriber to the ticket in context. If yes, set a flag in LoggedInRegularUser flag attrribute, then refer to that flag in the form in question.

weblike

Thank you for quick replies,

I will try both of suggestions to see them in action.

Nice day,