We're still working on the backend and some of the styling for this. Here is a nice demo on conditional formatting as generally applied.

Thanks. There is currently no official feature for css style revisions/styles/skinning, but there may be are other methods if that's what your thinking.

What are you thinking on coloring, might I ask?

Visibility to swimlanes, contents of swimlanes, and even the whole page would be based on roles / ACLs.

We're considering something like this as an option for the factory FDI experience. This example would be for a Finance Executive and you see the factory content broken out into functional "swimlanes" - like Accounting or Payables. This page could be customizable (or not) and would provide a starting point for users.…

This release was unfortunately delayed but actually starts rolling out today (11/26/24) @OAwiz-Oracle. As it rolls out across the fleet those HCM legacy dashboards (and the CX ones, for the record), will be disappearing.

This is a good idea @Mernisa ! We're looking into this and hope to deliver a generalized capability like this. I'll need to do a little more work before we have a timeline, but it likely won't be immediate. Your summary of he requirements is a good one and pretty much matches our plans. In the interim we do have the…

Thanks for the additional ideas, Josh. Write-back and taking actions based on insights is a current emphasis. I'll pass these notes on to the OAC folks too.

The above comments are true for OTBI but not for FAW/FDI. There is a template feature being considered that would be able to apply a predefined color palette across a number of reporting elements but it would not be css directly. What is the css intended to be used for?

Additionally, the Personalization feature in the Jan 2024 release of OAC (which will be present in FAW/FDI) will persist the last-selected filter value for a user across sessions.

We're working on a plan to do this in a productized was (addressing security, etc.). There are some hacks with iframes but these are not solid integration. Can provide an update on timing when that's known.

Insofar as Cards have been re-implemented as Workbook composite Viz, is this consistency issue resolved?

KPIs have been deprecated but this critique might apply to Key Metrics too. This may or may not still be an issue as Key Metrics are grouped under the dataset or Subject Area they live in. So numbers are smaller and a categorization is implied. Should we log this again for Key Metrics?

Clarifying this is in the Classic Homepage view of the catalog for BIP-related artifacts.

Insofar as Decks have now been re-implemented as Workbooks, the "Present" mode would be an optimal feature to consider for Briefing Book capabilities.

Insofar as Cards are now implemented as workbook composite visualizations, these can be turned off by removing any columns from the Tile section in the panel.

The FAW Cards and Decks have been deprecated but we have a number of projects in the works to provide integration of FAW content (with security) into Fusion screens. Those Card and Decks concepts have been re-implemented as workbook concepts which will be part of the integration plan. I can update on timing as we learn…

Factory content will likely remain read-only, but a new personalization feature allows users to not need to redo filters across sessions.

We're looking at enabling this for FAW/FDI. Not in-app but still useful,. Thoughts?

This appears to be solved?