OCTO:New and Noteworthy/V1.2.3

New and Noteworthy in OCTO V1.2.3 (Milestone 3: May 15, 2024)

605 - Solution and object decoration	Solutions can have issues. These are shown using decorations. Version conflicts Failed to compile Objects have labels The object has a compile override Object has comments

Create new objects	Octo now enables the creation of new objects in VSCode and the Web.

Enhancements to Source File Editor

Enhanced Alert Mechanism: In case the source file cannot be saved for any reason, an alert warning will immediately pop up to notify you. Additionally, the editor will intelligently switch the source file to a read-only state, ensuring that you can still access and review the content without risking any unintended alterations. Introducing a Background Source File Monitoring System: Now, when you attempt to save a source file that has been modified in the background, a dialog box will promptly appear. This dialog provides you with the option to either forcefully save the changes or to cancel the save operation altogether.

Enhancing Task URL Navigation for User Flexibility	Currently, when a task URL is clicked, users are directed to the Solution tab within the item editor by default. While this provides a quick access point, it limits user control and flexibility. Recognizing the importance of empowering users, we propose a solution to allow customization of the default tab selection through URL parameters.

Open an Octo Workspace in VS Code	You can now open a workspace in VS Code. This is one of more coming steps aiming to make the interaction with an Octo workspace between the web client and VS Code simple, stateful and seamless.

Open a plugin in New Tab	Each linked plugin can now be opened in own browser tab.

Improved Source Editor with Enhanced Syntax Highlighting	The source editor now boasts an upgraded feature set, including advanced source code syntax highlighting. Notably, it can seamlessly showcase the syntax of the most prevalent source code extensions, enhancing readability and usability for users.

Enhanced Source Editor with Production Comparison Feature	The source editor has been upgraded with a powerful source comparison feature. Users can now easily compare their code with the production version from an Object file, facilitating efficient editing and seamless saving of changes.

Other issues/enhancements resolved

643 - Signout form has html error

An HTML issue caused a UI glitch in the signout form. This has been fixed.

202 - Change task date does not work on task API

The following error is thrown: Value 1221129 is invalid for expectedCompletionDate.","messageID":"OMQ600A"

556 - Initial load reads the tasks more than once

Initial load reads the tasks more than once

557 - Octo client - Enable users to clear cache from menu

Octo users need sometimes to clear the browser local storage/cache for different reasons. Make it easy to do so from a menu instead of having to go through browser dev-views.

558 - Octo client - Refactor connection list conflict wizard to use the ConfigManager

The connection list conflict resolution wizard page should use the central TD/OMS Configuration Manager.

559 - Octo client - TD/OMS configuration dropdown

Recheck the TD/OMS configuration switching and caching.

561 - Octo client - Make ready the TD/OMS code for M3

Make a copy of TD/OMS code base and set needed parameters to be used for milestone 3.

562 - Work-Management Task Fetch Returns Empty Result After Refreshing Page with "Current" Filter Applied for Programmers

Upon refreshing the Work-Management page while filtering tasks by the "Current" filter and being designated as a programmer, an unexpected issue arises. Post-refresh, the task fetch operation fails to retrieve any tasks, presenting an empty task list. This critical setback disrupts the smooth flow of work management, particularly for programmers who heavily rely on this tool for task organization and prioritization.

563 - Inconsistency in Spool File Opening

Source Editor Visibility Issue

Currently, there exists a discrepancy in the behavior of opening spool files in the source editor. While the spool file can indeed be opened in the source editor, if the source editor window is hidden, the spool file opens in a hidden manner as well. Implement a solution that ensures the source file editor is brought to the forefront upon opening a spool file, regardless of its previous visibility status.

564 - Transfer wizard issues

The overview page is not shown when we have conflicts to confirm; The overview page is not grouped by library list

565 - Optimization of Transfer Wizards Utilizing Recent Octo Wizard Enhancements

Recently, numerous optimizations have been introduced to the Octo wizard, enhancing its efficiency and performance. However, the prototype wizards within our reference system have not yet been implemented with these functionalities. This issue tracks these changes. The goal is to prove that the new base classes are fit.

566 - Pagination Functionality Failure in Connection List Component

