Qbilon Software Changelog

• You can now add a new task or node via the dropdown menu in the "Topology View" graph. You can now quickly link new nodes by selecting a predecessor from the dropdown menu, which is faster than drag-and-drop.
• The "Topology View" now has an "Edit Toolbar" and a "Creation Popup." These tools support the visual creation and editing of tasks with an overlay toolbar and pop-up wizard.

• Users can now upgrade custom task templates.
• All configuration parameters are fully editable or removable during upgrades. New configuration parameters can also be added.
• The template name and icon remain fixed for consistency.
• Docker images linked to templates are now editable.

• A public GET endpoint has been implemented to retrieve full metamodel data. It returns type and relation information, as well as metadata such as data types, source contributions, instance counts, and system properties.

• A relation filter parameter has been introduced alongside the existing type filter in custom task templates.
• Users can now easily filter data using the Data API by relations, eliminating the need for manual input.
• Support for constraints within relation filters was added, offering more precise configuration options.

• A version selector has been introduced for custom task templates, allowing users to choose which version’s details to view.
• The corresponding template details are automatically loaded and displayed based on the selected version.
• This improves clarity and control when working with multi-version templates.

• Read endpoint permissions have been updated to grant the "user" role access to backend data.
• Previous access restrictions have been removed, enabling users to retrieve data seamlessly.

• Filtering options have been introduced to the Views Marketplace to enable faster discovery of relevant views.
• Users can now easily narrow results by "view types," "element types," "tags," and "recently added" to suit their needs.

• Comprehensive logging has been added to the PRTG Sensor Creator, Device Creator, and Deleter to provide clear feedback on success, warnings, and errors directly within the application.
• We resolved inconsistencies where certain PRTG operations (like group creation and deletion) lacked success or error logs. Now, users will receive accurate status updates.

• Missing account information for AWS EC2 instances has been fixed due to changes in the AWS API.

• Corrected the behavior where the Views page did not refresh after importing the first view.
• The page now automatically updates to display the newly imported view immediately.

• Resolved an issue where non-URL text properties were incorrectly underlined and treated as clickable links.
• Updated the URL detection logic so that only valid URLs are underlined and clickable in graph and table views.

• Addressed a bug where deactivated scheduled tasks were still executing according to their schedules.
• Tasks marked as deactivated no longer run, maintaining the expected workflow behavior.

• Resolved an issue where writer tasks (e.g., PRTG deleter) incorrectly displayed a "ready" state despite invalid credentials.
• Implemented proper error handling to display an "unauthorized" state when credentials are incorrect.
• Improved task status accuracy to prevent misleading completion indicators.

• Resolved an issue where newly created element properties (e.g., names) were not appearing in the suggestions list.
• All created properties are now instantly available for selection when adding new elements.

• The demo role was deprecated and removed to simplify the permission structure and improve system stability.

• Introduced API key generation in settings to securely access webhook endpoints.
• Added the ability to trigger any workflow via webhook through the API.
• Enables seamless external system integrations and automation through API-based workflow execution.

• Expanded the "PRTG Sensor Creator" to support multi-selection, enabling the creation of multiple sensor types per device at once.
• Improves setup speed and flexibility for monitoring.

• Implemented dynamic label coloring based on node background color to enhance readability.
• Eliminates visibility issues with dark colored nodes using automatic contrast adjustments.

• Introduced a "views marketplace" on the views page featuring professionally crafted graph, table, and chart views.
• Enables one-click addition of predefined views, reducing the need for manual creation.
• Views include metadata like descriptions, tags, and required element type chips.

• Added a new “Versions” column to display the number of template versions available per custom task.
• Improves transparency and control for users managing evolving task definitions.

• Corrected the problem where filtering views by instances on the home page had no effect.
• Now correctly displays only views that contain the selected instance.

• Fixed an issue where trailing spaces in column names triggered false “column not found” warnings.
• Column names in the ServiceNow Writer configuration are now trimmed automatically.

• Resolved inconsistency where the same relation constraint behaved differently in graph view versus ServiceNow Writer outputs.
• Now ensures unified and predictable constraint handling across the tool.

• Resolved an issue preventing users from rearranging columns in table views.
• Drag functionality now correctly updates column order as expected.

• Fixed discrepancies in "Date" fields "Last Ok/Down/Value/Up" imported from PRTG.
• Ensured imported timestamps accurately reflect the original times in PRTG.

• Resolved an error occurring when renaming and moving a task between workflows simultaneously.
• Tasks can now be renamed and moved across workflows without issues.

• Introduced creation of sensors in PRTG through Qbilon and its support for defining a target group for sensor placement.
• Introduced a counterpart to the creator, a PRTG Element Deleter, which allows automatic removal of PRTG device and sensor instances based on constraints.

• Introduced a dedicated PRTG Group Creator task type in Qbilon for creating groups directly in PRTG.
• Enables structured and automated group creation in PRTG environments.

• Enhanced both AWS and Azure connectors to include additional properties required for accurate PRTG device creation.
• AWS EC2 Enhancements:
  • Added ec2 region: Name of the region associated with the EC2 instance
  • Added ec2 availability zone: Name of the availability zone for the EC2 instance
• Azure VM Enhancements:
  • Added resource group name: Name of the Azure Resource Group the VM belongs to
  • Added region name: Azure region where the VM is hosted

• Introduced support for creating devices using standard device templates combined with "Auto-Discovery".
• "Auto-Discovery" now automatically executes post device creation when a template is provided.
• Template-aware discovery ensures tailored sensor setup, defaults apply if no template is specified.

• Updated “Open Context View” button to toggle to “Clear Context View” when the same element is selected again.
• Fixed “Set Focus” button to correctly display “Set Focus” when selecting elements without focus, and “Clear Focus” only for the focused element.
• Enhanced clarity and usability of graph view.

• Addressed issues with oversized relation names in Azure graph views causing inconsistent display across layout, ensured relation names fit neatly.

• Resolved issues causing the import view feature to throw an error.
• Restored successful import of multiple files simultaneously.

• Fixed an error occurring during creation of color rules involving relation constraints.
• Color rules with relation constraints now save and apply without issues.

• Corrected icon list ordering to follow alphabetical sequence in graph view creation.

• Enabled filtering by specific relations connected to elements in table and chart views.
• Previously, only relation directions were available as filter options.

• A new task type has been introduced, allowing admins to define reusable task templates powered by Docker images.
• Users can now integrate their own custom tasks into workflows by specifying the required inputs and container images.
• A new section has been added to the settings screen to enable the easy creation and management of custom tasks, which can be launched just like any other task in the system.

• The new Task Orchestrator has been launched. All data collectors are now available as Docker images, enabling consistent and scalable task execution.
• Addressed containerisation-related issues, including performance bottlenecks and incomplete behaviour in specific connectors.

• Enables users to filter and customize views based on the specific properties of the relations between assets and elements.
• Supports filtering in graph and table views using relation-based constraints.
• Allows filtering with relation-based constraints when writing data in ServiceNow via the ServiceNow Writer.
• Enhances flexibility by enabling complex filters throughout the platform.

• New API endpoints have been created for linking and merging operations, making them usable for custom tasks.
• Designed to handle entity linking and data merging workflows more efficiently and independently.
• Enables more targeted integration with external systems or automation tools that require fine-grained control over the linking and merging logic.

• We fixed a bug in the Read API relation conditions where certain operators did not behave as expected.
• Condition parsing has been improved to ensure accurate filtering and reliable query results.

• An issue was resolved where elements with valid ServiceNow System IDs were not created if their counterparts did not exist in ServiceNow.
• It now ensures that such elements are created properly and that the incoming system IDs are applied as expected.

• Addressed a UI bug that caused the existing placeholder or input text to overlap with the search bar when typing.
• Text input behavior has been improved for a clearer, more user-friendly search experience.

