Release date:
This release makes it easier to manage and govern your SAP BusinessObjects content at scale. You can restore archived documents in bulk and manage archived objects directly from the Resources views, and you can update the next run time, email delivery settings and server groups of recurring instances in bulk.
360Eyes usage counts now include objects used in charts, and Webi Repoint explains why a data provider cannot be repointed.
This is a large release, with much more below than we can summarise here. Please read the full release notes, including the Change Logs, which cover changes that need action when you upgrade.
As always, you can find important links just below.
⬇️ Download 📖Full documentation 💡Knowledge base 📊 Product Availability Matrix 📞Customer support
You no longer need to stay on the Diagnostic page until it completes. Start a Diagnostic, navigate elsewhere, and come back later to find the result without losing progress.
This removes a common blocker during installation, upgrade and onboarding, especially in large or slow environments where a Diagnostic can take several minutes. Other administrators can also see that a Diagnostic is in progress, and a running Diagnostic is picked up automatically if you open it from another tab. If a new run fails, the CMS keeps showing its last successful result.
Deleting many tasks at once now runs in the background, so the task list stays responsive.
Obsolete task data is cleaned up safely, which keeps the task list fast as volumes grow, and minimal logging lets you confirm that deletions are happening as expected.
Deleting large volumes of 360Eyes snapshots now runs as a background operation in the Admin Console, with a "Deleting" status so you can follow progress. Snapshots are removed in smaller committed batches rather than one large transaction, which protects database stability.
This applies to both 360Eyes for SAP BusinessObjects and 360Eyes for SAP Data Services.
When a scheduled task failed and retried, the retry was treated as a new request. It could end up behind lower priority tasks that had become eligible in the meantime. A new "Prioritize Retry" option in the task scheduling options aligns the retry's logical start time with the original task, so its original priority is preserved.
This applies to every task in the platform. It is especially useful for 360Cast, where documents need to be distributed in a particular order.
You can now configure Oracle database connections using native or centrally managed Oracle mechanisms such as tnsnames.ora, instead of entering a JDBC URL by hand.
This reduces configuration drift and maintenance effort, and preserves Oracle's built-in failover behaviour.
Tasks could previously be created with a SAML connection but not with an Active Directory connection, because SAP BusinessObjects Trusted Authentication was only enabled with SAML.
360Suite now supports Trusted Authentication when AD authentication is used, so you can create tasks with an AD connection.
The 360Eyes_CMS.unx universe now contains audit dimensions for each object kind (Folder, AppFolder, Event, Access Level, Universe and so on).
You can use these dimensions to build audit reports on each type of object in your SAP BusinessObjects environment.
Value usage now includes the Query Objects and Variables used inside chart (Visualization) components of SAP BusinessObjects reports. Previously these were ignored, because only the element name was captured and not its content.
Usage counts now better reflect reality, which makes impact analysis and governance more reliable.
The SQL parser can now extract table and column names from MultipleFlows queries, where each query returns different columns. This widens the range of Data Provider queries 360Eyes can analyse.
Error and warning messages (date, type and message) from SAP Data Services job executions are now available directly in 360Eyes. When a job fails or completes with warnings, you can see the cause without switching to the SAP Data Services Management Console.
Logs are available once the 360Eyes extraction has run. Trace and monitor logs are not included.
You can now restore archived SAP BusinessObjects documents in bulk by providing a list of Document IDs in an administration task, as you do for other bulk operations in 360View. Previously, bulk archiving was possible through a template, but restoring meant selecting items one by one.
This is useful after a migration mistake or a change in retention policy. You can generate the ID list from the 360View Resource view or from 360Eyes, and restore hundreds or thousands of documents in a single task.
The standalone Archived Objects screen has been removed. You now manage archived content directly from the existing Resources views (Public Folders, Public Documents, Universes and so on).
Archived objects appear alongside the rest of your resources. You can search and filter them, see their original location, and unarchive the right ones without manual ID lookups.
The Next Run Time column in the Update Recurring Instance template is now applied when you import it. You can reschedule hundreds of recurring instances in one go instead of editing each schedule individually.
You can now view and update email delivery settings for recurring instances in bulk: the email body text, whether attachments are included, and the attachment naming convention.
This is available through the Export Recurring Instance documentation task and the Update Recurring Instance administration task.
You can now view, export and update server group assignments for recurring schedules in bulk, from the same two tasks. This helps when rebalancing load across server groups or setting up a migrated environment.
In 360View, the icon used to create a Documentation Generation task is now in the filter view.
SAP BusinessObjects and 360Plus can report a backup as successful even when it is empty. 360Plus now detects empty backups and retries automatically, up to three times, notifying you after each attempt and escalating if the failure persists.
This means a backup you rely on for restoration or audit is far less likely to turn out to be empty.
360Suite permissions now cover universe operations independently: UNV to UNX conversion, MSU to SSU conversion, universe import, export and deletion.
You can give migration teams only the operations they need, which supports least privilege and removes the administrator bottleneck during migration projects.
In Guided WebI Repoint, documents that could not be repointed previously showed a generic "0/x" ratio. The Documents Content step now shows the specific reason for each unmatched data provider, such as an unsupported source or a missing mapping.
You can tell configuration issues from technical limitations without opening each document.
▪ Tomcat 11 and Java 21
360Suite now ships with Tomcat 11.0.26 and Java 21.0.12.1+1. Impact: updating from Tomcat 10 to Tomcat 11 means you will need to reconfigure SSL, the keystore, the truststore and any customised Java options for Tomcat.
▪ Support for RHEL 10
360Suite can now be deployed on Red Hat Enterprise Linux 10, running on Apache Tomcat 11 and Java 21.
▪ Oracle 23ai (and 26ai) compatibility
360Suite is now compatible with Oracle Database 23ai (and 26ai) across all databases it manages: the application, audit, 360Eyes for SAP BusinessObjects and 360Eyes for SAP Data Services databases. This also covers Data Provider Testing and 360Cast destination lists.
▪ PostgreSQL 18.4 for new installations
For new installations that choose the embedded database, the installer now ships PostgreSQL 18.4. The Product Availability Matrix has been updated accordingly.
▪ Scrollable SAP BusinessObjects event selector
The event selection dropdown now has a maximum height, internal scrolling and a sticky search bar, so it no longer pushes the rest of the form out of view in environments with many events.
▪ Large environment pop-up only appears when creating a 360Eyes task
The pop-up shown when the CMS Diagnostic identifies a large SAP BusinessObjects environment now appears only when you create a new 360Eyes task, not when you update an existing one.
▪ Tab completion for folder paths in the Linux installer
You can now use the Tab key to autocomplete folder paths when running the installer on Linux.
▪ New JOB_EXECUTION_ID column in EYE_DS_JOB_EXECUTION_LOG
The EYE_DS_JOB_EXECUTION_LOG table now has a JOB_EXECUTION_ID column that corresponds to EYE_DS_JOB_EXECUTION.EYE_ID, so you can join the two tables in SQL.
▪ "Email" accepted as a destination type for recurring instances
When updating recurring instances, you can now use the simpler value "Email" as a destination type, alongside the existing "Email recipients".
▪ Clearer unarchive confirmation
The unarchive confirmation dialog now offers a "Restore" option instead of a red "Delete" button and trash icon.
▪ Length validation on text fields
Text fields in 360Suite now validate the length of what you enter. This follows the Hibernate migration in 2026.1, after which overly long entries could be truncated silently, or rejected with an error on some databases.
▪ Stronger encryption for stored secrets
Application encryption has moved from 128-bit to 256-bit AES. Existing encrypted data remains readable and is migrated, and rolling back to the previous version keeps your data accessible.
▪ Third-party library updates
Several third-party libraries have been updated to address known vulnerabilities.
▪ Stronger session protection
Session handling has been hardened at sign-in and when accessing the administration panel.
▪ Tomcat hardening
The Tomcat network shutdown port is now disabled, so the application can only be stopped through standard service management.
▪ Tighter validation and access control in 360Cast and 360Bind
Access control and input validation have been strengthened in 360Bind and in 360Cast destination lists. SQL-based destination lists now accept read-only queries only, and destination list names can no longer contain angle brackets.
▪ Unable to install a second 360Suite on the same Linux machine
High impact · P360SUITE-12686
Description: Running the installer on a Linux machine that already had 360Suite installed caused the setup to crash when choosing to install a new application. You can now install another 360Suite on the same machine, for example for a different SAP BusinessObjects version.
▪ 360Cast failed destinations not kept after a retry ends in error
Medium impact · P360SUITE-12784
Description: When a retry of a 360Cast task ended in error, the failed destinations were not retained, so the next retry attempted every destination again, including those that had already succeeded. Retries now resume where the task left off.
▪ 360Eyes CMS job drops "Other" document kinds after the first batch
Medium impact · P360SUITE-12780
Description: When extracting documents with all document kinds selected, a 360Eyes CMS job included the "Other" kinds in the first batch only. Documents of those kinds, such as shortcuts, were missing from later batches. All selected kinds are now extracted in every batch.
▪ Task sharing not read and saved correctly
Medium impact · P360SUITE-12770
Description: Task sharing permissions were not always read and saved correctly, so some explicit sharing settings appeared empty. This has been corrected.
▪ Repoint data provider export fails for some documents
Medium impact · P360SUITE-12746
Description: Exporting data providers or running a Repoint task could fail with a "Query plan does not exist" error on documents that have no query plan. These documents are now handled without error.
▪ Data left in the database after deleting 360Eyes for SAP BusinessObjects snapshots
Low impact · P360SUITE-12782
Description: After deleting snapshots from the Admin Console, some related records remained in the database. They are now removed with the snapshot.
▪ 360Plus documentation shows First and Last Backup dates reversed
Low impact · P360SUITE-12768
Description: In the documentation generated for a backup repository, the First Backup and Last Backup columns were swapped. This has been corrected.
▪ 360View Documentation Task API does not match the task's exports list
Low impact · P360SUITE-12761
Description: A documentation task created through the API could appear in the interface as having a missing export that had to be re-imported, because the API accepted an export type that does not exist in the product. The API now aligns with the exports available in the interface.
▪ 360View "User Groups and Users" export is incomplete
Low impact · P360SUITE-12743
Description: The Excel export listed only one group membership per user, so users belonging to several groups were missing from some of them. Sub-groups and direct child users could also be missing. The export now lists all memberships.
▪ Watcher monitoring graph shows a timeline extending into the future
Low impact · P360SUITE-12742
Description: When selecting a time range such as 24 hours, 7 days or 30 days, the graph displayed a timeline running into the future instead of showing historical data up to now. This has been corrected.
▪ 360Vers Security Lock user settings not saved correctly
Low impact · P360SUITE-12729
Description: In Object Mode, "Use Security Lock for Draft Actions" was disabled again after a page refresh or reconnection. In Package Mode, a removed Security Lock user reappeared. Both settings are now retained.
▪ 360Vers_Edit permission not removed from Administrator after check in
Low impact · P360SUITE-12727
Description: After checking out and then checking in a document in a package, the 360Vers_Edit permission added to the Administrator was not removed. It is now removed on check in.
▪ 360Eyes CMS_DOCUMENT columns not filled correctly
Low impact · P360SUITE-12723
Description: In the CMS_DOCUMENT table, the NEXT_RUN_TIME and IS_LAST_INSTANCE columns received the wrong values during document extraction. Both now contain the correct values.
▪ Data Provider Testing Validation Report missing rule counts and values
Low impact · P360SUITE-12712
Description: The Validation Report no longer showed the number of rules passed, and the Current and Expected values were empty for all rules. The report now displays them again.
▪ Unable to rename SQL Queries and SQL Connections
Low impact · P360SUITE-12711
Description: Changing the title of a SQL Query in Data Provider Testing or a SQL Connection in 360Cast was not saved, and no error was shown. Titles can now be updated.
▪ MySQL update failure with long task notifications
Low impact · P360SUITE-12702
Description: On MySQL repositories, updating 360Suite could fail when task notification titles or content exceeded 255 characters. The update now completes successfully.
▪ 360Vers replication can stay stuck in the interface
Low impact · P360SUITE-12623
Description: During large replications, progress could stall in the interface. Replications now progress correctly.
▪ SLA ignores custom Java memory settings
Low impact · P360SUITE-12476
Description: The SLA always started with the default 1 GB of Java memory, even when a different Xmx value was configured for the daemon. It now starts with the value you set, with a 2 GB minimum by default.
