ORN:V14.1
Jump to navigation
Jump to search
In case you do not want to wait for the official milestone build, you may install the nightly builds.
New and Noteworthy in TD/OMS V14.1
New Command Line (CLI) API | The following new CLI API has been made available in this release:
|
---|
01793 - A better quickfilter | The Quickfilter box has been enhanced.
The Quickfilter simultaneously searches on the following fields: Object Name, Description, Attribute, Application, Environment, Library, Source library, Source file, Source member, IFS name, and IFS directory. You can use *wildcards* in the search. There is no automatic wildcard* assumed anymore. |
---|
REST API Code Generation Extensions | The REST Generator has been enhanced
The RPG REST Generator now offers the following additional extensions:
|
---|
T00324 - Introduce JWT in Rest API. | The RPG REST Generator now offers to support JWT.
As explained above (REST API Code Generation Extensions) the RPG API code would be generated on the basis of what option we choose in the Generation Extensions dialog box. |
---|
GUI issues/enhancements resolved
- 01638 - Slow startup when MiWorkplace included
- A startup could take several minutes when the MiWorkplace editor was included during install. This has been fixed.
- 01794 - Compile failure decorator is lagging
- The compile failure decorator is not accurate. It could sometimes take a long time before the decoration was updated. This has been fixed.
- 01469 - Fill object file not registering *MSGF details
- In some situations, messages were not loaded in the fill object file process. This has been fixed.
- I29 - Slow at Promote and Connect with Rules
- X-Analysis is slow when multiple objects are selected in an application area. This has been fixed.
- I02090 - Length of numeric field is not valid.
- When we add fields using edit schema in Open API studio then it always returns the type "integer" for the numeric field. So we get the "The length of an integer or unsigned field is not valid." compilation message while compiling the generated rest API program. Resolved this issue.
- I02045 - The TD/OMS RDi and RCP now install the jt400 library version 10.7.
- This version of the jt400 library is used by the reporting plugin.
- I02097 - RCP installer did not show previously installed options.
- This has been fixed and would happen if the RCP being installed had a different version number than the currently installed.
Server issues/enhancements resolved
- 01782 - The registry API should also allow keyword values.
- Currently, the registry API cannot handle values. The GUI can do it. Resolved this issue.
- I02078 - Open events are at the bottom of the list
- Change the writing of the *OPEN events to also include a date (event service program). Change the title to status date and status time. Resolved this issue.
- IT228 - The default subset is not working in STRFM
- After saving the default subset, come out of the STRFM screen and go back, the default subset does not work. It works when the user goes to the subset screen and presses Enter key. Resolved this issue.
- I2105 - Pre-transfer check screen issue
- The sequence number field should have the right-justified values. Upon adding new records, after pressing enter, the action code should covert to CHANGE. Resolved this issue.
- 01780 - Put session user data outside QTEMP
- We have introduced a new registry setting OMQUSRDTALIB to control the location of the OMS user session data. When this registry setting is used, it can point to a library where the session data must be stored. The special value *OMSLIB is used to point to the OMS library.
- 01469 - Fill object file not registering *MSGF details
- Fill object file was not writing a new message field. Resolved this issue.
- 01783 - Registry programs do not use security to block users from using
- The registry settings may only be set by the application manager or the OMS manager by calling OMX001. Resolved this issue.
- 01784 - Do not use variant characters in description and keys
- The values "#" and so on may not be used in event keys and descriptions because this will display differently in different languages. This normally means a number instead use 'n'. Resolved this issue.
- IT226 - Change OMQRTVEK to add additional parameters
- Earlier this API used to return only 10 keys and corresponding values from the requested JSON string, but now it has been modified to return 20 keys and the corresponding values.
- I29 - Slow at Promote and Connect with Rules
- The Object Transfer back-end is now much faster.
- IT225 - Rest API generator issues
- Rest API was not generated correctly in a few scenarios. Resolved this issue.
- I02085 - Give priority to a default value if the parameter doesn't pass.
- When we generate the Rest API if the user doesn't specify the parameter then the default value (if it exists) of that parameter should be assigned. Resolved this issue.
- I02084 - To disable changing the current library
- The default behavior for a CGI program seems to be to make a program's library the current library for the duration of the program's execution. After the program ends, the current library reverts to QHTTPSVR. Resolved this issue.
- IT223 - Request is completed even without selecting reason code
- When we close the request and don't select the reason code and press F12. The request is completed. Resolved this issue.
- I02077 - Add API Event.
- We have added the event in TD/OMS API.
- I02079 - Add subscriber topic id to OMSBE
- Added subscriber topic id field in subscriber events file and also revised the event logic to make sure that the most qualified event should be logged.
- I02098 - Subscriber events must be written once per subscriber priority.
- If there are more subscribers listening to the event, only one subscriber was receiving the event. Resolved this issue.
- I02033 - SP action does not report an error
- Action program is called an SP action with a critical indicator. The program reports the error but the transfer continues regardless. Resolved this issue.
- I02099 - Issue in Manual FallBack
- The save file sequence number from the fallback library relied on the application code, the transfer code, and the sequence number instead of the transfer code, and the sequence number also "number of objects not restored" parameter was not populated correctly. Resolved this issue.