• Corrected a discrepancy where the "received elements and relations" summary did not align with detailed log output.
• Now ensures consistent and accurate reporting across both UI and logs for better traceability.

• Updated task status language for clearer communication of workflow states.
• Replaced “Activated” chip with “Ready” for improved task readiness clarity.
• Introduced “No running task at the moment” message to indicate idle workflows.

• Introduced the ability to assign custom names to color rules, improving clarity.
• Simplifies understanding for non-technical users by replacing raw conditions with user-friendly labels.

• Updated relation condition logic to support optional relationFullName and direction fields.
• Added validation to ensure at least one—direction or relation name—is present for condition integrity.
• Enhanced usability by allowing simplified detection of isolated nodes without specifying all relation types.

• Enabled line break recognition in view descriptions for better content structuring.
• Added keyboard shortcuts (Ctrl+Enter / Cmd+Enter) to navigate steps without triggering premature save, ensured neatly formatted display of descriptions.

• Added support for prefixing and suffixing column values written via ServiceNow Writer.
• Configurable via new “Prefix/Postfix Column Value” section in column edit settings and only available for "Property", "Neighbor Property", "Source Property", and "Target Property" write types.

• Relocated “Open Context View” button from global to selection toolbar for intuitive interaction.
• Now appears only when at least one node is selected, enhancing user flow and reducing confusion.

• Resolved inconsistency between Relation Folding button state and actual graph behavior.
• Now, active button state correctly indicates folded relations, and inactive state means unfolded.

• Fixed issue where search results displayed incorrect views when searching for specific entries, improved search functionality to ensure results are now filtered precisely based on the entered keyword.

• Rectified the problem where expand/collapse buttons were not reflecting the correct state of node expansions in the graph view and expanded nodes that prevented users from returning to previous states or collapsing them again.
• Corrected element selection from the search bar, ensuring proper selection even when nodes are within container relationships.

• Handled issues which were causing 500 server errors when querying with valid yet unformatted values, ensuring queries like -PT1H return results instead of exceptions.
• Fixed inconsistent behavior with equality checks, ensuring consistent results when comparing values like 123 and 123.0 or numeric list values.
• Corrected handling of special characters in regex queries (e.g., \w), allowing proper regex evaluation and returning expected results with patterns like D+, Drie, and D|Z.
• Addressed date time query inconsistencies, ensuring correct handling of durations like -P2D and -PT1H, as well as fixed handling of non-zero hours in date calculations.
• Improved query error messages to correctly handle format violations, missing operators, and missing list operators.

• Fixed the bug where toggling the "Relation folding" button caused replication of relation labels when no foldable relations were present in the graph view.
• Ensured that the "Relation folding" toggle does not affect the graph view when no foldable relations are available.

• The tasks are now available as a container image.
• Data source tasks and consolidation tasks can now run as a separate container in Docker or Kubernetes.
• Removed the coupling between tasks and Qbilon to better manage resource requirements and better integrate custom container images into a Qbilon workflow.

• Added timestamps to all task logs for better tracking and organization.
• This improves the traceability of errors, warnings, and informational messages, allowing for better monitoring and problem resolution.

• Added filtering capabilities to the READ API endpoint, enabling complex query capabilities such as relational filtering.
• Extended the READ endpoint to accept POST requests to provide a filter object.
• Requires a valid license and ADMIN or ARCHITECT user roles to ensure secure data queries.

• Standardized all execution time displays to DD/MM/YYYY format for consistency.
• Updated formats in the Topology Mode, View, Edit, Settings, and Support sections.

• Changed PRTG Tags property datatype from Text to a List<Text>, allowing more efficient filtering and data handling, also changed Object ID datatype for Devices from TEXT to NUMBER, aligning it with Probes, Groups, and Sensors.

• Fixed issue with details being displayed without a selected node after returning to the topology view, ensured UI consistency details are now only displayed when a node is actively selected.

• Fixed a problem where color rules were not applied according to their top-to-bottom priority order, ensuring that top-priority rules are now correctly enforced

• Restored the expected behavior of automatically opening the right sidebar when clicking on an item in the graph; fix improves efficiency by reducing unnecessary clicks.

• Updated API behavior to allow adding relations between existing types/elements without having to list them in the JSON body.
• Removes unintuitive restrictions and aligns with expected usage logic.

• Fixed issue with ignoring changes to the target view in the Context View dialog, it now correctly opens the selected graph view (e.g. switching from View A to View B).

• Fixed issue where the "Exists" operator did not work properly with a "false" value in ServiceNow Writer.
• Fixed data writing inconsistencies when using the Exists operator.

• Fixed a problem where large relation names were truncated in the graph view, ensuring that text stays within the box and wraps to the next line instead of being truncated.

• Added search functionality to the Views field when creating context views, making navigation easier and allowing users to quickly filter options by typing initials, reducing the need to scroll through long lists.

• The previous "hide isolated elements" checkbox in graph view has been replaced with a dropdown menu, allowing users to:
  • Show only isolated elements
  • Show only non-isolated elements
  • Show all elements
• This enhancement supports better asset tracking by providing a clearer view of system dependencies.

• A new search bar at the top allows users to find the specific element and relation types effortlessly during defining a graph view, no more scrolling through the large metamodel—simply type to locate and add the needed element types.

• We’ve improved error handling by adding self-explanatory log messages for common issues. Now, if credentials are incorrect, the URL is invalid, or the target table name is wrong, users will see precise error logs, making debugging faster and easier

• Element types in the metamodel now clearly indicate whether they contain data.
• To reduce confusion and improve readability:
  • The number of instances is now shown next to the type name.
  • Empty types appear in a lighter shade, while types with data remain in the standard color.
  • A small icon highlights types with no instances, making it easier to track changes

• Implemented a search field on the Views page for easier navigation, it increases usability by providing a quick and efficient way to find the specific view.

• Resolved an issue where ServiceNow writer would throw an error when the "Name" property was missing, it will now safely handle missing "Name" properties, ensuring data is processed without disruption.

• Fixed the backend issue during creation of certain standard views in PRTG, ensured that standard views can now be created without errors.

• Addressed the issue where the counter for selected elements didn't update when unselecting elements using Shift-Click and corrected toolbar display to show "element/relation" when both nodes and edges are selected.

• Resolved the issue where changing or editing the "Scheduled" execution type settings caused the execution to stop working.

• Ensured consistent logging for the JSON push connector, providing better traceability and error handling.

• Corrected the error where pushing data for new elements with "null" provided as data type caused an exception, system now handles it gracefully without causing crashes.

• Rectified the problem of display of the "Deactivate Task" button, ensuring it changes to grey, like other inactive buttons, when not functional.

• Introduced a collapsible/expandable sidebar in the Topology view to display task data and logs.
• Sidebar details update in real time based on workflow changes and actions.
• Sidebar has three structured sections:
  • Data source Details – View relevant data source information.
  • Warnings & Errors– Monitor logs and system warnings.
  • Execution details – View task execution settings.

• With Qbilon SaaS a container image can be run in Kubernetes
• The image can be self-provided or a predefined Qbilon image
• The K8s task type can be integrated into the workflows
• Enables the customer to write own software and execute it within the Qbilon workflow

• Implemented real-time validation to prevent duplicate names across the tool.
• Users now receive an error message ("Name already exists") when attempting to create duplicate relations, element types, or other named entities, prevents conflicts in the metamodel.

• Replaced the context menu with a global top toolbar, eliminating the need for right-clicking to manage elements.
• Global actions now have dedicated icons in the top toolbar with explanatory tooltips on hover for better usability.
• introduced a bottom toolbar for batch functionalities, deleting and hiding multiple elements at once with a simple click.
• Enables bulk deletion and downloading of multiple views efficiently.

• Added an information box to clarify the implications of changing the execution type of workflow tasks.
• Ensures users understand the impact of editing execution settings of tasks, depends on the action it can create a new workflows or merge existing ones.

