Release date:
Everyone from the Wiiisdom Team wishes you a happy new year 🎉!
Thank you for your continuous feedback and support. Here’s to another fantastic year of innovation and growth together!
💡 360Eyes has officially moved to 360Suite, and this release note will now contain everything, including 360Suite and 360Eyes.
⚠️ To have more information on what it means exactly for 360Eyes, please refer to this knowledge base
This updates contains some major changes, the most important is that we are now using Java 21 instead of the old Java 8. This means multiple things, but mostly that the application will not work on SAP BusinessObjects Tomcat, and in general versions older than Tomcat 10.
📆 We’re going back to a four releases a year schedule for 360Suite. The new provisional release dates are:
Full Documentation: https://support.wiiisdom.com/documentation
Download Site: https://support.wiiisdom.com/downloads
Of course, do get in touch if you need help with updating.
Contact us via your Customer Centre and Support Site: https://support.wiiisdom.com/
Java 8 had a long life, it's time to let it rest, and we also want to be ready as BI2025 should also move away from it.
Java 8 was also limiting our ability to achieve better performance and access the latest features available in newer versions.
After upgrading to Java 21, on our environments, we’ve observed a significant reduction in database deadlocks, particularly with Microsoft SQLServer.
However, this transition brings changes to our support capabilities. As mentioned above, 360Suite can no longer be installed on the outdated SAP BusinessObjects Tomcat. If you are using your own Tomcat server, you will need to upgrade to at least version 10.1.34.
In any case, the setup process will guide you through the available options. For more information, please refer to this knowledge base
Previously, our log generation lacked clarity and detailed information, making it difficult to interpret and analyze.
With the revamped log generation, users can now benefit from clearer, more informative logs that enhance understanding and efficiency.
The new logs are designed to be read with specialized software, significantly improving readability and usability.
If you want to read logs, head over this knowledge base to have more information.
This is a small example of what errors will look like, and what double clicking will allow you to do:
With 360Eyes and 360Eyes for SAP Data Services now integrated into 360Suite, monitoring upcoming tasks requires navigating multiple pages to get a clear overview.
To resolve this, we added the scheduling manager which simplifies this process by providing comprehensive insights into task statuses, including which tasks are late, failed, recurring, and more.
360Suite tasks have in real time logs. When implementing 360Eyes, we did not add this feature immediatly.
In the version 2024.3 we added them for 360Eyes for SAP BusinessObjects tasks.
In this release we added them for 360Eyes SAP For Data Services. You are now able to see what the task is doing in real time without having to download Tomcat Logs.
When using 360Eyes for SAP BusinessObjects in standalone, it was possible launch jobs thanks to a command prompt.
We don't have this possibility in 360Suite, but we are able to create tasks via an API. We added the possibility of doing so for 360Eyes for SAP BusinessObjects and 360Eyes for SAP Data Services.
To learn more about this and get a better understanding of the API, you can head over to the API documentation here.
360Suite tasks allow you to send notifications depending on how the task ends. This ensures you can confirm the task’s success or take action if it has a warning or has failed.
But until now, we were not able to let you know when a task started unless you went on 360Suite to see it. We have now added the possibility to send a notification when the task starts.
This will allow you to confirm the task has started and identify if it was delayed for any reason, without having to connect to 360Suite.
When creating a 360Cast Task or getting the link to a document in the Folder view, you can generate OpenDocument links to share with users. These links allow users to view the document directly inside SAP BusinessObjects.
Previously, the URL was automatically generated by 360Suite, which could cause issues if SAP BusinessObjects and 360Suite were on different servers. However, now you have the option to customize the URL, ensuring that the links work correctly for your users.
The 360Eyes SQL Parser is effective for most databases, but thanks to your feedback, we found that it had some issue with Google BigQuery.
We have now enhanced the SQL Parser to accurately parse data from Google BigQuery SQL queries.
When using the “Variable Usage Occurrence” feature, occurrences were not being fully extracted if the variable was used in a Merged Dimension.
The extraction process now includes these occurrences in the count and correctly extracts the value of the merged dimension to display the variable name.
When trying to link a document to its connection, we weren't able to link a document linked to a connection without a universe.
This meant that for connections such as FHSQL, BEx, and BW, it was impossible to see the link between the document and the connection. We are now fetching the link between them allowing you to gain a better understanding of your environment.
You now have access to two new dimension in the universe :
Job Execution in SAP Data Services may contain SQL Queries with a lot of information, which can be in the SELECT, FROM, WHERE, GROUP BY and ORDER BY tabs.
Up until now, we only fetched basic data, we are now extracting the properties from those tabs. This allows you to have a better understanding of what your jobs are doing, and how they are configured.
360Eyes for SAP BusinessObjects and 360Eyes for SAP Data Services may use a lot of database to run, considering the one needed to store the information, the audit database of SAP BusinessObjects, and the Local Repository of SAP Data Services.
We added the way to use an alias for each one instead of the URL in 2024.3, we now allow you to add an alias for the SAP Data Services Local Repository also to facilitate your task creation and management.
We implemented a new feature in 360Cast that will allow you to simulate running a task without actually sending results to your destinations.
This will ensure the configuration of the task and destination list is working as expected, this will also ensure that SAP BusinessObjects is able to generate the instances.
We recommend using this feature after every upgrade to make sure nothing changed. As it will allow you to be more confident in the data you are sending to your end users.
You now have this toggle at the bottom to choose whether or not to launch a simulation or a real task
Pro tip: Use this feature with the 360Cast Audit feature released in a previous release to document and analyze the results.
When doing frequent backup, purging them is also a good pratice. We provided a way to purge backup that were older than a certain date, which could be enough, but was not perfect, as you could need to keep old backup and only want to delete recent one, or from a specific time-range.
We have now added a way to delete backup inside a given time range, which will allow you to keep old backup, and still purge backups.
With our application increasing the number or database that can be used, either for the application data itself, or for the 360Eyes Database, the setup lacked a way of importing multiple JDBC drivers to allow you to use different databases. We have modified the setup to allow you to import multiple drivers. Even when the PostgreSQL database is selected.
360Suite allow you to make sure two documents have not changed between upgrades, but until now, it lacked a way to make sure the data the document is using is correct.
This means that you were not able to, let's say, verify that a user does not have access to data he shouldn't see, or even that there is no duplication in the data.
With Data Provider Testing, we allow you to verify this and much more, like verifying the number of rows is correct and so on.
To get more information on this feature, please reach your Wiiisdom contact.
▪ When creating 360Cast or 360Bind Task, the document list is now sorted by name.
▪ When initializing a 360Eyes environment, you are no longer required to import the 360Eyes biar to use 360Eyes on it.
▪ When installing 360Suite, the option to install PostgreSQL will now be unselected by default.
▪ We have added the support of Microsoft Azure SQL. Please refer to the PAM to get more information.
▪ We are deprecating the extraction of Crystal Reports and Webi Intelligence in the IA Job to avoid confusion, and duplication from other jobs.
▪ Tomcat version changed from 9.0.84 to 10.1.34
▪ Java version changed from 8u372-b07 to 21.0.5+11 LTS
▪ Data Provider Testing read max and min as String instead of Number (Impact: High)
Product: Data Provider Testing
Description: Data Provider Testing can use alphabetical comparison instead of number comparison for min and max.
ID: P360SUITE-11898
▪ Task sharing not taken into account when scheduling a documentation task (Impact: Medium)
Product: 360View
Description: Scheduled task documentation only takes into account the tasks of the user who launched the task
ID: P360SUITE-12024
▪ MSU check in audit BI readiness include Single source (Impact: Medium)
Product: Core Improvement
Description: MSU check in audit BI readiness include Single source Universes
ID: P360SUITE-11991
▪ Unable to run 360Cast with a complex prompt using Between operator (Impact: Medium)
Product: 360Cast
Description: Unable run 360Cast with a complex prompt using Between operator
ID: P360SUITE-11951
▪ In some case, comparison task with differences export can give NullPointerException (Impact: Medium)
Product: 360Bind
Description: In rare case, the comparison task with result sending enabled stop with unexpected error
ID: P360SUITE-11827
▪ CMS Job - Job Failure in including or excluding Specific Object IDs. (Impact: Medium)
Product: 360Eyes For SAP BusinessObjects
Description: The CMS job fails due to a critical error caused by incorrect parsing of Object IDs, where extra spaces are added, leading to a type conversion error. This issue occurs when including or excluding specific Object IDs in the job parameters.
ID: P360EYES-5409
▪ Eyes Database - The Connection is closed when 2 jobs are run simultaneously. (Impact: Medium)
Product: 360Eyes
Description: When running two parallel tasks with multiple 360Eyes jobs using the same database, the second job fails because the first job closes the database connection after updating the schema.
ID: P360EYES-5385
▪ Unable to reinstall 360Suite when the registry contains GBANDSMITH folder (Impact: Medium)
Product: Setup
Description: Installing 360Suite after an Uninstall may not work in rare case
ID: P360SUITE-11909
▪ Settings button in the watcher page redirect to a NullPointerException (Impact: Medium)
Product: 360Live
Description: Watcher graph configuration causes an error.
ID: P360SUITE-11920
▪ Two 360Cast export with the same filters do not reuse previous export. (Impact: Low)
Product: 360Cast
Description: When exporting two documents with the same filters, we do not reuse previous one if possible, resulting in longer processing time.
ID: P360SUITE-12015
▪ 360Cast detect wrong recipients if email start or end with space (Impact: Low)
Product: 360Cast
Description: 360Cast detect wrong recipients if the field contains multiples email separated with a space after the coma.
ID: P360SUITE-11990
▪ Rule deletion pop-up won't disappear (Impact: Low)
Product: Data Provider Testing
Description: The rule deletion confirmation pop-up does not disappear.
ID: P360SUITE-11917
▪ In rare case we can not do the backup post process for Oracle (Impact: Low)
Product: 360Plus
Description: In oracle, huge Backup task with ignore broken object policy can throw an exception at the end, visible in the logs.
ID: P360SUITE-11809
▪ Limiting the number of BOBJ user to deny the access to 360Suite doesn't display the right message (Impact: Low)
Product: Core Improvement
Description: When the license doesn’t allow the connection due to number of users in the CMS, the message doesn’t indicate the reason.
ID: P360SUITE-11945
▪ Task export do not use selection and export all tasks (Impact: Low)
Product: Core Improvement
Description: Task export do not use selection and export all tasks.
ID: P360SUITE-11928
▪ 360Bind task's detail overview doesn't render correctly the number of documents per batch (Impact: Low)
Product: 360Bind
Description: The 360Bind task overview displays a value for the split even if it is not activated.
ID: P360SUITE-12013
