Thursday, April 14, 2022

PTF Chrome Recorder

PeopleSoft Test Framework now records with Google Chrome! As of PeopleTools 8.59.07, Google Chrome replaces Internet Explorer 11 as the PTF recorder. This is great news considering Internet Explorer 11 retires from most Windows operating systems on June 15th, 2022. We took the new recorder for a test drive and have some findings to share with you. Check it out on our YouTube channel.

Be sure to subscribe to our channel so you don't miss future updates!

The biggest changes seem to be the replacement of the "always-on-top" recorder with a side window and a right-click pop-up menu.

Are you ready for June 15th? Details about the new PTF recorder are available in My Oracle Support document 2834568.1. At this time, Oracle plans to backport the Chrome recorder to 8.58.18. The document also shares details about potentially recording with the Edge browser in a future PeopleTools release.

What are customers saying? If your site disables Chrome extension installation, then you may experience challenges with the new Chrome recorder. It appears to self-install and run when launching the PTF recorder. You may find limited details about the Chrome extension issue in MOS doc 2648652.1.

With Event Mapping, Drop Zones, and other customization isolation solutions, PTF is more important than ever! Since we no longer customize directly, compare reports don't identify potential impacts. PTF regression tests are how modern PeopleSoft developers locate isolated customizations issues. Are you ready to learn more? Check out our live and recorded PTF courses online! Do you have a team you would like to train? Contact us with the details, and let's get something scheduled.

Thursday, March 17, 2022

Announcing PeopleSoft Fluid Day 2022!

Announcing PeopleSoft Fluid Day 2022 with all new Content! Join us online Thursday, May 19th for a full-day PeopleSoft education experience. Filled with Fluid development tips and best practices, we designed this opportunity to help you build better solutions faster. Space is limited so register now!

Register Now!

With the rapid pace of change in the IT industry, it is imperative that we keep our skills sharp. That is why I'm inviting you to reserve May 19th, 2022 to sharpen your PeopleSoft skills so you can develop better solutions faster and with less effort. Save time and money while increasing customer satisfaction by learning new techniques for building intuitive, mobile and desktop-friendly solutions. Learn how to use responsive and adaptive design to make the best use of screen real estate regardless of device type. Discover new ways to present information that communicates effectively with our users. Reduce the amount of time spent training users by creating intuitive experiences.

Here are some of the topics we will cover:

Fluid Page Design

  • Experience the key development differences between Classic and Fluid
  • Learn adaptive versus responsive design techniques
  • Understand Fluid Search Strategies
  • Leverage the PeopleSoft Fluid style library to create solutions without writing CSS.

Extending Oracle-delivered Solutions

At Fluid Day 2022, we will show you some fantastic examples of using Drop Zones and Event Mapping to isolate customizations.

Testing Strategies

Learn strategies for testing mobile and desktop solutions. With Drop Zones and Event Mapping, regression testing is more important than ever!

JavaScript and CSS

PeopleSoft wrote all the JavaScript and CSS required to build Fluid solutions, which means you don't have to write your own! We'll show you how to leverage Oracle's web assets. If you want to write your own, this session will give you some great ideas. We have examples that show you how to incorporate custom CSS and JavaScript into your Fluid designs.

Data Visualizations

A modern, intuitive user experience is an experience that communicates effectively. Learn simple CSS and JavaScript techniques to build an effective user experience.


Register now to reserve your seat for this dynamic one-day event on Thursday, May 19th. Registrants receive 60-days access to the recording, a copy of the Q&A roster, and sample code downloads.

Take advantage of this opportunity for only $447 per person. If you have a group of 10 or more, contact us at info@jsmpros.com for a quantity discount.

Register Now!

Thursday, March 03, 2022

A Simple Classic to Fluid Conversion

Oracle published a fantastic document describing how Oracle converted from Classic to Fluid. This very educational document is available at Doc ID 1984833.1. Oracle's solution makes sense for Oracle because it offers customers a choice: migrate to Fluid or stay Classic. As customers, do we need to offer that same flexibility? If so, then Oracle's approach is fantastic. I find most customers are either Fluid or Classic (or some derivative thereof), and when we convert a component to Fluid, it stays Fluid. We don't, for example, have part of an organization using a Classic version while another part of the organization uses the upgraded Fluid version. With that in mind, we developed a simpler approach to Fluid conversion: the in-place conversion. This stands in contrast to the clone-and-recreate approach. We put together a playlist with several videos describing our approach:

