PeopleSoft Enterprise

I am very interested in component based branding, but have not had the opportunity to touch it.

Question: did you try accessing the /psc/ URL so that you are ONLY seeing assets for the component?

I have been experimenting with Branding in PeopleTools 8.54 recently. I wrote some posts based on my testing (see... Part 1, Part 2, Part 3).

I just tried applying component branding to a test component and I do see my stylesheet being included when I access the component.

What are you trying to do? Are you trying to override an existing style sheet on the component/page? Are you trying to inject component/page specific js?

Here is my example where I am overriding the style class PSEDITBOXLABEL specific to my component (this style is applied only to my component and the rest of the components are not affected):

Custom Style Sheet:

Component Branding:

Component:

Notice: The Edit Box Label color is now red.

Yup. No luck.

This is exactly what I am trying to accomplish. But the stylesheet I'm attaching to the component is not getting loaded for some reason. Is there additional configuration that needs to be performed to enable this feature?

I did not have to do anything additional (just whatever I have in the screenshots). But if you have caching enabled at the web profile level, it might help to restart your web server and clear the cache. Let us know if you are still experiencing issues.

It was the cache. Thanks so much!

Glad to hear that it is working now!

Well, it looks like I may have spoken too soon... It seems like component based branding works for some components but not others, even after clearing the cache. For example, in the FSCM demo image I can brand the "CHANGE_PASSWORD" component, but not the "REQUISITIONS" one. Any thoughts on why this may be?

Hi William - Yes, I noticed the same with FSCM. And I am not seeing the style sheet when I debug on the browser so it is not as if another style is overriding the custom style (which would have been easier to fix).

I will dig in a bit more and see if I find the problem.

William - This might be a bit premature but from what I am seeing, it appears that any component with search processing seems to be affected. If the component is self-service style, it seems to work.

Is that consistent with what you are seeing? I will let you know if I find out more. Thanks!

Yup, that seems to be the source of the issue.

William - Thanks for the information! Good to know that it is a bug.

@Sasank, you should file a ticket in global support to get on the list of people experiencing this problem. The resolution time frame and release is often dependent on demand.

Jim - Sure. I will do that (it has been an item on my to-do list). I have not found the need to employ this feature in any use cases yet, I was trying to help answer William's question with a proof of concept and in the process find out how it works!

Will definitely raise a SR with Oracle (more the merrier) and hopefully we will have a fix sooner. Thanks!

FYI, this also breaks in modal windows, even if it was functioning in a component without a search record.