• Added a new button to enable direct task creation from the Workflow overview page.
• Users can now create tasks without navigating into a specific workflow.

• Users can now modify a task's dependency trigger to reassign it to a different workflow.
• Supports splitting and merging workflows by allowing tasks to switch between Onetime, Scheduled, or Dependency triggers.
• Enhances workflow flexibility, enabling more efficient workflow restructuring.

• Resolved an issue where filtered elements in the orthogonal layout appeared differently than in hierarchic and organic layouts.
• Filtered elements are now consistently displayed across all three graph layouts for a uniform experience.

• Fixed a problem where color rules were not consistently applied to expanded and folded relations.
• Expanding the container now correctly applies the designated color rules to all expanded relations.

• The global app bar now correctly displays "Add View" when creating a view and "Edit View" when modifying one, improved consistency in the UI.

• Rectified the issue where merging data failed due to empty lists in one of the merging element instance.
• Empty list values are now correctly merged into an empty list, ensuring smooth merging functionality.

• Resolved a bug preventing the addition of elements or relations via the context menu while editing views.
• Users can now seamlessly add elements and relations as expected by simply right click.

• Corrected an error where the "warning" filter in the topology sidebar incorrectly generated logs on every click.
• Logs are now properly filtered per node, ensuring expected behavior

• Introduced a new POST /data/delete/{datasourceId} endpoint for deleting nodes, edges, and properties.
• Secured access with Basic Authentication to ensure controlled data removal.
• Improved API consistency by renaming the upsert endpoint to POST /data/upsert/{datasourceId}.
• This enhancement finalizes full CRUD support, allowing seamless data management in the Qbilon database.

• Enhanced Workflow Topology by allowing users to expand individual nodes to view task details.
• Real-time data updates ensure node information stays synchronized with the tasks tab.
• Smart graph adjustments prevent overlap, maintaining a clear and structured layout.
• This update moves the Topology view closer to a fully informative experience, helping users better plan and manage their workflows.

• Added “Address Space” property to Azure Networks, displaying CIDR block information.
• Established VM-to-Network relationship, clearly mapping which VM belongs to which network.
• Included “Availability Zone” property for RDS Instances, enhancing visibility in Qbilon

• Split API documentation into public and internal sections for better clarity.
• Public API docs now focus on data endpoints, ensuring external users access only relevant information.
• Added an introductory section explaining the purpose and scope of the public API.

• Introduced qbilonId for nodes and edges—globally unique within Qbilon, ensuring deterministic results.
• Added externalId for third-party system IDs, maintaining uniqueness within their respective sources.
• Refactored edges by replacing sourceId and targetId with sourceQbilonId/externalQbilonId and targetQbilonId/targetExternalId for clarity.
• Removed redundant fields (sourceType, targetType), as they are now inferred from relation names.

• Unified relation format by making relation names mandatory in the form <relation name> [<sourceType> ➝ <targetType>].
• Removed sourceType and targetType from mandatory fields, ensuring a more concise and consistent structure.
• Prevented duplicate relation keys in JSON, allowing multiple relations with the same name but different source/target types.
• Standardized relation format ensures data retrieved via GET /data/{datasourceId} can be directly reused in POST /data/{datasourceId} without modifications.

• 409 Conflict replaced with 422 Unprocessable Entity for mismatched update strategies.
• Meaningful error messages now clarify incompatible update strategies and suggest appropriate replacements.
• Invalid data types return structured error responses, preventing unexpected 500 errors.

• Redesigned the Keycloak login page to match Qbilon’s aesthetics.
• Enhanced brand consistency, ensuring the login page aligns with the rest of the platform.

• Optimized layout to consider relation labels, reducing overlaps and occlusions.
• Enhanced readability by ensuring labels remain clearly associated with their respective relations.

• Enabled text selection & copying for properties, node names, and edge names in the graph sidebar.
• Improved UX by allowing users to quickly extract key information without manual retyping.

• Resolved text overlap issue by adjusting line breaks and repositioning sublabels.
• Improved readability to ensure clear differentiation between element names and type labels.

• Restricted drag-and-drop functionality to only allow moving columns, not conditions.
• Ensured conditions remain linked to their assigned columns, preventing unintended reassignments.

• Prevented form breakage when deleting a selected type during table view creation.
• Implemented auto-reset to an empty state instead of causing errors.

• Ensured newly created attributes in the metamodel appear automatically in the property list in the linker configuration.
• Implemented real-time updates when defining conditions in custom linker configuration.

• Resolved parsing issue to correctly handle and write “number” data type into ServiceNow tables.
• Ensured compatibility with SNOW’s data processing, preventing unexpected errors.

• Resolved inconsistency where number-based rules were reset while text-based rules remained.
• Ensured color rules for number properties persist while editing the chart view.

• Ensured “Toggle Relation Label” remains functional even after activating and configuring a Context View.

• Disabled the delete button when only one constraint remains, preventing deletion.
• Added an explanatory tooltip to inform users that last constraint cannot be removed.

• Introduced a new “Create and Save” button next to the existing Save button when creating new color rules or filters.
• Ensures users can save and finalize new color rules and filters seamlessly, preventing accidental loss of unsaved changes.

• System properties (e.g., Qbilon ID, First Seen, Last Seen, Data Sources) are now displayed in a separate section within the metamodel for better clarity.
• Aligns the display with the graph/table view sidebar, reducing confusion and ensuring consistent property organization across the interface.

• Added a new “Scheduled at” column to the information table on the task details page.
• Displays the scheduled time or frequency for each task, following the format like “Every hour at 2nd minute”.

• Restructured the tab bar into three sections:
  • Data Sources: Displays all data sources that can be added in Qbilon.
  • Data Consolidation: Contains mergers and linkers for consolidating data.
  • Data Writer: Includes ServiceNow Writer and Webhook options.
•   Updated layout ensures better categorization and improved navigation.

• Replaced the existing data source icons with new, improved icons for a modern and consistent look.

• Renamed the “Settings” menu item to “Settings & Support”.
• Moved the “Support” section to the top of the page.
• Updated and optimized support links:
  • “Create Ticket” button now redirects to the new HubSpot-based support form.
  • Added a “Tutorials @ YouTube” button for quick access to video guides.
  • Removed the “Go to Ticket Board” button.
  • Retained the “Send Mail” button with the existing functionality.
• Added info boxes and support hints on the second step of the task creation dialog to guide users to relevant documentation (Qbilon manual).
• Ensures users are aware of available support resources, improving self-service support.

Rectified the problem where user as “user” role could hide elements within the graph, ensured proper user role restrictions to maintain graph integrity.

Resolved issue where the “Default view” was not loaded when the table view was opened from the “view-overview” page.

Fixed the bug where “Create and save new workflow” button appeared during task creation, corrected “create and save task” button to appear during task creation and “create and save new workflow” button to appear when creating a new workflow.

Addressed inconsistency in button text and title when creating or updating color rules/filters, button now correctly shows “Create” for first-time rule creation and “Update” for subsequent edits.

Corrected the display of the data source name in the “Next Execution” field for tasks with dependency execution type.

Rectified issue where the same description was shown for every task on the “Task Information” page, task information now dynamically updates based on whether the first task is being created in workflow or subsequent.

Fixed the issue where Docker tasks entered an error state when log entries exceeded 4095 characters, Implemented log entry length capping to ensure no errors occur when logs exceed the limit.

Resolved the problem where related relation columns were not displayed when editing a table view, related relation columns, which show neighboring element values, now appear correctly during table view edit.

• Simplified the JSON model for pushing graph-data to Qbilon.
• Reduces the amount of data sent to Qbilon.
• Model also used for querying data from Qbilon.

• Qbilon can run any docker image (amd64).
• Adds the possibility to write own tasks, dockerize them and run them as a normal task in Qbilon.
• Own Tasks can now be integrated into the Qbilon data-workflows.

