- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi @hetfidd,
We had the same issue and the only solution could come up with was to create a different scheduled workflow to update the status.
The status is stored in "nms:couponValue" schema. All the used coupons are linked to a broadlog record.
If the status is Available and message-id>0, then you can set the status to "Consumed" or you can extend the "nms:couponValue" and set to different enum value according to you requirement.
Cheers,
Deb