This week, Kyle and Dan discuss SSH port knocking, a possible MOS API for Weblogic patching, and the excellent DMSViewer tools. Dan also shares some thoughts on the Unified Compare Reports in PeopleTools 8.56+.
This week on the podcast, Kyle discusses how he kept the Supplier Portal in Classic while going Fluid Nav for the rest of the application, Dan shares some Related Content feedback and some App Designer filtering tips.
- Don’t be afraid of Makefiles @ 7:00
- MOS Documents in Google results? @ 13:30
- Classic on my Supplier Portal @ 16:00
- Related Content Follow-up @ 32:00
- Security Deployment with Custom Security @ 37:45
- PUM and Translations @ 43:00
- Mobile-friendly Tool Tips @ 46:00
- Beyond Compare and YAML @ 49:00
- App Designer Filtering @ 53:00
This week on the podcast, Kyle and Dan revisit Fluid Navigation and why they are fans of the new navigation model. Kyle shares his experiences working with the DPK and his method for managing the YAML and Puppet files on servers. Dan shares a top-notch “Dad Joke”.
- Location-based Event Mapping @ 1:30
- Classic UI for Admin’s/Power Users @ 2:45
- Linked-in Style Notifications @ 7:30
- SQL Turns 43 @ 11:15
- SQL Notebook @ 13:00
- Creating patch tarballs for the DPK @ 14:00
- Kyle’s DPK Experience @ 22:00
- DPKFiles Setup @ 28:45
- How do you do it? – Dad Joke Style @ 45:45
- Embracing Fluid Navigation @ 46:45
I’m happy to release a set of stylesheets for PeopleTools 8.55 for everyone to use. The stylesheets are based on the
TANGERINE theme (8.53 look and feel), so they won’t work with Fluid pages. For people who are using the Classic look, these stylesheets are a great way to ensure your users know which environment they are using.
I’ve used stylesheets for pre-8.50 environments from Duncan Davies in the past and built custom stylesheets for 8.53. But with the Branding Framework in 8.54 and 8.55, using custom styles are even easier. Thanks to Sasank Vemana for his great posts on using the Branding Framework as well. I used his posts to build these stylesheets.
There are six styles in the project. The colors (except the purple theme) are based on the Bootstrap default theme.
Use the colors however you want, but the list below is how I’m using the colors:
- DEV1 – Green
- DEV2 – Light Blue
- DEV3 – Purple
- TST – Red
- QA/UAT – Grey
- SBX (Sandbox and Nightly Refresh) – Yellow
Load Stylesheets and Branding Data
You can apply the stylesheets three ways: manually load the project with App Designer and Data Mover, apply a change package with Change Assistant, or follow Sasank’s post and use the stylesheets from the GitHub repository.
Download the change package,
updIO_STYLES_855.zip, from the GitHub repository. Extract the
updIO_STYLES_855.zip file to get the project and scripts. In App Designer, copy the project
IO_STYLES_855 from the change package folder into the target database.
ptbr_io_theme.dat file using Data Mover and the script
updateSystemBranding.sql script to update the Branding System Options and insert the
Download the change package,
updIO_STYLES_855.zip, from the GitHub repository. Apply the change package against any environment where you want to use the stylesheets. (You’ll need to use the “Apply Updates” mode in newer Change Assistant versions). The change package will import the
IO_STYLES_855 project, import the Branding Framework theme data, and update System Branding Options.
If you want to use the styles in your non-production environments, you can import the project and Branding Framework setup and theme data into your production database. Skip the SQL script to update the System Branding Options. Add the SQL commands from the Change Package script
updateSystemBranding.sql into your refresh scripts.
After you load the project and run the scripts, Classic pages will show up with the new stylesheest. If you are on 8.55 and want to use the Classic homepage, you’ll need to run the SQL below:
update psuseroptndefn set user_option_value = 'C' where optn_category_lvl = 'PPTL' and useroptn in ('HPPC', 'HPTABLET');
To change the header colors, change the Additional Stylesheet on the “PeopleTools > Portal > Branding > Branding System Options” page.
There are two ways you can replace the logo with your own:
- Replace the
IO_LOGOfile under “PeopleTools > Portal > Branding > Branding Objects > Images”
- Upload your logo as a new image and replace the
IO_LOGOreference in the
I have created a GitHub project with the styleets used in the project. If you want to add any changes or suggest improvments, please send them in or contribute to the GitHub repository.
In a past post, I highlighted the new default navigation options with PeopleTools 8.55. For some organizations, the new Fluid Navigation might be a large change and are not ready to make the jump to Fluid. But, there is a way to keep the Classic Drop-Down menu style in PeopleTools 8.55. If you switch the System Default Theme back to the 8.54 or 8.53 stylesheets, you can use the Drop-Down menu.
1. PeopleTools > Portal > Branding > Branding System Options
DEFAULT_THEME_TANGERINE (8.53 Look-and-Feel) or
DEFAULT_THEME_TANGERINE_ALT (8.54 Look-and-Feel). You need to log out and back in to see the changes (I had to clear some browser cache too).
The screenshot above is from HR 9.2 Image 16 after I updated the system theme to
DEFAULT_THEME_TANGERINE. One thing to note if you make this change, the default homepage is still the Fluid Homepage when you log in. The “Assign Themes” let’s you change the user homepage based on Role or Permission List if you want to make that change.