• Added a new endpoint to facilitate writing and updating data in the consolidation database.
• Provides an easy way for users to create their own tasks that can directly interact with the database.
• Simplifies the process of managing data and streamlining workflows for users.

• Introduced new read endpoint to fetch nodes and edges, including options for filtering by specific type/relation.
• The endpoints are accessible via basic authentication for secure access.
• The response includes the data-source specific IDs for each node/edge, enabling users to directly modify existing elements via the write endpoint.

• Access Qbilon API with Basic-Auth Authentication.
• Basic-Auth can be used to gain access to the Qbilon API without the browser login-workflow.
• Useful when implementing own tasks that need API access but cannot run the browser login-workflow.

• Redesigned the task creation flow using step-by-step navigation for improved usability.
• Introduced four distinct steps: task info, data source settings, execution settings, and summary.
• Simplified data entry by replacing the single-page format with an intuitive, guided process.

• Replaced passhash-based authentication with the more secure PRTG Autherisation API key, ensuring credentials are no longer passed in the URL query.

• Introduced the ability to delete multiple element and relation types simultaneously in the metamodel.
• Furthermore added functionality to delete multiple elements and relation instances at once directly in the graph view.

• Replaced the in-house user and token management system with Keycloak for enhanced scalability.
• Leveraged Keycloak’s features to streamline authentication and authorization processes, ensuring better interoperability with other tools.

• Introduced structured tables in the Data Management tab, displaying key details such as Type, Name, Status, Last Execution, Next Execution, Triggered Tasks, and Actions, making it easier for users to track and manage tasks and workflows.

• Added search fields to quickly locate specific workflows and tasks within the Data Management tab.

• Addressed the updating of property with a List type in graph view’s edit mode throw an exception, users can now successfully update list-type property values without encountering errors.

• Fixed the bug where the “contains element with” operator behaved differently for “list of numbers” properties in view definition versus graph view, ensured consistent functionality across both view definition and graph view.

• Solved the problem where elements in the context view were not recognized when searched using capital letters, only responding to lowercase.
• Elements are now correctly recognized regardless of case, ensuring accurate search results.

• Enhanced the usability where users couldn’t manually delete entries in the property field when defining a color rule.
• Users now can easily delete typed entries and search for new properties.

• Fixed the deleting of “Name” attribute in the metamodel also deleted all instances of that type, now instances are not deleted when the “Name” attribute is removed.

• Rectified deselecting a service in the “Services” field of the ServiceNow data source wasn’t saving changes.

• Resolved the bug that resulted in repeated properties when a relation was created and a new column was added in table view.
• Ensured no duplication of properties for source and target types when adding new columns in the table view.

• Resolved problem where filters defined with the current date and time in the table view displayed as “invalid date” in the sidebar, fix make sure that current date and time entered in the filter are properly displayed and functional.

• Fixed downloading individual views resulted in all files being named “tmp.db” instead of their respective names, files are now correctly named when downloading individual views.

• Reworked the display of sublabels set to a datetime property were being displayed in UTC time, sublabels now correctly display in the local time zone instead of UTC.

• Redesigned the entire UI with a fresh, modern look, featuring our new corporate design.
• Added purple as the main accent color and Qbilon red for the logo to reinforce brand identity.
• Simplified navigation by removing Dashboard and Reports tabs for a cleaner, more streamlined experience.

• Enhanced ServiceNow Writer to allow writing of relation types in addition to element types, broadening integration capabilities.
• Users can now also write relation between element instances, expanding flexibility in data structure representation.

• Enabled cross-type merging in the UI, allowing users to merge nodes of different types, enhancing data consolidation flexibility.
• Updated the merge configuration UI to support selection of a secondary type, aligning the frontend with backend capabilities.
• Added functionality to create a new merged type dynamically (e.g., merging Type A and Type B into a new Type C).

• Expanded temporal constraint options by introducing hours and minutes as additional time units.
• Enhanced flexibility to meet varied time constraint needs beyond the existing units (years, months, weeks, and days).

• Enabled deletion of attributes for element types and relation types within the metamodel, enhancing customization options.
• Users can now remove unwanted attributes after activating edit mode, providing greater control over data structures.

• Introduced batch operations to allow users to delete or download multiple views simultaneously, reducing the time and effort required for repetition.
• Enhanced interface allows for easier management of views, making it more efficient for users to handle large list of views.

• Introduced external connectors for VSphere, LUY, Darktrace, and PRTG, broadening data collection capabilities.
• Run these connectors as a docker container on any other machine/host.
• Ability to run them once but also to schedule them.

• Enabled deletion of element and relation types directly within the metamodel, enhancing data management.
• Users can now remove unwanted Element and relation types after activating edit mode, providing greater control over data structures.

• Fixed exceptions related to deserialization failures, ensuring that data is accurately processed and improving the reliability of the Azure Connector.
• Addressed the issue of duplicated elements, enhancing quality of the data retrieved by the connector.

• Adjusted the SNOW import process to infer data types per attribute rather than per individual property, ensuring that all instances of the same attribute share a consistent data type.

• Fixed the statement timeout exception that occurred when running multiple complex connectors simultaneously, ensuring smoother operation during large parallel data inserts.

• Rectified the issue where expanding and collapsing nodes via right-click toggles incorrectly enabled disabled buttons, disrupting the user experience in the graph view.
• Ensured that the expand and collapse buttons remain disabled when the maximum node expansion is reached.

• Fixed the issue where the navbar failed to highlight the current position when navigating to subpages like graph, table, or chart view creation, ensuring users can easily identify their location within the application.

• Resolved the issue where the “and” operator was not correctly evaluating multiple conditions for color rules when “cell-wise” coloring was enabled, ensuring accurate application of color rules.
• Now, colorization is applied only to cells that meet all specified conditions within a row, preventing incorrect color application to cells that do not fulfill the entire “and-rule.”

• Addressed preventing the list of relations for a node from appearing in the sidebar.
• Fixed the sidebar to correctly display all relations of a Node, allowing users to easily navigate and understand the connections of nodes within the graph view.

• Fixed the problem where optional names for constraints defined during view creation were not being applied correctly, ensuring that users can assign and see their intended names for the constraints.

• Resolved the issue where the title bar in focus and context views was cropping text due to multi-line display, ensuring that all titles are fully visible without truncation.

• Modified where long element names in graph views caused overlaps with sublabels, ensuring a clear and organized display of all text.
• Implemented adjustments to label formatting, allowing long element names to be displayed without compromising the visibility of associated sublabels.

• Introduced a new webhook task type that allows users to specify a URL for data retrieval.
• Implemented functionality to fetch Elements and Relations data from a selected graph view and transmit it to the specified URL for seamless data export for customers without ServiceNow, enhancing Qbilon’s compatibility with third-party systems.

• Introduced a new checkbox in the view-creation UI labeled “Enforce structural constraints” allowing users to enable constraints on relations to match a certain structure.
• Enhanced user control over graph view selections, allowing isolated elements to be excluded and ensuring compliance with the selected metamodel pattern for more accurate data representation.

• Enhanced the frontend filter options by adding new temporal constraint types for DateTime properties, allowing users to filter by “within last” and “not within last” based on a customizable timeframe.
• Updated the dialog with an integer-only number field and a unit selector for “days” and “weeks,” providing more control over temporal data filtering.
• Enabled users to apply these constraints to any DateTime property, expanding beyond “LastSeen” for more versatile temporal data management.

• Streamlined the device fetching process by retrieving all devices in a single request, eliminating the need for an initial count-fetch step.
• Enhanced efficiency of PRTG integration, resulting in faster data processing and a more responsive user experience

• Refined data retrieval from the PRTG to fetch only the necessary columns, reducing the volume of unnecessary data.
• Improved task speed and performance, particularly for large datasets, by minimizing data transfer and processing time.