Be sure to subscribe to our channel so you don't miss future updates!

Want to learn more? Check out our vast Fluid training library, including recorded and live virtual events, online!

Wednesday, February 16, 2022

Where is that Content Reference?

New user 'X' needs access to 'Y.' Piece of cake, right? At least it was in Classic. The entire PeopleSoft navigation model stems from Content References. The classic "Navigator" and bread-crumb menus rendered the "Structure and Content" hierarchy. Finding content references under the classic model was trivial because the online visual rendering matched the "Structure and Content" portal registry hierarchical model. After finding a Content Reference, we could review the menu/component combination as well as existing permission lists to derive a solution.

What about Fluid? Most Fluid components exist somewhere in "Structure and Content." The question is, "Where?" The Fluid navigation model consists of homepages, dashboards, tiles, navigation collections, activity guides, and WorkCenters. And we can add any Content Reference to any one of these definitions. There is no structure. We use two tools to help us find Content References:

  1. Enterprise Components > Find Object Navigation
  2. SQL
If you know the menu/component combination or the CREF ID, you can look up the path using Enterprise Components > Find Object navigation. This is very helpful.

Unfortunately, many Fluid content references share the same component, a framework component such as PT_FLDASHBOARD or PT_AGSTARTPAGE_NUI. Everyone has access to these components. Let's consider the Personal Details tile on the HCM Employee Self-Service homepage. The menu/component combination is exactly the same as Payroll. Both use a framework component. What differentiates one tile from the next is the additional URL parameters. So we put together a SQL statement to help us locate content references by URL fragment. The following SQL is Oracle-specific. Notice the URL in the WHERE clause. Replace that URL with your own. Since this SQL uses regular expressions to filter CLOB data, be sure to regex escape special characters.

There is one other way to find a CREF ID. If the target is a Fluid Dashboard, then you may visit PeopleTools > Portal > Dashboards > Manage Dashboard Pages. The properties link shows both the parent folder and the dashboard's CREF ID.

Are you interested in learning more about PeopleSoft Fluid administration and development? Check out our website for live virtual and on-demand recorded PeopleSoft Fluid training.

Tuesday, January 11, 2022

Hiding Tiles

At a conference several years ago, a friend and I were discussing PeopleSoft Fluid. Fluid was new at the time, so my friend was sharing his vision for making Fluid better. One of his ideas was to dynamically hide tiles. For example, if an employee has an Onboarding event, show the onboarding tile. Likewise, if a student has holds or "To Do's," then show a tile. I thought this was a fantastic idea and came up with a few ways to make this happen. If you are using PeopleTools 8.54 through 8.58, here are some options:

  • Use Dynamic Role Rules to add/remove a role that grants access to the target tile. This is the easiest approach and the most adopted method for dynamic access to tiles. For this to work properly, a tile should be marked as required.
  • Use Event Mapping to hide a tile. The PeopleSoft tile homepage is a cleverly formatted Fluid DIV Grid. Each tile represents one row in a grid. Through PageActivate Event Mapping, we can selectively show or hide rows by setting a row's Visible property. As you iterate over the list of rows, evaluate criteria and set the row's visbility accordingly.

What about 8.59? Why did I recommend these strategies for 8.58 and earlier and not 8.59? There is a new PeopleTools 8.59 feature that lets you configure a tile's visibility. Tammy Boyles from Oracle Product Management shared about how HCM uses this new feature last month. Here are the steps:

  1. Create an App Class that extends PTGP_APPCLASS_TILE:API:TileAppFilter.
  2. Put your conditional logic in the IsTileVisible method, returning True to show or False to hide.
  3. Add the content reference attribute TILEAPPFILTER to your tile's content reference.
  4. Open the appropriate homepage content reference and mark the tile as required.

Once you configure a TILEAPPFILTER attribute, the tile will no longer show in the "Personalize Homepage" list of available tiles, so users may no longer add or remove this tile. Therefore, a tile that has a TILEAPPFILTER attribute must be marked as required.

Do you want to see an example? Join us on November 18th, 2021 for Configuration Day 2021 to see this and many other new 8.59 features in action.

