Many PeopleSoft customers have multiple PeopleSoft applications. We often refer to this type of environment as a ‘cluster’. Customers have different types of clusters, some using the Interaction Hub to unify the cluster and some without the Hub. We are often asked how these are different. Should a customer use the Interaction Hub for clusters? Can you get by without it?
The scenario I’m describing in this post relates to PeopleTools 8.55 and it’s use with applications using the Fluid header (whether the content is Classic or Fluid).
This can be somewhat confusing because the PeopleSoft Interaction Hub was originally called the ‘PeopleSoft Enterprise Portal’, which was designed to be used as a traditional portal, aggregating content from multiple sources. People still often refer to that product as simply ‘The Portal’. The Interaction Hub still provides that traditional, aggregating functionality. However, PeopleSoft also uses the term ‘Portal System’ to mean more than just the Interaction Hub system connecting to content systems like HCM, FSCM, and Campus Solutions. In PeopleSoft, whatever system the user logs into first is considered to be acting as the Portal system. For example if Single Sign-On (SSO) is set up between HCM and Campus Solution and the user logs into the HCM system and from there access Campus solution then the HCM system acts as the Portal system.
Let’s look at a specific Example. In this scenario, the customer is NOT using the Interaction Hub, but they have PeopleSoft HCM and FSCM and have SSO set up for these applications. A user of this system logs into HCM and is presented with an HCM-based Employee Home Page. That home page contains a tile for FSCM content, and there is other FSCM content represented in the Nav Bar. When the user selects an FSCM tile, they are presented with the FSCM content, but the header context remains in HCM. This means that the Nav Bar will still be the one from the HCM system. It also means that if the user employs Global Search, the results will only come from HCM. Similarly, any notifications/alerts/actions they receive will originate from HCM only. Basically, the partitioning between the applications is maintained. If users want to search in FSCM, they must log out of HCM and log into FSCM, which at that point will become the acting portal system.
Now let’s look at an example in which the customer is using the Interaction Hub to unify the cluster including HCM and FSCM. In this scenario, the user logs into the Interaction Hub system, which provides the header and context. The home page displayed initially can come from HCM or FSCM (or any application), and the Nav Bar can contain content from any PeopleSoft application where the content from these applications are registered. When the user navigates to any content--whether it comes from the Interaction Hub, HCM or FSCM--the header and the Nav Bar is from the Interaction Hub system, which is where the user originated. In this case, even when the user navigates to an HCM or FSCM transaction page, they can still use the header or the Nav Bar to navigate to any content in the cluster seamlessly. In addition, if the user executes a search, the results of that search can come from any application in the cluster—in this case HCM, FSCM, or the Interaction Hub. Furthermore, the user can take action from those search results using Related Actions regardless of where that content originated. Similarly, the notifications in the header will deliver actions and alerts from all content systems in the cluster, and users can act on those notifications from the notifications window.
Customers that have a cluster of multiple PeopleSoft applications should use the Interaction Hub to unify their user experience. The Hub enables you to break down the barriers between applications and align your user experience with your business processes. This enables your users to navigate freely among PeopleSoft content (and even external content) to complete their work--without having to know which PeopleSoft application is being used. In addition, users don’t have to log in and out of different applications to complete business processes that may cross application boundaries. Instead, the Hub presents the PeopleSoft cluster as a single unified ecosystem.