• Extended Azure Connectors to support 10 additional services, including Azure DevOps, Azure Functions, and Azure Key Vault, increasing total Azure service coverage to 25.
• Added integration for specialized services such as Azure Synapse Analytics, Azure Machine Learning, and Azure Service Bus, enabling broader data connectivity and enhanced functionality.

• Enhanced AWS Connector functionality by adding support for 13 additional services, bringing total AWS service coverage to 25.
• Integrated key services such as Amazon CloudFront, AWS Elastic Beanstalk, and AWS Route 53, AWS Fargate, AWS Redshift, and AWS Step Functions enhancing cloud connectivity and resource management capabilities.

• Optimized TopTalker data retrieval by consolidating 12 separate requests into a single, unified request, filtering all relevant sensor types at once.
• Improved the speed and efficiency of the PRTG data source.

• Launched a new API endpoint allowing users to query stored nodes and edges.
• Enabled data retrieval using our BlueprintDTO, facilitating easier access to stored graph data through the API.

• Standardized logging practices across all connectors ensuring a unified logging approach.
• Extracted and organized all relevant logs for each connector, enhancing clarity and consistency in log management.

• Fixed a critical issue where connectors were occasionally not created correctly, leading to backend errors.
• Ensured that predefined views are consistently generated upon connector creation, enhancing reliability and user experience.

• Resolved the issue where the “Add Property” button was incorrectly positioned at the bottom of the list in edit mode within the metamodel.
• Ensured the button is now prominently displayed at the top of the list when adding an attribute in the metamodel.

• Introduced a cancel/close button in the table view search bar, allowing users to easily clear their search input.
• Enhanced user experience by providing a straightforward way to reset the search field.

• Resolved the issue where the cursor shape did not change appropriately when hovering over different analysis buttons in the view definition.
• Ensured that the cursor now reflects the intended action, enhancing interface interaction.

• Resolved the issue where previously selected elements or relations remained pre-filled in the filter dialog after cancellation.
• Ensured that the filter dialog opens empty each time, providing a fresh start for users when creating new filters.

• Resolved the issue preventing users with the “Architect” role from deleting datasources.
• Ensured that the deletion functionality is now accessible, allowing architects to manage datasources effectively.

• Resolved the issue where the execution type “dependency” appeared as an empty space in the data management tab.
• Ensured that “dependency” is now correctly displayed as the execution type, enhancing clarity.

• Resolved the issue where the “Add Element” dialog was pre-filled with previous entries instead of opening empty.
• Ensured the dialog now provides a blank slate for users, allowing for fresh inputs with each new addition.

• Resolved an issue where the button for the sign in with “OIDC provider” was not properly displaying, ensuring the name fits perfectly within the button.

• Resolved a bug where the highlight box indicating the searched Element remained visible after the search query was deleted.
• Improved user interface functionality by ensuring that the black box disappears after deleting the query.

• Implemented a dedicated page that informs users when they attempt to access restricted areas without sufficient permissions.
• Users are no longer logged out when attempting to access unauthorized pages, ensuring a smoother and less confusing experience with clear error messaging. The page also provides a button to navigate back to the home page.

• The context view selection workflow has been updated such that the view has to be chosen before the start element, making the process more logical and user-friendly.
• Removed confusing type filtering and type symbols from dropdowns to reduce complexity and prevent misinterpretation between types and elements.
• Element selection is now disabled until a view is chosen, and the “Open View” button is disabled until both selections are made, ensuring a clearer step-by-step configuration.

• Created endpoints to return only the types and relations relevant to the view’s blueprint.
• Moved filtering logic from the frontend to the backend, improving efficiency and reducing unnecessary data processing on the client side.
• Enhanced overall performance by minimizing data payloads, leading to faster load times and a more responsive user experience.

• Added column-level constraints and four writing metrics (Attribute, Reference, Static Value, Neighbor Attribute) for more flexible data handling.
• Simplified reference handling by automatically using “ServiceNow System ID” for neighbors, removing manual entry requirements.
• Introduced an intuitive UI for managing constraints and ensured validation for all inputs, with easy entry deletion options.

• Introduced functionality to automatically populate the license key and system ID on the activation page, with optional encoding for added security.
• If the query parameters are not present, the input fields will remain blank, ensuring that manual entry is still possible if needed.

• Fixed an issue where tasks appeared as activated (green) on the frontend despite backend errors caused by invalid credentials provided to the ServiceNow writer.
• Task are now correctly displayed in an error state when invalid credentials are detected, providing a more accurate reflection of task status.

• Rectified the post-license activation flow to redirect users to the home page instead of the misleading “Access Expired” error message, as the user remains logged in throughout the process. This ensures a seamless experience without unnecessary interruptions.

• Resolved an issue that prevented view generation with temporal constraints like “seen within last month,” “seen within last week,” and “seen within last day”, thereby aligning functionality with user expectations.

• Fixed an issue where nodes were not deselected when their properties changed, causing them to be removed from the view while they were still selectable.
• This prevents exceptions and ensures that node interactions are accurately reflected in real-time.

• Adjusted the issue where navigating to the /app route displayed an empty screen by implementing an automatic redirect to /app/home.

• Corrected an issue where adding a new edge in a graph view worked initially but failed on subsequent attempts when editing mode was enabled.
• Users can now continuously add edges without interruptions, ensuring reliable performance when modifying graph structures.

• Solved an issue where saving a graph with ‘Save View as Default’ preserved the view on the starting page but did not maintain filters and layout when accessed from the dashboard.

• Updated the color rule creation process to ensure that the order of selecting a property and element/relation type does not affect the validity or display of the color rule.

• Adjusted the logout process to reset the refresh token, ensuring that users are correctly redirected to the /login page after logging out.
• Users attempting to navigate to /app/home or any other restricted page post-logout are now properly redirected to the /login screen, maintaining security and session integrity.

• Replaced the “eye” icon in the task list with an “info” icon to better convey the context of the information.
• Switched the “bookmark” icon to a “chainlink” icon for clearer representation of link-related actions.
• Replaced the dropdown for the “hide isolated elements” setting with the MDI “group” icon.
• These changes enhance the look and feel of the web app, making icons more meaningful and improving overall usability.

• Fixed an issue where deleted users could still log in.
• Ensured that deleted users are immediately logged out of active sessions and cannot log in again.

• Prevented unauthorized actions such as deleting elements, modifying properties, and editing filters or color rules.
• Ensured that each role (user, architect, demo, admin) can only access and modify features as defined in the permissions.

• Ensured that after changing the property for relation analysis, the operator and value fields are reset to prevent creating invalid rules.
• Stabilized the color palette so it remains consistent when switching between element and relation analysis modes.

• The license banner has been removed from the metamodel view, ensuring a cleaner interface.

• Addressed an issue where adding values to lists occasionally overwrote existing values.
• Users can now add values to lists consistently as expected.

• Addressed an issue where the name-giving property for elements or relations was not updated if the database already contained newer information.
• Enhanced synchronization between the graph information and the database to maintain accurate property settings.

• Corrected an issue where toggling the “relation folding” feature in graph views failed to work.
• Users can now seamlessly switch between displaying parallel relations as separate lines or as a merged thicker line.

• Removed the “Save” and “Share Link” buttons for users with regular access permissions.
• Ensured that only authorized roles have access to these functionalities.

• Corrected the failure in the “UVexplorer File Import” connector that prevented the import of UVexplorer test data.

• Implemented a new connector to facilitate data extraction from Google Cloud Platform (GCP).
• Successfully integrated GCP Projects, Compute Engine, Cloud Storage, and Cloud SQL into our system.
• Expanded cloud compatibility by supporting GCP, the third-largest cloud service provider.

• Introduced functionality to reorder color rules within filter groups in graph and table views for a more flexible analysis.
• Eliminated the need to delete and recreate rules, streamlining the process and making it more intuitive.
• Allowed users to easily change rule priorities, ensuring the correct rules are applied without conflicts.

