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
Accept EBICS order timestamps with no decimals for seconds
For timestamps provided when sending an order request although the EBICS Specification generally refers to 3 decimal places for seconds being expected, it just points to the W3 datetime specification (https://www.w3.org/TR/xmlschema-2/#dateTime) which states that the form must be:
'-'? yyyy '-' mm '-' dd 'T' hh ':' mm ':' ss ('.' s+)? (zzzzzz)?
'.' s+ (if present) represents the fractional seconds;
The fractional second string, if present, must not end in '0';
This has been implemented by some vendors of EBICS Client software such that if the timestamp occurs on a whole second then the ('.'s+) is omitted entirely so the IBM EBICS Server needs to allow for and accept these.
THE ebicsserver.initialisation.request.timestamp.format property (e.g. yyyy-MM-dd'T'HH:mm:ss.SSSSSSZ) permits any number of decimal places up to the maximum specified (SSSSSS) but insists that the decimal point is provided. A value such as 2023-11-30T12:01:01Z should be accepted just as 2023-11-30T12:01:01.0Z is. Perhaps a value similar to the RegEx permitting definition of optional elements could be used instead?
Do not place IBM confidential, company confidential, or personal information into any field.