The pagination feature has been incorporated into the connection list component to enhance user experience by efficiently managing large datasets. However, an issue has been identified where the pagination functionality does not work as expected. Specifically, clicking on a page initially functions correctly, but subsequent attempts to navigate between pages result in the failure to reload data.

568 - Octo VSCode - Read plugins automatically

Let Octo VS Code read automatically all the plugins available in the Octo market.

569 - Spoolfile view refresh does not work in VSCode

The spool file refresh does not work in VSCode. See attachment,

572 - VSCode picks up and old spoolfile

When I double-click on the spooled file in the spool file view, sometimes an older version of the same spool file is shown. It looks like VSCode cashes a spool file with the same name and shows that. Open in the browser on the spooled file does show the correct data.

573 - Add to build queue does not work in VSCode

When the source is saved, or the add to build queue options are selected. Nothing happens in VSCode.

575 - Inconsistent Error Message Display in Form Octo Wizard

In the Form Octo Wizard, there appears to be an inconsistency in the display of error messages when attempting to change the message type from "error" to "info". Despite the attempt to modify the message type, the wizard consistently displays error messages instead of the intended information messages.

576 - Decoding Issue with Copyright Symbol (©) on Server Side

When attempting to save a source file containing the copyright symbol (©), the encoded string is sent to the server. However, upon receiving the encoded string, the server encounters a decoding failure.

578 - Octo - Let entities provide their own URL query parameters

An Octo entity may provide the URL query parameters necessary to build its state when loaded from a link within a UI component. As a result, each Octo entity may be linkable.

577 - Octo VSCode - Automate event topics registration

Automatically detect a plugin registered event topics and register them in the VS Code WebView view.

584 - Task Form Application Sorting Issue

The task form within our application is currently experiencing an issue where applications are not displayed in a sorted manner. This lack of sorting impacts the user experience and makes it challenging for users to efficiently navigate through the applications. To enhance usability and organization, it's crucial that applications are displayed in a sorted order within the task form.

585 - After switching configurations these error messages appear

After switching configurations, error messages appear: Unauthorized or expired token, please log in again (on build queue and spool file component).

587 - Error in OCTO Startup

Missing Required Field 'appCode' in Components Plugin

Upon initiating OCTO, an error is encountered originating from the Components Plugin. The error message specifies that a crucial field, 'appCode', is missing.

588 - Work Management Filter Issues

In the work management filter feature, we have identified two significant issues that are impacting user experience: Selected application disappears after a hard refresh; Filter retains data of current config after switching to another config.

590 - Octo VSCode - Upon reload, close erroneous editors

If an Octo editor is open and you reload or restart your VS Code, that editor will show up with an error that the file cannot be found.

591 - Octo VSCode - Reload all plugins upon sign in/out

In VS Code, Octo plugins are not reloading as a reaction on a sign in/out events

592 - Enhancing Source API

Revise Client Model and Implement Updates by Octo

The Source API requires revision to meet evolving user needs and optimize performance. This issue aims to initiate the process of enhancing the Source API by revising the client model and implementing necessary updates by Octo.

593 - Task Selection Memento Feature Fails to Persist in Workmanagement Plugin

The Workmanagement plugin functionality, the "Memento of Task Selection," is currently experiencing a persistent failure to retain the selected task.

598 - Loading a Task from URL Prompts Login Despite Existing Local Storage Login Data

When attempting to load a task from a URL within the item editor, the system prompts the user to log in even though login data from local storage already exists.

599 - Customizing Default Tab Selection in Task URL

Currently, when a task URL is clicked, the item editor displays data within tabs such as Solution, Details, and Ratification. However, the Solution tab is automatically selected by default. To offer users more control and flexibility, we aim to implement a solution where the default tab selection can be customized through URL parameters. This enhancement empowers users to define which tab will be automatically selected upon clicking the URL, enhancing user experience and efficiency.

600 - Octo VSCode - Plugins views not showing all plugins

Upon reload in VS Code, the plugins view can't initialize the plugins anew as they're already registered

601 - Octo VSCode - TD/OMS plugins should all react on the sign in/out events

In Octo VS Code, - the TD/OMS plugins should all react on the sign in/out actions either showing the sign-in form or plugin content.