• Fixed the bug where CSV files disappeared when editing a data source, thus preventing unnecessary re-uploads.
• Users can now edit the name of a CSV data source without the need to re-upload files, streamlining the editing process.

• Addressed issue of displaying extensive CSV file details in “Data Source Task Details”, ensuring a cleaner and more user-friendly interface.
• Improved the overall readability of data source details by displaying only relevant information.

• Fixed issue where users were not redirected to the login screen after their access token became invalid.
• Ensured that users are properly redirected to the login page when unauthenticated, improving security and user experience.

• Reformatted the “ServiceNow Writer” data task details, making the information more concise and easier to understand.

• Addressed the conflicting highlighting of all elements containing a search string and specific highlighting for elements selected from the drop-down list.
• Fixed the issue where the “highlight frame” was not removed upon clearing the search field, ensuring a clean reset of the search state.

• Fixed an issue where cancelling a layout left the graph in a strange state, with the selected layouter remaining the canceled one.
• Clicking the “re-layout icon” now consistently applies the selected layouter, as intended.

• Ensured that the two rows of text are compact enough to fit within the title bar’s height, through changes in spacing and text size.

• Fixed the issue where report filters were not functioning properly.
• Addressed an issue where navigating to other pages from within a report was not working.
• Ensured that cards resize properly when changing the width of the side-bar.
• Fixed tool-tips on charts to ensure that they are displayed correctly.

• Fixed the issue where the context view dialog did not load all instances for a given type.
• Implemented changes to ensure that all instances are properly loaded and displayed in the drop-down list.

• Addressed the issue where source and target elements were incorrectly labeled on the views detail page.
• Adjusted the labeling so that “Source” accurately reflects the source element and “Target” accurately reflects the target element.

• Adjusted the spacing in the “Tag Filter” drop-down menu to ensure entries are shown in a more compact and dense format.
• Fixed the errors in the background that were thrown when the report was initially opened and when the tag filter selection was changed.

• Reduced unnecessary height in filter and color rule rows, minimizing the need for vertical scrolling and enhancing overall usability.

• Introduction of on-premises Active Directory (AD) authentication capability for Qbilon’s Single Sign-On (SSO) frontend.
• Enables seamless integration with on-premises AD environments, facilitating user authentication and management for organizations utilizing Qbilon.
• Provides enhanced convenience and security for users, streamlining user management processes and ensuring alignment with existing on-premises infrastructure.
• Customizable mapping feature allows users to associate AD security groups with corresponding roles in Qbilon, providing flexibility to adapt to varying organizational structures and naming conventions.

• Added a new data source to load users and user groups from a local Active Directory.
• Implemented functionality to synchronize user data from Active Directory, thereby enabling visualization of users and security groups in a graph view.
• Enabled automatic updates to keep user information up-to-date.

• Implemented the ability to exclude certain element types from the total count of licensed elements, as specified by Qbilon.
• Added clear indications within the meta model page to distinguish between billable and non-billable elements.
• Updated the license information display and alert banners to explicitly show the status of non-billable elements and notify users when their element count is nearly full or has reached its limit.

• The new property field is now added at the top of the properties list in the sidebar.
• Enhances user experience by ensuring the visibility of the property input field, especially in cases with numerous properties.
• Resolves the issue of the scrollbar appearing misplaced within the properties table.

• Azure disks within the default “Azure subscription overview” are now organized within their associated resource groups, improving visual clarity.
• Introduces a “container” relation between Azure Resource Groups and Azure Disks, streamlining the overview presentation.
• Addresses aesthetic concerns post-initial import, enhancing user experience, especially for scenarios like cloud demos.

• Default setting for “Rows per page” in the view list increased.
• “All” option removed to prevent potential performance issues and unnecessary navigation.
• Enhances user workflow by reducing the need for frequent scrolling and navigation, particularly on screens with ample space.

• Upon navigating to “Data Management”, the list of entries (data sources and data consolidation tasks) now defaults to a comprehensible sorting order.
• Eliminates user frustration associated with navigating through apparently random entry orders, improving overall workflow efficiency.

• Implemented text hints to indicate when a graph or table view lacks inclusion of relation types.
• Enhanced user experience with logical feedback regarding missing relation types within the view definition.

• Transitioned from a custom notification implementation to Vuetify Snackbar component for frontend notifications.
• Improves user experience with a leaner, more reliable, and aesthetically pleasing notification system.

• Implemented functionality to store temporary filter settings, including their activation state, when generating shareable links for graph views.
• Ensures that temporary filters remain intact and visible upon reopening a shareable link, maintaining consistency between saved and visible states.
• Enhances user experience by fulfilling the promise of preserving the current visible state when utilizing shareable links, thereby reducing discrepancies and improving usability.

• Addressed issue where selected rows in tables cannot be deselected by clicking outside the table.
• Implemented intuitive deselection functionality to allow users to clear selected rows easily.

• Enhancement allowing users to define constraints within the ServiceNow exporter, specifying criteria for element selection.
• Enables users to export only elements meeting specific conditions, such as having certain tags fulfilled or belonging to particular regions, enhancing customization options.
• Improves user experience by providing greater control over exported data, ensuring only relevant elements are included.

• Ensured that activating or deactivating a color rule in graphs with containers now consistently applies the rules to all relevant relations and ensuring all conditions are uniformly met.

• Corrected the vertical alignment of analysis rule icons to match the filter icons, now aligned to flex end for uniformity.

• Resolved errors occurring when editing empty values in-line within tables, ensuring smooth and error-free updates.
• Empty values can now be edited and updated correctly without any issues.

• Fixed the creation of temporary color rules in default table views, ensuring functionality as expected, allowing for the correct application of temporary color rules.

• Updated the manual element creation dialog to require a value for the name-giving property, preventing the creation of elements with empty names.
• Ensured that users cannot bypass entering a value for the essential name-giving property during element creation.

• Addressed a null pointer exception by handling cases where TaskTrigger is null.
• Ensured that the application no longer encounters null pointer exceptions in the mentioned scenario.

• Fixed an issue preventing the reimport of view definitions containing related relations, ensuring smooth import without error messages.

• Resolved an issue where the merger tool was using a random name property, instead of the intended property.
• Fix will ensure to use the namegiving property of the first element during a merge, ensuring consistent and logical behavior in property selection.

• Addressed an issue where the task system was encountering a null pointer exception when deleting a data source under certain circumstances.

• Fix ensured a better error message for empty CSV file uploads, improved validation to accurately detect and handle empty files or attempts to upload relation files without corresponding element files, ensuring clearer guidance for users.

• Modified the CSV connector to better handle mixed data types in columns, ensuring that it can generalize to the appropriate data type (Text) based on all values in a property’s column.
• Improved consistency in data type inference, preventing issues where a strict data type (e.g., Number) appearing first would cause errors when less strict types (e.g., Text) appear later in the same column.

• Enhanced usability by providing a comprehensive selection of properties, addressing scenarios where users need to link multiple types with uncertain property availability.
• Enable selection of properties from all available options across selected types in the custom linker.
• It will ignore element lacking certain properties, ensuring seamless integration with the backend’s capability.

• Enhanced parsing capabilities for “portList” CSV files, ensuring accurate interpretation of headers and seamless representation of CSV rows.
• Users can now import port lists with greater reliability and precision, reducing errors in data interpretation.
• Users will experience improved accuracy in graph representation, ensuring a more comprehensive view of network topology and connectivity.

• Updated the status label of data sources from “Coming Soon” to “On Demand” to better reflect their availability status.
• By changing the label to “On Demand,” users understand that these data sources are available upon request, aligning with their actual availability status. This also ensures transparency and accuracy in communication.

• Introduced a new default chart showcasing statistics about used sensor types, providing immediate insights into sensor distribution and usage patterns.
• Enhances utility for users, particularly existing PRTG users, by offering more relevant and actionable information aligned with their familiarity with sensor types.
• Improves overall user experience by delivering more valuable insights, increasing user satisfaction and engagement with the platform.

