Skin Not Inherited on Custom ADF Taskflows Added By Extending WebCenter Portal Shared Libraries (Doc ID 1668790.1)

Last updated on AUGUST 08, 2024

Applies to:

Symptoms

Custom ADF Task Flows added to WebCenter Portal by Extending the WebCenter Portal Shared Libraries do not inherit the skin set in the Task Flows.
The skin is inherited correctly when running the Task Flows in the standalone ADF application, however when the Task Flows are consumed in WebCenter Portal, the skin is not inherited.

Changes

Steps to Reproduce:

1.  Create a custom application in JDeveloper with Some Task Flows.

2.  Create a skin.
For example, include some custom css styleClasses in the skin so you can apply the same in the task flows.

e.g.: portalSkin.css

4.  Run the application and confirm the skin is applied.
In this case the task flow should show the css styleClasses (e.g. red hyperlink and blue background in this case).

5.  Extend WebCenter Portal to add the Task Flows as shared libraries as indicated in the following document:

Oracle Fusion Middleware Developing Portals with Oracle WebCenter Portal and Oracle JDeveloper
11g Release 1 (11.1.1.8.3)
55 Developing Components for WebCenter Portal Using JDeveloper
55.2 Developing Task Flows, Data Controls, and Managed Beans for WebCenter Portal

6.  Consume the Task Flow in WebCenter Portal.
Here you should see the skin is not inherited in the Task Flow.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.