This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
YPMValidateCouponUE needs to do default coupon validation after the UE is invoked
On Version: IBM Sterling OMS V10 Fix Pack: 32
When ValidateCouponUE is enabled, Sterling does not give YPM_RULE_INVALID response if the coupon does not exist. The CouponStatusMsgCode field in the output is blank. Consumer applications need error reason for the appropriate handling of response.
According to the YPMValidateCouponUE java documentation, when a system rule exists to enable default validation to be performed after user exit is invoked. The system rule is named "perform the default validation for coupons". When this rule is enabled, coupons that were returned as valid by the user exit will have the default validation logic performed on them.
But in reality, it is not working as expected, this default rule validation is not performed when the system rule is enabled. We would like to have this validation done in addition to any custom validation in the UE, as there are a number of system validation
Another thing we noticed is that the Sterling performs other validations like YPM_RULE_EXPIRED, YPM_RULE_NOT_ACTIVE, but it is not doing YPM_RULE_INVALID, which seems like a missing functionality.
What is your industry?
How will this idea be used?
As a customer doing online shopping, I will be able to receive error reason after the default validation for coupons.
Do not place IBM confidential, company confidential, or personal information into any field.