IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
The API for managing organizations allows the caller to specify the receiving, shipping and business calendars, but only by specifying the calendar key.
The key is typically a system generated value which is unique to the environment and therefore not useful in an interface.
Please allow for the API to specify instead the calendar id for these three calendars.
Better yet, allow the API to specify the Calendar details directly by adding an optional Calendar node to the API.
|What is your industry?||Retail|
How will this idea be used?
Legacy systems that feed OMS retail store location info typically also maintain store hours / calendar info. Consistency between these APIs greatly simplifies the integration points to maintain store hours and locations.
Consistency in the API (by allowing a foreign key to be specified by id, rather than by key) allows much easier integration to source or legacy systems. Keys cannot typically be used by interfaces as they can change between environments. Ids can be used as they can be specified externally when the calendar is created.
Do not place IBM confidential, company confidential, or personal information into any field.