Tiles in PeopleSoft fluid homepages

Tiles are building blocks or elements of an Home page that show information to the end user 
And enable an easy way to navigate around the system. Tiles allow users a quick way to perform routine tasks, such as decision making or monitoring. Tiles give users direct access to targeted transactions.

Creating a Tile

The below diagram clearly depicts components of a Tile and the sequence in which they should be created.

Adding tiles to the homepage

Step 1

Give access to the Source

Step 2

Give access to the Target

Step 3

Give access to the homepage

Step 4

Selected the tile to appear on homepage

Step 5

Configure the tile to mandatorily appear on homepage

Want to see a demonstration with real time example on how to create and add tiles to fluid homepage?

I have a complete session which demonstrates:

1. The Tiles overview
2. Creating the Tiles
3. Adding the Tile to fluid homepage

Below is the link to video in YouTube.

PopelSoft Fluid Tiles

However, if you want to save money by purchasing whole module instead of in parts then visit this page to get more details PeopleSoft Functional and technical online training

How to implement Toolbars in a Page PeopleSoft

Toolbars are replacements of traditional push buttons, they brings many advantages for developers on the table such as:

• Very easy to implement
• No alignment required
• Their page behavior can be controlled from PIA
• Easy to debug since the underlying code is written in App Class/Package

While the developers enjoy these advantages while implementing Toolbars however, once implementated, the end users enjoy the ultimate benefits such as:

• The page looks more aligned with modern web based pages
• Easy to navigate through various pages involved in the wizard like applications
• For the pages with bulk data which makes it long with scrolls, the Toolbars with actionable options can be displayed both in header and footer areas. This makes the end user's job easy to take the actions on page.

These are the steps to implement Toolbars:

1. Identify the icons/buttons required on the page
2. Create/modify the buttons that are required to be displayed on Toolbar in the page
3. Create new Toolbar Definition and add the buttons
4. Develop the application package/classes which contains underlying code for toolbar action
5. Add the delivered sub page for toolbars into the page where this needs to be implemented
6. Add the PeopleCode into the page activate PeopleCode to initialize Toolbars on page
7. Add the PeopleCode in the FieldChange event to trigger the underlying PeopleCode

Want to see a demonstration with real time example on how to implement Toolbar?

I have a complete session which demonstrates:

1. The Tooolbar overview
2. Implementing Toolbar on a page

Below is the link to video in YouTube.

PopelSoft Toolbars

However, if you want to save money by purchasing whole module instead of in parts then visit this page to get more details PeopleSoft Functional and technical online training

4 Reasons PeopleSoft will continue to be a leader in HR segment

Over last few years, especially since the advent of Workday, the talks that PeopleSoft, once a leader in the ERP segment is now loosing it's hold in the market share and soon it will be vanished, is going around a lot. Being a PeopleSoft consultant for over 8 years, that's not too long though, it concerns me a lot not because I also believe what People say but more because these excessive talks are changing perception among those who are already working in this technology as well as young aspirants aiming to kick start their career in this.

So, what's going to happen ? Is what being talked about gonna be true or there is something which is gonna change the course of the wheel ?

It's true that some of the PeopleSoft customers are switching over to Workday but while that happens, customers who are in other technologies are also switching over to PeopleSoft and this has been happening for quite a long and that keeps the balance in the industry.

So these are the 4 reasons that make me believe what I believe 

Fluid UI

In this era of compact devices(Smartphones, Tablets, Ultrabooks), the classic user interface really looked old school and was bound to fade out in the end. Apparently Oracle realized it on time and came up with Fluid Technology. PeopleSoft application fluid pages scale gracefully from large screen devices, such as laptops and desktops, to the reduced viewing space of tablets and smartphones. Many commercial websites use a similar design model whereby the presentation and layout of information is adjusted dynamically to conform to the dimensions of the user’s device.

With Fluid, PeopleSoft is has already moved from an application based portal to a modern website based portal. 

No more expensive upgrades

The big fat upgrade process have really been dragging down PeopleSoft from staying afloat like it has always been, so Oracle had to come up with something really path-breaking and they did which we call as PeopleSoft selective adoption wherein we break the large upgrade into small easy-to-apply updates through a tool called PeopleSoft Update Manager (PUM). It really simplifies the maintenance.
 starts with a complete image of PeopleSoft, a cumulative image that includes everything and is updated as often as every 8–10 weeks. PUM simplifies the process of identifying and creating a tailored package for updating your PeopleSoft system with enhancements, bug fixes, and regulatory changes. Change Assistant then takes the tailored package from PUM and automates most of the remaining steps to update the system.

Interaction Hub

Lets first understand what Interaction hub really is.
Assume your organization has these 4 different applications running on different systems to conduct daily business.

