Oracle Communities

Oracle Analytics and AI

Child Item

OAS 7.6 2024 skin customizations

We have been using Skyros as our skin since we started using OBIEE/OAS. Since that will no longer be available in this version, can we simply copy the master.css contents for Skyros to the custom.css file to still get the same look? We have not really done much in the master.css files, so not sure of what will work and what won't.

Going from Skyros to Alta or even Redwood is a big albeit cosmetic change for our users. If looks like font sizes/styles are different and we haven't even started looking at what our custom formatting looks like when exported with the Alta style.

Find more posts tagged with

Accepted answers

Gianni Ceresa

You would probably have more chances by building a full custom style/skin, and not mixing up things in the CSS.

As Federico mentioned, most styles/skins work by inheritance: there is a base one on top of which some customization are deployed.

If you want Skyros, then you should create a full skin/style for Skyros by coping the full style from your older version to the new one.

The issue is that the code of the product could change over time, therefore your copied style maybe doesn't apply as before because some tags or attributes changed in the code, and you will need to adjust your custom style/skin for that.

If you are still using Skyros in a recent OAS release, then it will just work fine. If you are still on 12c and now look at moving to OAS 7.6 it could be a bit more challenging.

On the positive side: there should be only small changes required at best. "classic" (/analytics) doesn't change much/at all in OAS. And custom styles/skins do not apply to DV (which is the one changing at every release of OAS).

Try, but deploy the full style and not just a CSS.

All comments

Federico Venturin - Oracle

Hi @Stacey D ,

I didn't try the approach you are suggesting, but I'm pretty sure that it will not work as expected. The styles specified in the custom.css file are applied on the top of the base style (which should be either Alta or Redwood), which is expected to be different from Skyros' base style.

Gianni Ceresa

You would probably have more chances by building a full custom style/skin, and not mixing up things in the CSS.

As Federico mentioned, most styles/skins work by inheritance: there is a base one on top of which some customization are deployed.

If you want Skyros, then you should create a full skin/style for Skyros by coping the full style from your older version to the new one.

If you are still using Skyros in a recent OAS release, then it will just work fine. If you are still on 12c and now look at moving to OAS 7.6 it could be a bit more challenging.

Try, but deploy the full style and not just a CSS.

Stacey D

Thanks Gianni. We are currently on OAS 7.4 and have Skyros set in the instance config file and everything is fine.

Just to make sure I understand what you are suggesting…I should take a copy of the Skyros and s_Skyros files and basically just save them in 7.6 bicustom.ear then update the instanceconfig file to Skyros in the UI section?

Gianni Ceresa

Yes, that's the plan. Creating Skyros as a full style/skin, with all it's files, and deploy it as a custom style.

Because it doesn't exist anymore in 7.6, you will not really have issues (duplicate name etc.).

And from 7.4 to 7.6, I don't think you will need to adjust anything: it will just work fine. I'm not fully sure of the justification to remove the old styles from 7.6, it's maybe just a cleanup process, because the UI didn't really change in what is impacted by a style/skin.

It's maybe just a way to start moving people into RedWood and have a more unified "experience" (most Oracle cloud products are going full RedWood).

Steve F-2

To add, custom theme feature is coming to the /dv side in an upcoming OAC update; therefore, you can potentially expect it in the next OAS release (OAS 2025).

{safe harbor statement}