• This enhancement aims to address a limitation in the current AWS import functionality where all regions are considered without the option to limit them according to user preferences.
• The proposed solution introduces a filter option during import, allowing users to specify only the relevant regions for integration into Qbilon. By incorporating a further select field in the importer, users gain the ability to explicitly select desired regions, aligning the import process with their specific requirements and preferences.
• This enhancement is driven by customer feedback, providing a tailored solution to improve usability and efficiency within the AWS import feature of Qbilon.

• Considering enhanced layer information during container view creation, the enhancement delivers a more intuitive and coherent display of data, improving user understanding and usability.
• Before this extension, child elements were randomly assigned to parent or child containers, leading to confusion in data presentation. Now, when determining the placement of child elements, the system prioritizes the mid layer if it exists in the hierarchy, aligning with user expectations for hierarchical structure.
• Child elements with relations to both the mid and top parent are now consistently displayed in the mid element, meeting user expectations for deterministic data presentation.

• Addressed an issue preventing users from manually adding elements with negative numbers in numeric properties.
• Users can now input negative numbers without encountering validation errors.

• Resolved issue where collapsing group elements (containers) did not reduce their sizes as intended in the graph view.
• Group element sizes now shrink appropriately when collapsed, enhancing visualization clarity and space utilization.

• Fixed the hierarchy relations within standard views, ensuring clarity and structure in visual representations, notably in views like AWS Security Group Accessibility View.

• Updated links to ensure accessibility and relevance; disabled connectors linked to obsolete URLs directing users to non-existent content.

• Implemented functionality to enable seamless modification of the namegiving property, reflecting changes in the displayed name.
• Users can now efficiently update namegiving properties within the graph view, ensuring accurate element representation.

• Corrected the dropdown behavior to display only unique values within the list, enhancing usability and reducing clutter.
• Implemented fix to ensure aligning with expected behavior and improving user experience.

• This bug fix addresses an issue where random errors occurred during the import of multiple views, while importing a single view proceeded without any problems.
• With this bug fix, users can now seamlessly import multiple views without encountering any errors, ensuring smooth and uninterrupted integration processes.

• This bug fix addresses an issue where relation filters were absent when creating a table view over relations in the system. Users observed that despite selecting relations in the initial steps of table definition, the corresponding relation filters were not displayed as expected.
• With this bug fix, users can now create table views over relations, as all selected relations will display their respective filters, ensuring clarity and accuracy in data representation.

• This bug fix resolves an issue where users were unable to change the passwords via the user tab within the system. With this bug fix implemented, users can once again reset the passwords seamlessly through the user tab.

• Addressed issue where users were automatically logged out after activating a new Qbilon instance with a valid activation code.
• Ensured that users can seamlessly use Qbilon without the need for re-login after initialization.

• Addressed issue preventing users from creating relations on the metamodel page.
• Eliminated an exception thrown during the creation of new relations, enhancing the overall user experience.

• Rectified issue where deleting a linker caused exceptions and incomplete deletion.
• Ensured proper deletion of linkers, now removing associated edges from the database and updating metamodel edge count accordingly.

• Fixed warning system for ServiceNow connector when users lack permissions to load custom tables.
• Addressed error handling and log insufficient permission errors, ensuring smoother operation of the connector.

• Resolved issue where saved relation filter rules were not working after being saved.
• Maintain functionality for activating and deactivating saved relation filter rules as expected.

• Fixed issue with PRTG merger failing after multiple imports, especially with CSV data.
• Ensured consistent functionality of PRTG merger across all scenarios, including cases involving CSV imports.

• Resolved backend error preventing updates to name-giving properties of edges.
• Enabled functionality to modify name-giving properties of edges as expected.

• Addressed multiple minor issues within the merger functionality.
• Improved overall stability and performance of the merger feature.

• Rectified issue preventing deactivation of scheduled tasks.
• Scheduled tasks can now be deactivated without encountering any problem.

• Modified connector name as specified on the website for improved consistency and clarity.

• Fixed issue with deleting individual data sources.
• Users can now successfully delete single data sources as expected.

• Resolved issue preventing users from viewing content; users can now access views as intended.
• Addressed the issue where users were unable to see views, restoring expected functionality.

• Rectified issue preventing the creation of table views with two relation columns, users can now seamlessly create views as intended enabling a smooth creation of views.

• Resolved issue where the JSON Push connector was malfunctioning, resulting in a 401 exception.
• Ensured that JSON data can be successfully sent to the backend as expected.

• Addressed critical issue where upsert functionality was non-functional.
• This hotfix ensures that upsert operations now work as expected.

• Resolved issue where users could log in with any password when OIDC is enabled.
• Implemented fix to ensure password validation is enforced during OIDC login authentication.

• Addressed issue where running a merger followed by a data source resulted in an exception.
• Implemented fix to ensure smooth execution without exceptions during the mentioned process.

• We resolved a critical issue with the JSON Push connector that rendered it unusable.
• All running instances now remove their current non-functional JSON Push connectors, as they were not operational prior to this fix.
• This update restores full functionality to the JSON Push connector, ensuring seamless operation for all users.

• Our development team has been working hard on optimizing Qbilon for high scalability. Since version 2.0, Qbilon now features a new PostgreSQL database, which requires significantly less resources and uses less memory.
• With the new database, Qbilon is now capable of processing a significantly larger number of elements.

• With this new data connector – which is currently only file based – is it possible to get the results from a layer 2 discovery with UV Explorer into Qbilon.
• The data from UV Explorer enable to create a network map to visualize which device is connected to which switch via which port.
• Mapping the data with, e.g. PRTG, it can be seen how much of the network is covered by a monitoring tool like PRTG.

• PRTG allows characters that are not valid in the XML definition which can cause XML parsing to fail.
• We’ve added filtering for those characters to ensure greater robustness when loading PRTG data sources.

• We addressed potential conflicts with other data sources by adopting a consistent naming scheme, mitigating side effects when importing elements with similar types.
• Introduction of prefixes for Microsoft Entra ID data elements, ensuring clarity and distinction, e.g., “Group” is now named “Entra ID Group”.

• Fixed a bug that occurred when importing a PRTG data source that contained an empty PRTG probe without groups or devices.

• Again, a lot of work has been done in the background to create a more efficient, high performance database that can load huge amounts of data. To give you an idea, here are a few numbers:
  • 1.639 tests have been written to avoid any issues with the new database.
  • 3.000.000 elements could be loaded into Qbilon without any problems.
• The new database will be published with the next release.

• With our latest update, we’ve been able to make significant improvements to our quality assurance (QA) processes, resulting in a noticeable increase in speed and reduction in storage space. Our main focus was optimizing Merger and Linker functions, resulting in an impressive 60% increase in speed.
• The optimizations implemented in the Merger and Linker components have improved performance when handling large datasets. This includes significant reductions in both time and memory consumption during linking and merging operations.
• Another notable achievement is the successful refinement of our database housekeeping processes. This improvement has resulted in a significant reduction in disk space usage, contributing to a leaner and more efficient storage system.

• Resolved issues causing negative costs for PODs, deployments, and namespaces in the “current month”, ensuring accurate calculations.
• In addition, the performance has been optimized for a seamless transition between months.

• The system now recalculates the relative next execution time immediately after a restart, ensuring that all connectors are correctly scheduled and executed as intended.
• This fix addresses reliability concerns, ensuring consistent operation.

• We addressed a critical issue where the Azure connector experienced timeouts while attempting to connect to management.azure.com. These connection timeouts have been eliminated, ensuring that the Azure connector operates within its expected time frame.
• After applying the fix, no further timeouts were observed in both SaaS instances and local tests.

• This fix ensures the stability and integrity of the PRTG connector, allowing for seamless parsing of XML responses.

• With this bugfix, the “Last Seen” properties are updated correctly.