• PeoleSoft HR to conduct HR related business activities
• PeopleSoft Finance to conduct Finance related business activities
• A Benefits and Payroll system
• A system that facilitates time related entries and processing

Typically, an employee in the organization has to login into all these systems and perform various transactions depending upon what their role is which is very common but the problem with this is that they have to login into each system and then navigate to various links/pages to carry out the same.

Now let's say we have a single unified portal where an employee, depending upon their role, can access all these four systems and the related links/pages where they conduct their day to day activities, from this portal with just single sign-on.  That's PeoleSoft interaction hub is all about.

Powered with fluid, interaction hub is now website based portal instead of application based portal having all the necessary navigation to the pages of all the underlying systems enabling users to seamlessly conduct their day to day business activities.

Flexibility

Unlike a pure SaaS solution (Example - Workday) PeopleSoft offers it's customers a development platforms called PeopleTools to tailor the application based on the business needs, So, PeopleSoft can address most complex business requirements. This is one of the features that make PeoplSoft stand out in the ERP crowd.

Customers can have both the options to implement PeopleSoft:

• On their on-premises infrastructure 
• On Oracle cloud to eliminate the cost of on-premises infrastructure 

How to get rid of system generated OPRID criteria in PS Query without having to create View

This particular issue is very annoying especially if you happen to use OPRID as a key field in your custom records and don't realize that you can't use the record in PS query as the Query Manager appends the additional criteria and by the time you realize, it has become very late.

However, even if you land up in such a circumstance, do not worry.  You just need to do a slight adjustment in the record field properties using App Designer to prevent Query Manager from appending the OPRID criteria:

• Make the field OPRID also an List Box Item
• Make the field OPRID also a Search key

The first option is safer and doesn't require much analysis. However, second option will have significant impact as enabling Search option will change the behaviors of components where this record has been used as search record.

Check out PeopleSoft Functional and technical online training

Concept of Salary Admin Plan, Grade and Step in PeopleSoft

Want to learn PeopleSoft Core HR module thoroughly? I have several videos with total duration of 12 hours.

Following is the link to the YouTube videos Core HR
Click here to see course contents

Click here to know how it works

However, if you want to save money by purchasing whole module instead of in parts then visit this page to get more details PeopleSoft Functional and technical online training

4 Key advantages of Application Package over traditional Functional Libraries

Better Organization of Code

Through my experience they do not have any significant performance impact but they do add an additional layer of organization that funclibs cannot provide.
Example:
Assume you are developing a self-service application named ePromotion so this is how you can organize your PeoleCode using Application Package:
You can create one package named EPROMOTION for the whole project, and then add the classes within it as below:

EPROMOTION

1. ePromoUtility
2. ePromoConstants
3. ePromoNotifications
4. ePromoUserLists

Coding Practice

They enforce better coding practices. For instance, in regular peoplecode (funclibs, etc), variables are not required to be declared before using them, but in app classes they are - thus eliminating bugs introduced by typos. Variable scope is much more explicit and easier to understand / follow as well. 

Avoid Redundant Code

Also an App Class can extend an existing App Class thus allowing you to leverage the original code without copy / pasting it. All of this is part of the advantages of Object Programming. 

Portability is another aspect, being able to pull up the App Package and go through it without having to dig through Component Record Field PCode or Record PCode. Just import your package/class, instantiate and call. Keep all the grunt work in the app package.

Think Time PeopleCode

Biggest advantage is that it is think time PeopleCode versus "regular" PeopleCode which is run time. As an example, if you have functions in a funclib record and you call a function in your PeopleCode, at run time (when you go into a component) and run a trace, you will find that 1) Your function is being brought in and 2) All the other functions are being brought in even though they are not going to be called. In an App Package, the code is imported, but no call to the code is made unless needed. That means that as you go into your component, The App Package is not brought in until called. You can construct code so that you only instantiate your app class and code as needed. Ex., If True then &Variable = Create AppPackage:AppClass(); &Variable.DoSomething(); else end-if; If true then we bring in PCode else we do not. 

Another way to visualize think time versus run time PeopleCode is to go into a component / page. Make a change to regular PeopleCode and save. Now if you navigate or try and save the component, you will get a data integrity error and have to re-navigate back to where you were. With think time, you go into a component / page. Make a change to your app package PeopleCode and save. No data integrity error on your page as the code is brought in at think time and thus no error.

You can gain in-depth knowledge on Application Package with a live example by just paying below amount

I have a complete session in two parts which explains:

1. Advantages of using application packages over functional libraries
2. Elements of Application Package and how to write PeopleCode using them

Below are the links to videos in YouTube.

App Package Part 1
App Package Part 2

Click here to know how it works

