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
Implement 'Hold' for a bulk product order for up to 30mins (or XX mins) as per OMoC SF ticket TS002131182
Add following functionality for 'On Hold' bulk items up to XX mins. As per following scenario ... We have created a remorse hold, to hold order's for 30 mins. To resolve the hold, we have created hold processing agent which is abstract transaction of process order hold Type. And part of the YFSProcessOrderHoldTypeUE code of the custom agent, we have added custom code to check whether to resolve the hold or not, if the condition is not being satisfied hold will not be resolved. In that case if the hold is not resolved, available_ts in yfs_task_q is getting incremented by 15 mins. After 15 mins passed, we could observe the custom agent picking particular record based on available_ts in yfs_task_q and once again checking whether to resolve the hold or not, if the condition is satisified hold will be resolved, else once again available_ts in yfs_task_q will be further incremented by 15 mins. This behavoir is happening for single order.
But when we trying to validate the behavoir for bulk orders, what we could see is agent is not immediately picking the order after the available_ts is passed in yfs_task_q. Due to which time to resolve the hold is increasing upto 1 hr.
Ex: available_ts in yfs_task_q is at 12:30, for bulk orders we could see agent is picking the record at 12:37. And if the load is being increasing further the agent is picking the record at 12:47, which 17 mins more than the available_ts.
What is your industry?
How will this idea be used?
To provide bulk order hold functionality and improve the customer experience.
Do not place IBM confidential, company confidential, or personal information into any field.