• We’ve successfully fixed a bug in the tooltip format for the regex hint during constraint creation, which was displaying with buggy HTML tags.
• This fix improves the user experience by providing clear and properly formatted information while creating constraints.

• The fix ensures that evaluations now correctly encompass both specified properties, aligning with our documentation and enhancing the reliability of data consolidation processes.

• We’ve expanded the PRTG data connector by incorporating additional valuable information, enriching the scope and depth of available data for your analysis.
• Qbilon now offers the ability to import in-depth properties for analysis into:
  • all probes and groups
  • all devices within the probes and groups
  • all sensors with their respective primary measured values.

• The new connector allows you to retrieve the system information from PRTG for every device which is particularly valuable in scenarios involving other data sources, e.g. vSphere, as it provides important details such as system versions.

• In addition to automating the writing of all IT elements, you can now effortlessly write and update your relational data in Qbilon to ServiceNow.

• Keep track of every change to our system. The changelog is now easily accessible in the handbook, empowering users to understand the evolution of our platform and the value each update brings.

• For larger organizations with multiple Azure subscriptions, the need for efficient management becomes paramount. Hence, in this update this capability is extended to the tenant group level allowing users to also import Azure Management Groups.
• For a complete understanding of Azure Management Groups, please refer to Microsoft’s official documentation: Azure Management Groups Overview.

• Resolved an issue where the colors in the chart preview were incorrect, ensuring an accurate and reliable visual representation of data.

• Improved user experience by alphabetically sorting every unsorted dropdown menu in the chart definition, making it easier for users to locate and select options.

• Users can now easily recognize and associate the PRTG merger with the updated icon, contributing to a more cohesive and memorable user experience.

• Addressed and rectified the issue causing inaccuracies in the calculation of the next execution time.

• The fix ensures that the license expiration banner reflects the correct information, eliminating any confusion or misrepresentation. This means users will receive timely accurate alerts about license renewals, helping them to manage their resources more effectively.

• When the name giving property doesn’t exist, the qbilon ID is used.
• Now, the name giving property changes with the strategy based element/relation updater.
• Therefore, we now can update the name giving property.

• The fix contributes to a more efficient editing workflow as dropdown lists in edit mode are now sorted alphabetically, thereby reducing the time spent and searching for specific options.

• When adding a new color rule within an existing table view, the rule can be saved, modified or deleted now.
• Furthermore, existing rules can be modified.
• Therefore, colorings (“per cell” or “whole row”) no longer produce errors and creating additional rules doesn’t cause any unexpected issues.

• The majority of services have now been successfully migrated to the new database.

• The “ServiceNow Writer” is designed to automate the process of transferring data collected, merged and consolidated in Qbilon back into the ServiceNow database.
• This feature improves the completeness and integrity of all information on IT assets and their dependencies in ServiceNow.
• The “ServiceNow Writer” can be configured to write back specific asset types at a scheduled interval and in the format preferred by the user.

• The documentation for our software has been fundamentally revised and brought up to date.

• The relation labels toggle setting is now applied when navigating through containers, especially when the default view is set with “activated relation labels”.
• The behaviour is consistent throughout the graph. Either all relation labels are displayed or none

• Color rules for relations can be edited, saved, and deleted in the same manner as for elements.

• Server and infrastructure elements having the same IP address are consolidated.
• IP addresses are only used for merging when the information is deemed “new” (as within the server merger).

• The Darktrace connector is now functional at both short and long intervals.

• The data preview does not undergo recalculation when the color changes.
• The color picker can now be used smoothly without excessive loading times.

• The migration of the database remains one of the main focuses in development, leading to several updates occurring outside of the Qbilon application and not being reflected in the changelog.
• Tremendous strides have been accomplished with the successful implementation and testing of the initial services.

• The JSON Push data connector facilitates loading and storing data in Qbilon, without requiring a pre-configured data source. Its versatile “push” interface seamlessly transfers data into Qbilon, enabling storage, merging, and analysis of relevant information from all your existing systems in one tool.

• Qbilon now offers the ability to filter elements by type in the element search field for context views.

• Linker and merger conditions have increased expressiveness thanks to an editable dropdown field for the “Operator”. The Operator dropdown offers the following options for selection: [equals, contains, contained in, smaller than, greater than, smaller than or equal to, greater than or equal to, intersects with]. The default value is “equals”.

• All default colors in the Azure, AWS, vSphere, PRTG and Darktrace standard views now conform to a specified color palette.

• There are notifications for all types of users warning about the expiry of the license/activation.
• Furthermore, there will be a notification if the limit of the maximum numbers of elements will be reached soon.

• Azure AD has been renamed as Azure Entry ID (formerly Azure AD) throughout Qbilon.

• The PRTG data connector now includes data from a wider range of PRTG sensors.
• In addition to NetFlow, Qbilon can now process data from Juniper devices (jFlow) and industry standards such as HPE, Arista and Fortinet (sFlow).
• Qbilon now also captures the top talkers of the following sensor types in addition to NetFlow sensors:
  • IPFIX
  • IPFIX (Custom)
  • JFlow v5
  • JFlow v5 (Custom)
  • NetFlow v5
  • NetFlow v5 (Custom)
  • NetFlow v9
  • NetFlow v9 (Custom)
  • sFlow
  • sFlow (Custom)
  • Packet Sniffer Sensor

• The “Delete All” button has been removed from the “data sources and data consolidation” view.
• Instead, adminstrators of Qbilon can now perform a “Software Reset” in the “Advanced” tab found within the settings page. This reset will require confirmation in an additional dialog.

• Sorting in chart views now follows the same implementation as table views, meaning no string ordering is applied. Instead, sorting is based on integer/float values.

• The preview image is now set correctly when switching views.

• The relation is now accurately shown in the meta model.

• The new name will now immediately appear in the search field after updating the element’s name.

• The JSON connector now enables users to upload multiple JSON files at once and supports lists of primitive properties.

• The latest version of ADOIT, v16.0, has been released by the BOC Group this year.
• With Qbilon Ultimate, users can now import data from this Enterprise Architecture Management tool in Qbilon and connect it with data from other data sources.

• As a customer, you can now activate, reactivate or upgrade your Qbilon Ultimate instance independently.
  • If a license has not been obtained yet, an initial license activation page will appear when starting the Qbilon application, where you can import a license file.
  • If your license has expired, you will be redirected to a page to reactivate it, where you can import a new license file.
  • Additionally, you can update or upgrade your existing license anytime through “Settings” -> “Update License”.

• If in edit mode, the namegiving property is editable by clicking on the property name.
• An autocomplete field will display all available property values and their corresponding names for proposals

• To improve recognition of Azure resources, we now label “Remaining Resource”, “Log Analytics Workspace”, “API Management Service” and “Front Door” with the prefix “Azure”.

• “Azure Blob Storage” has been removed from the Azure Importer and the standard views included in the Azure connector.

• Qbilon now retrieves account information from AWS and is able to associate each AWS resource with the corresponding account.

• Instead of providing the license in the frontend or with a POST to a secured license endpoint, it can now be read from a file.
• The license file is called “qb.license”.
• There is a new env “QB_LICENSE_FOLDER” which defines the license folder.

• The size of an icon when using the “Icon” element style is now set to 48×48 pixels.

• The hint “There are no analysis rules defined. Add rules by editing this view in the ‘Views’ section.” only appears when the analysis rule set is empty.

• When opening a view that doesn’t show any asset instances, i.e., no elements, the message “There are no elements to show, because there are either no element instances anymore or the current filter selection hides all elements.” appears.
• The hint appears for all types of views, i.e., graph, table and chart views.

• When editing relation names in graph views, the respective labels are updated immediately after saving.

• If you change the color of an element during graph view definition and then try to change the color of another element, the color of the first element is not preselected in the color picker dialog.

• We are currently working on the integration of a new database to make Qbilon even more powerful in large IT environments.
• This improvement will be done mostly in the background, but we will provide updates on the progress from time to time.