Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Coupon Module Status on the Coupon Value table does not change from Available to Consumed when assigned

hetfidd
Level 2
Level 2

There is a status field in the coupon value (nms) table.  This field has an enumeration of Available or Consumed.

 

We are using an individual coupon and then calling the coupon code from the coupon table (nms) in a delivery template to add it into the template.

 

When this happens - it is an out of the box function.   But it doesn't update the status of the coupon from available to consumed.   This is completely different than redeemed and nothing we do flips the coupon to consumed. 

 

What good is a status of the coupon value being assigned if it doesn't get updated.  It doesn't get updated when the coupon is redeemed either.  It always says "Available."  How can we get this status to flip to "Consumed" when they are assigned?  It should do it automatically if we use the delivery template coupon assignment in the advanced tab on the delivery template.

 

Ideas?

Coupon
1 Accepted Solution
Deb007
Correct answer by
Level 5
Level 5

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

 

View solution in original post

3 Replies
Jyoti_Y
Community Advisor
Community Advisor

Hi @hetfidd ,

 

Have you written code to change status of coupon when attached in delivery?

If it's out of the box, you need to trace and find where exactly is the fault. You can check which function is called when coupon is added  and does that function performs status update? If yes, then is the status correctly updated.

 

Thanks,

Jyoti.

Deb007
Correct answer by
Level 5
Level 5

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

 

View solution in original post

Sukrity_Wadhwa
Employee
Employee

Hi @hetfidd,

 

Were you able to resolve this query with the help of any of the given solutions or do you still need more help here? Do let us know.


Thanks!