IBM Z Software
This portal is to open public enhancement requests against IBM Z Software products. 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 updates on 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
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thank you for raising this requirement. It is being closed as a duplicate of existing RFE 147569
http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=147569
Thank you for this RFE.
Today, API input validation is performed using the bounds of the respective fields in the underlying service definition. For example, if a header is mapped to a CHAR field in the service, the input value is checked against the maximum length of the field. If a header is mapped to a numeric field, the input value is checked against the minimum and maximum values of the field. There exist two special cases where a field in the service is overridden as type Date or Boolean. When a header is mapped to a service field that is overridden as type Date, the value is checked to be in Open API Date format and to be a valid calendar date. When a header is a mapped to a service field overridden as type Boolean, the value is checked to be either true or false.
While Open API and JSON schema support specifying a custom range or pattern to be used when validating a field, they do not support injection of a temporal or non-static element to a range or pattern. For example, Open API and JSON schema cannot express something of the form "No more than two hours from the current system time".
Would it meet your needs if you were to specify that your timestamp header was of type Open API DateTime so that input values are checked to be in DateTime format as well as valid according to the calendar?