Payment type with multiple target accounts with ask question action

[mokospeti]

I have created a Basic tutorial on a solution to have multiple target accounts under one button on payment screen.

Continuing the discussion from Payment type with multiple target accounts:

Payment type with multiple target accounts

Create a new entity type for partners and assign partner to the ticket as an entity. When you do this a single Partner Account payment button (like Customer Account) will assign partner account to Target Account. If needed you can automate it further by creating a popup with ask question action and update ticket entity with Update Ticket Entity action.

MultiplePayment.pdf (700.6 KB)

[mokospeti]

Ideas why constraints on ticket closing does not work are welcome!

[QMcKay]

The reason the constraints do not work is because [:RemainingAmount] is not available to the Automation Command - it’s value in this case is null, blank, or undefined.

You need to move actions for Display Payment Screen and Close Ticket to a Rule that captures the event for Payment Processed… this event will return the correct value for [:RemainingAmount], so the Action constraints will work as expected.

[mokospeti]

Thanks, it works!