At JSMpros, we teach PeopleTools topics like this every week. In fact, this specific topic is part of our continuously updated Configure, Don't Customize course. Be sure to check out our website for more information about this and many other PeopleTools topics.

Wednesday, December 01, 2021

Campus Solutions: Which Navigation Collection?

When Campus Solutions built their business process-based navigation, they did something interesting: they wrapped Navigation Collections in the Master/Detail Framework. Rather than hard-code a list of links (like the original HCM Personal Details), Campus Solutions chose Navigation Collections. The flexibility is incredible. This design decision allows you and I to add new links to Campus business processes without modifying delivered code (unlike the original HCM solution).

Personal Details Master/Detail component

That's fantastic! But here is the problem: which navigation collection should you update? Some of them are easy to find because they have the same label as the tile itself. But others don't. Fortunately, the navigation collection name is in the URL:

&scname=CS_SSR_ACADEMIC_RECORDS_FL

Wait... did I say the Navigation Collection name? I apologize. There seems to be some confusion about the "name." When creating a Navigation Collection, the Navigation Collection tool asks for a name. The "name" we supply is actually a label. PeopleSoft dynamically generates the name from our label. Since a Navigation Collection is a Portal Registry folder, the real "name" is the CREF Folder ID. So in the example listed above, the CREF ID is CS_SSR_ACADEMIC_RECORDS_FL, but we don't know the label. To maintain the Navigation Collection, we must know the Content Reference's label. The good news is we can find the label with a simple query. The SQL to find the label for the example above would be:

SELECT PORTAL_LABEL
  FROM PSPRSMDEFN
 WHERE PORTAL_PRNTOBJNAME = 'CO_NAVIGATION_COLLECTIONS'
   AND PORTAL_NAME = 'EMPLOYEE'
   AND PORTAL_OBJNAME = 'CS_SSR_ACADEMIC_RECORDS_FL'

Fluid is PeopleSoft's mobile and modern rendering engine. Through a few simple techniques, we can show you how to build better Fluid solutions faster. Are you interested in learning more? Check out our Fluid course offerings at jsmpros.com.

Tuesday, November 09, 2021

PeopleTools 8.59 new feature: Independent "AddTo" Security

Imagine having a PeopleSoft Favorites feature and no way to add Favorites. After 8.54, many customers found themselves in this situation. Fluid introduced "Add to Homepage" and "Add to Navbar" as fantastic personalization options. Our users love them. For example, I can "pin" my favorite classic components to my homepage for quick and easy access. For power users, this is terrific! And for self-service users? Every component a self-service user visits should already be represented through a Fluid homepage tile. For the casual self-service user, offering an "Add to Homepage" feature often causes more problems than it solves. With that in mind, customers often disable the "AddTo*" feature for self-service users. My friend Simon Chiu explains how in Section Four of his post PeopleTools 8.55 Features: How to Deploy Homepages, Tiles and Branding. From 8.54 to 8.58, disabling Add to Homepage also disables Add to Favorites, which is unfortunate. Favorites are the domain of the user. Nobody questions a user's favorites. Our friend Sasank Vemana shared a solution to "decouple" the AddTo options so we could disable these features independently. Likewise, My Oracle Support published Doc ID 2143709.1, showing how to customize the AddTo* features so customers can remove Add to Homepage while keeping Add to Favorites. Unfortunately, through 8.58, retaining Add to Favorites requires a customization.

What about PeopleTools 8.59? Oracle basically applied this customization to the base PeopleTools code. This feature is now built into PeopleTools. With PeopleTools 8.59, PeopleSoft added the following new roles:

  • DisableAddToFavorites
  • DisableAddToHomepage
  • DisableAddToNavBar

To remove access to Add to Homepage, assign the role DisableAddToHomepage.

Here are a couple of interesting observations of this new feature. First, access seems logically inverted. To remove access, you must assign a role. Normally, we assign roles to grant access. In this case, we assign a role to remove access. Second, we noticed user PS has these roles in the latest HCM PUM, which means out of the box, user PS can no longer add to favorites, homepages, or Navbar.

What are your observations of this new feature? Share your thoughts in the comments. We would love to hear!

Are you interested in learning more about PeopleSoft security or fluid? Check out our latest course offerings at https://www.jsmpros.com/courses/ and events at https://www.jsmpros.com/events/.