ORN:V17.0 Milestone 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 V17 Milestone 1
| Dependency Graph Improvements | It is now possible to
|
|---|
| More decorations on Tasks and Solutions | More decorations have been added in the tasks in the work management and in the solutions in the item editor.
Task decorations now include: active running jobs, version conflicts, compilation failures, ratification, comments. Solution decorations now include: active solution count, version conflict, compilation failure, compile overrides, labels, comments. In addition the task title has been added in the item editor together with its actions menu.
|
|---|
| Connection Rules support in Definitions | Connection rules and their details are now supported in the definitions view. Connection rules can now be viewed, created, copied, changed or deleted in the host and application levels. They can also be interconnected with each other with the "Continue with Rule" option in details of a rule.
|
|---|
| Q45 - Call via request data is not visible in dependencies | In older CL programs sometimes, a program call is performed by specifying a command in one of the following ways:
1. SBMJOB JOBQ(QBATCH) RQSDTA('CALL OMA002')
2. CHGVAR &RQSDTA VALUE('CALL OMA002')
SBMJOB JOBQ(QBATCH) RQSDTA(&RQSDTA)
Using the routing entries of subsystem QBATCH, the command in the RQSDTA parameter will be executed. TD/OMS would not show any dependencies of this call because they are program described. The source scanner has been enhanced to scan for these patterns in the RQSDTA parameter in CLLE CLP and CLP38 programs. Any string with the patterns 'CALL {LIB/}PGM' will now result in a dependency to PGM. If you created your own scanning rules, back them up before executing: INZSRCSCAN FORCE(*YES) to install the updated source scanner. |
|---|
| I02810 - Version conflicts dialog should not show potential conflicts by default | The Version Conflicts dialog has been enhanced to improve user experience by altering how potential conflicts are displayed by default.
In previous versions, the Version Conflicts dialog would automatically select all potential conflicts for review. This could lead to unnecessary clutter, as not all conflicts are critical or relevant to the user's current operation. The dialog now only selects the required conflicts by default, which are the ones that are most relevant to the user's current task. This change ensures that the user focuses on the important conflicts without being overwhelmed by less critical ones. Users can still manually review and select additional conflicts if needed.
|
|---|
| I02814 - 'Direct Connect' in context menu of Component | In the Components plugin, when connecting the object to the task the component will be immediately connected to the indicated task if Direct Connect Action is selected.
|
|---|
| I02838 - Adding Checkout Action on Component | The new action allows users to directly connect a component to a task and immediately check out the object if it resides in a higher environment (such as production). This functionality streamlines the workflow by bypassing the need for multiple steps when managing components.
|
|---|
| 02091 - Speed issue in the GUI | Two speed issue were resolved in the decoration framework of the Rich Client. If you notice UI freezes in the client, you should install this update. The decoration framework adds additional information to the Icons and Text
|
|---|
| New CLI API's | We are moving all TD/OMS business logic into separate programs for our back-end modernization project. These APIs can also be called using a command with the same name. To access additional information about these APIs, please click on the link below. |
|---|
| New REST API's | We have developed a set of new REST APIs. To access additional information about these APIs, please click on the link below. |
|---|
| E255 - VS Code Panels - Responsive to Dark Theme | We can now switch to dark or light inside VSCode. After switching reload the webviews from the VSCode by pressing:
|
|---|
| I02833 - REST APIs documentation | The REST APIs documentation is up to date. For more information, you can see REST APIs documentation. |
|---|
GUI issues/enhancements resolved
- E253 - OCTO Unneeded error messages.
- Unneeded error messages have been removed.
- E255 - VS Code Panels - Responsive to Dark Theme
- Added the theming button.
- I02897 - Switch Build Queue to show results from all users
- Now the build queue will show results from all users instead from the current user only.
- I02890 - Impact Analysis REST API memory leak
- The REST server had a memory leak due to an invalid pointer allocation.
- I02883 - An error is thrown during the initialization of the item editor when calling the loadRatificationColorAndTip method
- Fixed a problem where the ratification type for the task's environment was not loaded in the task for the item editor and component plugins.
- I02885 - Create new object wizard environment combo-box doesn't have values when opened from link
- Fixed a bug where the environment combo-box had no values loaded when the "Create New Object" wizard was opened from a link.
- I02876 - Create new object wizard fails on item editor and component plugins
- Fixed a bug where the "Create New Object" wizard was not working in the item editor and component plugins in OCTO.
- I02830 - Adding Compare functionality on the Version Conflict Wizard
- Object Code on the wizard of version conflict should be clickable, and adding the compare code option to enable user to compare to the previous codes on a new window/Tab.
- I02843 - Save on definitions doesn't update the properties view title and image
- Fixed a bug where the title and the image of the form in the properties view were not updated after a save when an entity is changed.
- I02812 - GUI Scheduling does not accept some formatting
- When the transfer job was scheduled in the GUI, some dates were not accepted by the process due to local specific date formatting.
- I02428 - CONFIRMTRANSFER - Registry setting does not work on the GUI
- When the registry setting to confirm a transfer with a password in the GUI is on, the password was not checked if it was valid. Also improved the speed of the internal operations done by the last confirmation page of the transfer.
- 02071 - TD/OMS Move Transfer Failing
- Fixed an issue where a move transfer was failing to select the correct sub-environments.
- I02759 - "Change" in Toolbar of Comments View not enable
- Resolved the issue as there was a bug that prevented the button from enabling as intended. The "Change" button will be enabled when a comment is selected.
- I02768 - Update dynamic 'Show/Hide' Label and add decorator in Components view menu
- The issue was fixed concerning the dynamic updating of the 'Show/Hide' label, i.e., whether in the components view the current state shown or hidden. Also adding a decorator in the view menu, adds visual enhancements that can indicate additional information of it to be selected.
- I02758 - TD/OMS Definitions - sub-environment filter
- Fixed an issue when the sub-environment sequence number range is used in a sub-environment filter and the results were wrong when a number bigger than 1000 is used.
- I02763 - Sorting of environments is wrong in the definitions
- Resolved an issue where the sorting of the environments was sometimes wrong.
- I02764 - Sorting of sub-environments is wrong in the definitions
- Resolved an issue where the sorting of the sub-environments was sometimes wrong.
- I02756 - TD/OMS definitions - copy application
- Fixed a bug when an application was copied, including security, and then the user was not authorized to change anything in the copied application.
- I02762 - Application deletion and recreation with the same name is not working
- When an application is deleted and an attempt is made to recreate it again with the same name there is an issue saying that the application already exists. This is fixed.
- I02765 - Adding invalid ratification group member returns no error message
- Fixed an issue when adding an invalid ratification group member an empty error was shown.
- I02773 - New entity definitions actions are in the wrong place
- Fixed a bug where new entity actions are not inside the "New" menu in the definitions.
- I02805 - Xref query will fail with generic failure message when Xref server preferences are not set
- A more specific message will be shown if the Xref server has not been set and a query is run
- I2162 - Add a button to the Xref simple dialog to switch to the Advanced Xref dialog
- Now it is possible to jump to the Advanced Xref dialog from the simple Xref dialog
- I02844 - Add compile result view support in VSCode
- The compile result view is functional in the OCTO, but it is not yet working in the VSCode extension. The compile result view should be supported by VSCode as well.
- I02853 - VSCode source editor shows included files' errors instead of only main compile errors
- When I click on the "Show Compile Errors" option in the build queue in Visual Studio Code, the editor opens and displays not only the main errors but also the errors from the included files.
- I02856 - In VSCode, error info can be added to the source editor but lacks an option for removal
- In VSCode, it's possible to add error info to the source editor. However, there is no available method to clear or remove this error info once it has been added.
- I02860 - Task takes too long to open in VSCode source editor
- When attempting to open a task from the VSCode work management, there is a significant delay before the task is fully rendered in the source editor.
- I02821 - OCTO Unneeded error messages
- When opening Octo, it presents a login screen when the token has expired. This is expected behavior. After logging in notifications show up from components (such as the build queue) that the login failed.
Please consider clearing error notifications that no longer reflect the current state. It probably makes sense to have an error view that can be opened for troubleshooting purposes, but otherwise let developers focus on the current state (logged in) unless there is a current error preventing some components from functioning.
- I02862 - Store JWT token in local storage without encryption
- At the moment, the JWT token is encrypted and saved in the browser's local storage. We need to modify this behavior by storing the JWT token in local storage without encryption.
- I02858 - Error displayed when clicking on a build queue item menu
- An error occurs when attempting to click on the menu item in the build queue.
- I02863 - Paging widget is not showing completely on the Solution tab of the task
- The paging widget at the bottom of the Solution tab in the task view does not appear fully. It is either partially hidden or cut off, making it difficult for users to navigate through the pages.
- I02868 - Tab title disappears when scrolling with plugin tile scrollbar in source editor
- In the source editor, there are two scrollbars: one for the Monaco editor and one for the plugin tile. The issue occurs when scrolling using the plugin tile scrollbar on the tab head, which results in the tab title disappearing or becoming hidden. This affects usability and visibility of the tab titles when interacting with the scrollbars.
- I02871 - Refreshing the Source Editor via the Menu Closes Newly Opened Editor
- When clicking the "Refresh" option in the source editor menu, the currently opened editor closes instead of refreshing its contents. This issue occurs only if the editor was newly opened.
- I02872 - Azure interface was failing in RDi 9.8 and wasn't showing the correct work-item icons in the RCP
- The creation of the Azure work-item type icon (for the workmanagement perspective) was not being created or was created incorrectly, this has been fixed.
- I02874 - Close All' Menu Closes Unsaved Files Without Prompting for Save Confirmation
- The 'Close All' menu option in the source editor currently closes all open files, including those with unsaved changes, without prompting the user to save their work. This can lead to accidental data loss as the editor does not ask for confirmation before discarding unsaved modifications.
- I02870 - Show errors in build queue
- The errors are not shown when the source is not open.The errors are not shown when the source is not open in GOTO LINE.The menu option must change in "Show errors in source"
- I02882 - null pointer exception on Bitbucket interface when incorrect credentials are provided or issues not setup from repository
- No errors were being logged in the TD/OMS log or displayed in the tree view, this has been fixed so that failures in the interface are now correctly displayed and or logged
- I02894 - Change Compile Result Component to Display Only Errors of Specific Severity Numbers
- Currently, the Compile Result component displays errors of all severity numbers. The component should be modified to display only the errors of specific severity numbers (sevNum >= 20 && sevNum<= 30).
- I02893 - "No Transfer Records Found" Error Alert on Hard Refresh
- When performing a hard refresh, an error alert displaying "No transfer records found" appears unexpectedly.
- I02901 - VSCode- Dock views in the bottom panel by default
- All views are now organized under the TD/OMS view container. By default, most views are docked in the bottom panel for improved usability and consistency.
- I02902 - VSCode- error message when token cannot be renewed
- Previously, token renewal failures resulted in generic error messages without context. This has been resolved with enhanced error reporting that provides clear, actionable information to the user.
Server issues/enhancements resolved
- I02840 - STRFOF - Processing method Emptying messsage logging issue
- Now, the STRFOF logs message in the OMS log while emptying.
- I02845 - Ratification is not moved to the history when promoting
- Now, the ratification is moved to history when promoting.
- I02693 - Unable to return the correct library
- Now, while creating the new object, the library and the source library fields are filled with the correct library name.
- I02809 - Retrieve Database issue related to the Date and Time field.
- When filtering records, if the file contains a Date and Time field, the Database API should return the corresponding records.
- I02891 - REST API - Incorrect message in BUILD Queue API.
- Now we are receiving the correct message.
- I02877 - REST API - Objects are not added in BUILD Queue.
- In certain scenarios, the Build Queue REST API is unable to add objects to the BUILD queue
- I02866 - Typo in message OMQF810
- The message contains a typo; it states *AUTHRIZE, but it should be *AUTHORIZE.
- I02818 - The version is not being updated by the upstream application.
- We changed the logic to ensure that the upstream application must update the version if it is zero.
- I02817 - Get Severity code from QMHRTVM API.
- We changed the retrieveMessageText procedure also to include the severity code.
- T00403 - Get procedure List of Program
- Fetching procedure list is made faster.
- I02417 - Conversion fails when PF member name is changed.
- In a scenario where 'From Environment PF' and 'To Environment PF' each have one member with different member names, The conversion will be successful.
- I02831 - Search with '_' does not work in Object Maintenance
- Searching with '_' works in Object Maintenance to find objects that contain that character.
- I02815 - Issue while creating new message id.
- Numbers (0-9) are allowed at the 4th position in the message id.
- I02156 - Disconnecting a solution should also clean up the compile history
- When a solution is disconnected or moved to another task, it will automatically delete any unnecessary build-history, ensuring no red error decorations remain in the fix.
- E249 - Add the completion date to the details view of OMQPRTFI
- We have added the object completion date to the details section of the Fix Report (OMQPRTFI).
- I02375 - Reject connect from development object
- A development object will not be connected to a task as a *CHANGE solution if the source information does not reference a valid development source library.
- 814 - EVEFEventFile API Parse event post method returns empty status instead of '*NORM'
- Now, It returns the status '*NORM' instead of blanks.
- I02811 - OMQCHGCR - Not Returning Error Message and Status
- Now, it returns the correct error message with the appropriate status.
- I02816 - OMQCHGCR - update the regex field length
- The field 'Primary object regex' has been updated from varchar to a char (510) field. It has no impact while using the OMQCHGCR command line API.
- I02822 - Fill Object File does not refresh object
- Source physical files are getting refreshed.
- I02825 - OMQCHGCR *COPY must also copy details
- Related detail information is included when copying a connection rule code.
- I02824 - OMQCHGCD - Update the regex field
- Fields have been updated from varchar to char(510). It has no impact while using the OMQCHGCD command line API.
- I02795 - Cursor C01 not open
- While transferring the object and processing the select action in the selection program, we should not recieve the message "Cursor C01 not open."
- I02804 - Application should not be deleted if transfers are open
- The application will not be deleted if there are open monitored remote transfers.
- I02781 - Job description issue
- When we transfer the object, the remote job description should retrieve the most specific default job description code.
- I02798 - BRSRCI field is missing in OMDDI file
- We recently added a new field, BRSRCI, to the OMBRV1 view. As a result, this field information should be included in the OMDDI file.
- I02627 - OMQCHGFI - A task that has already been completed can again be completed.
- If the task is already completed, it should exit to prevent triggering the task/complete and task/status events again.
- I02792 - Issue in Spool file Api
- Now we are getting the correct message data.
- I02799 - F13 in Fix maintenance and request maintenance
- Users can use the F13 key to copy a selected option to the end of the list in Fix Maintenance and Request Maintenance, just as in Solution Maintenance.
- I02842 - New Label Creation Issue.
- When we encounter this situation, we need to reset the label ID field, which is an identity column.
- I02793 - Comment API issue
- Comments can only be edited by the original user and within 24 hours of being posted.
- I02766 - OMQCHGRL issues
- When attempting to copy from a remote location, unexpected * characters appeared in some of the fields.
- I02786 - Add new command line APIs to the OMSAPI menu.
- The OMQCHGVC, OMQCHGPT, OMQCHGUV, OMQCHGAC, and OMQCHGCN APIs have been added to the OMSAPI menu.
- I02801 - STROCM - Authorization should not be allowed when the object doesn't exist.
- Authorization is now restricted when the object does not exist.
- I02541 - Increment value for *NEXT in environment maintenance
- The sub-environment sequence number increment has been set to 10 instead of 2 in the OMQCHGSE API and the sub-environment maintenance screen. Additionally, the special value *NEXT has been added to increment the sub-environment sequence number by 10. You can see Sub-environment API documentation for more information.
- I02796 - OMQCHGSL does not create the library when application is defined as SYNON
- For the synon applications, libraries are created now.
- 739 - Check out is not working properly
- When we try to check out the object from OCTO, the possible level check window appears. However, when we try to check out the same object from the green screen, it displays the message: "No target library list definitions were found for this transfer."
- I02772 - Comment API Issue
- When attempting to reply to a comment, the short description field does not appear. However, after pressing enter, a message indicates that a short description is required.
- I02778 - Issue in Spool file Api
- When we select the spool file component, the number of records for the given page number should be returned correctly.
- I02779 - Indicator variable required.
- When we run the REST API, the job log should not display the message "Indicator variable required."
- I02788 - Connection list api issue
- When we attempt to connect the member to the connection list, the member's name should be displayed.
- I02790 - Fix maintenance dump
- When we close the fix and press enter, the screen should not become unresponsive.
- I02794 - Transfer API issue
- When attempting to transfer the object, the appropriate job description for the remote address should be automatically selected.
- I02776 - OMQCHGCO - The special value *NOCHANGE is not appropriate.
- The special value *NOCHANGE has been changed to *HEADER in the compile override command-line API.
- I02771 - Logical Library like SYNON_TEST not added with in sub environment.
- 4GL Libraries can be added now.
- T00394 - Rest API for OMQCHGUV - Change User Defined Variable.
- Rest API created for Change User Defined Variable.
- T00397 - Screen to add whole License at once in INSLICOMS.
- The user was previously able to add only one module license at a time. Now, it has been changed to allow adding the entire license at once.
- I02789 - Multi select shows wrong description.
- The library list description was not displayed correctly when multiple sub-environments for distribution lists were selected. This has been fixed.
- I02696 - Application relationships help correction in 5250
- The help link for application relationships was incorrect. This has been fixed.
- I02760 - Message DFN0003 in TD/OMS log on remote
- Message DFN0003 was initially generated for action, label and job description creation. Now, different messages are used for each purpose, respectively.
- I02656 - Maintain library does not close
- The object screen was not closing when all records were filled. This is corrected.
- I02806 - New Pre transfer checks are missing
- Any Pre transfer check that does not have any authority, will be granted C2 Authority.
OpenAPI Generator Enhancements
Please re-install the generator with INZOMSSRV SERVICE(*APIRESTGEN)
- WARNING
A service program has received an official signature. If you upgrade to V15 Milestone 1, then you need to rebind your existing generated APIs with: UPDPGM PGM(your/program) MODULE(*NONE) BNDSRVPGM((OMNSRV))
- I02775 - The default value is not set correctly for modules generated by the REST API.
- When we define a schema as a string type with a default value in Swagger, the default value should be correctly applied in the modules generated by the REST API if we don't pass a value for that field.
- I02785 - Rest API Generator issue
- Prevent duplicate field declarations during the generation of the REST API.
- I02800 - REST API - The local variable declarations are missing in the M member
- The local variable declarations are missing in the generated REST API's M member.
- I02797 - Duplicate Objects Generated with Client-Server
- When generating objects with the client-server setup, duplicate objects should not be created if the same objects already exist.
- I02807 - REST API - Client generation issue.
- When a nested schema is encountered, the generator API should generate the appropriate logic to parse the value correctly.
- I02819 - REST API - Binding directory description is empty
- The binding directory description text shouldn't be empty while generating the REST API.
- I02820 - REST API - Client generation issue.
- The definition of the pointer field was missing while generating the client API.
- I02823 - REST API generator fails to produce source numbers in the correct sequence.
- The REST API generator should produce source numbers in the correct sequence