602 - Incorporating Last Change Date in Source File API for Client-Side Updates

With the recent addition of the last change date to our source file API, it's essential to update our client-side functionality to leverage this information effectively. This enhancement aims to regenerate the API to accommodate this new feature, enabling clients to retrieve changes efficiently and reuse the last changed date for updating the source after saving alterations.

607 - Octo client - Welcome page editor in admin mode malfunctioning

An octo admin/owner should be able to view the welcome page editor when selecting the Welcome link from the avatar sub-menu.

608 - Octo client - The components plugin not retaining its content from memento

The components plugin is not loading its content from a memento state.

610 - Update Database Entities with Enhanced Versions Featuring Key Fields Retrieval

Currently, our system utilizes database entities that lack a method for efficiently retrieving key fields. To enhance functionality and optimize operations, we propose replacing the existing entities with newly enhanced versions. These enhanced entities will incorporate a method capable of retrieving the key fields associated with each entity.

611 - Octo client - Replace colors in HTML files with the template ones

When common colors styles are defined in the core templates, plugins' HTML files should use them instead of re-defining their own within the file.

612 - Octo & WebContainers API Integration

614 - Old database entity "CreateObjectMonitorExtended" refactored to "CreateMonitorExtended" in the new database

The legacy database contains an entity named "CreateObjectMonitorExtended," while in the new database, this entity has been refactored to "CreateMonitorExtended." This situation poses a compatibility issue during data mapping.

615 - Promote and Checkout Functionality Fails

Transfer Process Halts at Selection Stage

Users attempting to promote items and proceed to checkout encounter a critical issue where the transfer process stalls indefinitely at the selection stage. This impasse prevents users from completing their intended actions, disrupting workflow and potentially causing delays in important tasks.

617 - When Closing One Item Without Selection in the Editor, the Following Item Displays Empty Content

When two items are open in the item editor, and the user selects the second item and then closes the first one without actively selecting it, the editor fails to display the content of the second item correctly. Instead, the content area appears empty, leading to confusion and potential data loss.

618 - Octo VSCode - A wizard should close upon Finish button click

An Octo wizard plugin should be dismissed upon finish click when opened in VS Code UI.

619 - Octo VSCode - Octo plugins loaded at the bottom section keeps loading

If the Octo plugins view is collapsed, then the plugins opened at the bottom VS Code section keep loading.

620 - Octo Client - Regroup the local context menus

Regroup the context menu (the ones trigger by the dots) to make it shorter and easier to navigate.

621 - Update Component Imports to Utilize TdomsApiNamespace Instead of Hard-Coded Version Plugin

We've identified a critical issue where certain components within our system are importing classes using hard-coded version plugins. To resolve this issue comprehensively, we need to replace all these imports with the class TdomsApiNamespace.

622 - The view header should not scroll out of focus

Bottom+Right ViewStack

When we scroll in the bottom viewstack then the header scrolls out of focus. We can then also not resize anymore.

624 - VSCode

Source save fails with special characters

The source fails to save correctly in VSCode. I have added a special © character in the source. This works on the web.

625 - Unsaved Changes Prompt Not Dismissible

When a source file is open and has unsaved changes in the source editor, closing the editor window prompts a save dialog, as expected. However, upon clicking the "Cancel" button in the save dialog, the dialog remains open, which is inconsistent with standard behavior and creates a usability issue.

627 - Octo Client - Sections toggler issues

Some sections toggler issues still persist: See issue for more details.

628 - Octo Client - The tile toolbar in the middle section

Some sections toggler issues still persist: See issue for more details.

630 - Octo VSCode - Add 'Open in VS Code" menu option

Given an Octo URL, make it possible to open VS Code from the web client then activate the Octo plugins. (If both already installed, of course).

631 - Octo client - Add 'Get link" to plugins' main toolbar

Add a toolbar menu entry to all plugins that implement the Linkable interface.

642 - Source Editor Crashes Parsing DDS Files

When attempting to parse DDS files within the source editor, users are encountering frequent crashes. Upon parsing DDS files, the editor becomes unresponsive and ultimately crashes, resulting in potential loss of unsaved work and frustration.