Here you will find information about:

• limitations,
• known issues,
• changes in the supported environments,
• any unexpected behvavior of Optimize (e.g due to a new feature)

New behavior of Optimize

With the introduction of the new collection and permission concept you might find the behavior of Optimize startling and thus the subsequent sections will guide you through the changes.

Collection Permissions & Private Reports

With Optimize 2.6.0 a resource permission system is introduced. This system provides private reports/dashboard entities in the Home section as well as the possibility to manage permissions on collection entity level in order to share it with other Optimize users.

This ultimately means that after the migration to Optimize 2.6.0 each user only sees the entities they originally created. This includes reports, dashboards as well as collections. In order for other users to be able to access those entities they need to be copied into a collection and view access to this new collection must be granted to other users.

Grant access to a private report

Given the scenario that the user john owns a report John's Report that user mary was used to access in Optimize 2.5.0 the user john can share this report in Optimize 2.6.0 with mary following these steps:

1. User john creates a collection named e.g. John's Share

   

2. User john grants user mary the viewer role on the collection John's Share

   

3. User john copies & moves the John's Report report to the John's Share collection

   

   

4. User mary will now see the Collection John's Share in her Home section of Optimize

   

Grant access to an existing collection

Given the scenario that the user john owns a collection John's Collection that user mary was used to access in Optimize 2.5.0, the user john can share this collection with mary in Optimize 2.6.0 granting user mary a permission role on that collection. Please refer to step 2 in Grant access to a private report.

Super User Role

You can now grant users Super User permissions, which allows them to bypasses the owner/collection permissions, enabling them to access all available entities. This can for example be useful if entities are owned by users that are not available anymore.

In order to grant a user Super User permissions see the Authentication & Security Section.

Known issues

Rebuild your Optimize plugins

With Optimize 2.6.0 the plugin system was overhauled. In order for your plugins to continue to work you have to rebuild them with the latest Optimize plugin artifact as an uber jar. Please refer to the updated plugin setup guide.

Misinterpreted cron expressions

The configuration of Optimize allows you to define when the history cleanup is triggered using Cron expression notation. However, the values are incorrectly interpreted in Optimize. For example, the historyCleanup.cronTrigger configuration has the default value 0 1 * * *, which should be 01:00 AM every day. Unfortunately, a bug causes this to be interpreted as every hour.

To fix this just use the spring cron expression notation. For instance, the default value for historyCleanup.cronTrigger would then be 0 0 1 * * *.