However, if you want to save money by purchasing whole module instead of in parts then visit this page to get more details PeopleSoft Functional and technical online training

Why query is not visible in Query Manager

Did you ever felt embarrassed by not being able to even open the Query in Query Manager let alone modify it despite having access to it i.e having access to records used in query and to make the matter even worse, this all happened when you are a PeopleSoft consultant who is believed to know such technical glitches.

Well, guess what, this was exactly what happened to me few years ago. There was a query of type Role with a simple SQL text 

SELECT OPRID FROM PSOPRDEFN

These were the properties of the query

There was requirement to make some changes in this so I quickly tried to open it in Query Manager but it didn't come in search result. Whenever we come across this particular incident, there are two things that you believe could cause this:

You don't have access to Query

If you don't have access to all records used in Query through Query Security Tree then you won't see the query neither in Query Manager or Query Viewer. So, I open the query in Query Administration (Peopletools - Utilities - Administration - Query Administration) and checked the SQL and discovered that only one record PSOPRDEFN has been used in this query to which I already have access which effectively authorizes me to open the query in Query Manager but it didn't.

Note - Query Administrator page empowers you to open any type of query whether or not you have access to it.

Query is private

Having had no luck here, I then turned my attention to what if Query is Private ? so I looked closely at the attributes of this query in Query Administration.

Having discovered that query isn't private either because it's not assigned to any user, when it's assigned to a user then it means it's private, I then started to feel puzzled as to what the heck is going on. Then after digging through little more I felt so stupid when I finally figured it out. I went to query manager again and clicked on Advance Search

There it is..! by default the query type selected by system is User so when I entered the query name and hit on search, the Query Manager tried to search only those with type User whereas my query was of type Role hence despite having full access to it and query being public too, I couldn't fetch it.

So all I did was, change the value in the drop down above to Role and then performed the search again and it did the trick.

You can gain in-depth knowledge on PS Query with a live example by just paying below amount

I have a complete session in two parts which explains:

1. How CI works - Overview, all the elements of CI etc..
2. Creating an Inbound interface, that loads data on a multi level component using CI and App Engine

Below are the links to videos in YouTube.

PS Query Part 1
PS Query Part 2

Click here to know how it works

However, if you want to save money by purchasing whole module instead of in parts then visit this page to get more details PeopleSoft Functional and technical online training

Creating a Component Interface in PeopleSoft

You can gain in-depth knowledge on CI with a live example by just paying below amount

I have a complete session in two parts which explains:

1. How CI works - Overview, all the elements of CI etc..
2. Creating an Inbound interface, that loads data on a multi level component using CI and App Engine

Below are the links to videos in YouTube.

CI Part 1
CI Part 2

Click here to know how it works
However, if you want to save money by purchasing whole module instead of in parts then visit this page to get more details PeopleSoft Functional and technical online training

How it works

Send an email/message on either of below contact to know how to make payment

santosh.tripathi87@gmail.com
Whatsapp - +91 8800648297
skype - santosh.tripathi72

Once the payment is done, you will get access immediately to the videos shown in the link on the shared Gmail ID, a email notification with link to videos will also be sent

Done..!!

However, if you want to save money by purchasing whole module instead of in parts then visit this page to get more details PeopleSoft Functional and technical online training

PeopleSoft Benefit Record Number Vs Employee Record Number

These two elements are always confusing especially for the person who isn't well versed with the Person Model.
The Employee record Number (ERN) is updated whenever a new assignment is created.The Benefit Record Number is defaulted to 0 to attach the new job with Benefit Record Number 0 but can be overridden to the particular number if it needs to be attached to that Benefit Record Number.

The Benefit Record Number is used by benefit module to track benefit entitlements of employees. Multiple Employee Records (EMPL_RCD) can be grouped under one Benefit Record Number.

Lets try to understand this with a very simple scenario.

Lets say a person is a professor in a college with Employee Record 0 and is eligible for various benefits so we assign the Ben Record Number as 0 to track his eligibility and enrollments in various benefit plans.

Lets say this person got appointed as a Dean of the same college after some time so a new job got created with Empl Record 1 but since this new job doesn't make him eligible for any new benefit program so we keep the Ben Record Number as 0.

But after sometime, lets say this person appointed as a physician also in the same college so we created a new job with Empl Record 2. However, this new job entitles him for an additional benefit program but can't be mixed with previous one so we assign ben record number for this new job as 1 for eligibility and enrollment of this employee under new benefit program.

Want to learn PeopleSoft Benefits module thoroughly? I have several videos with total duration of 12 hours.

Following is the link to the YouTube videos Benefits
Click here to see course contents

Click here to know how it works

However, if you want to save money by purchasing whole module instead of in parts then visit this page to get more details PeopleSoft Functional and technical online training