Unexpected behaviour when trying to skip pledge payment
I am currently working with an organisation looking to use CiviPledge. One requirement is that occasionally payments get missed, in which case the client would like the subsequent payment amount to be doubled. Currently the behaviour to allow this is non-intuative and lacks the flexibility to do exactly what the user wants.
I made a couple of non-successful attempts to try this initially:
Attempt 1
My initial assumption was that the table of pledge payments would have a cancel button next to each payment. This does not appear to be the case.
I would have expected such a link, which when clicked I would have expected to ask what I wanted to do with the subsequent payments. Either:
- No change (reduce total pledge payment).
- Add extra payment to extra schedule
- Adjust next payment with rolled amount.
Attempt 2
Next I tried to record a payment with an amount of 0. The actual payment was recorded correctly with an amount of 0, but when there is no amount the radio buttons "adjust payment amount" and "Adjust Total Pledge Amount?" appear to have no effect.
Attempt 3
Next I tried to record a cancelled payment.
- Click "record payment" next to a pledge.
- Set the "Contribution Status" to "Failed"
- Click save
We now end up in a situation where it is impossible to reach the pledged amount because the price of the cancelled payment is not taken off the pledged amount, and no changes are made to the other pledged payments. Therefore the pledge will never reach the "Completed" status, unless edited via the API.
I'm not sure exactly what the solution is here, espcially in terms of the ideal UX, but its clear that as it stands pledges are lacking flexibility to correctly handle missed payments.