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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
This requirement has been evaluated. Looking at current plans, it is not likely that
this would be implemented in future zOS Connect releases, so correspondingly
this requirement is being rejected. You have an opportunity to resubmit in twelve
months time if you wish it to be considered then.
This solution is really complex and will be located at API's level not at Service Interface level.
I cannot understand how the value "Omitted", "Yes" or "No" can be passed to the IMS or CICS service into a CHAR of size 1.
The meaning of my request is to only allow a default value for boolean type for "Service interface" like it this possible for other types..
Would the following JSONata expression satisfy the need?
Explination: If the boolean property Account.isOpen exists in the JSON and is true, then the value "Yes" is assigned. If the boolean property Account.isOpen exists in the JSON and is false, then the value "No" is assigned. If the boolean property Account.isOpen does not exist in the JSON then the value "Omitted" is assigned. $exists(Account.isOpen) ? Account.isOpen ? "Yes" : "No" : "Omitted"
No it's not a requirement for a third value.
When the field is not provided in request payload we want to be able to set a default value like other fields in the service interface.
Setting a default value for Booleans is not supported. At current, the client is expected to send in either true or false. In the Service Interface Editor you specify which value to store in the data structure field for each of true and false.
Is the requirement for a third state where neither true or false is received (the property is omitted from the JSON)? That would be three mappings/states: true, false, default (omitted).