The PeopleCode language has a lot of features and functions. But sometimes, it seems there are tasks we need to accomplish that are just out of reach of the PeopleCode language. It is at these times that I reach for Java. I have written a lot about Java, so I'm sure many of you already know how to mix Java with PeopleCode. While certainly a rational solution, one of the pain points of a Java solution is managing custom Java on the app and process scheduler servers.
One of our customers asked us to implement nested landing pages, in which some tiles would open a second landing page and eventually a third one and so on. Let me illustrate the use case with some screenshots (I apologise as they are in Spanish, but it should be useful anyway). This would be how the main landing page would look like:
I was asked by Dan Iverson from psadmin.io about my experiences of PeopleSoft on Oracle 12c. I have seen a number of PeopleSoft Financials systems on 12c recently. Generally the experience is very positive, but one common feature is that they had all disabled Adaptive Query Optimization. What is Adaptive Query Optimization?
Lots of information about the configuration and operation of a PeopleSoft system is stored in the database. Of course, most of the application itself is stored in the PeopleTools tables, for example, there are also performance metrics, particularly about batch processes. PS360 is a new tool that I am working on that will use just SQL scripts to extract that data to flat files, and package them up in a zip file so that they can be sent for further analysis.
I recently recorded an interview with Dan Iverson and Kyle Benson for the PeopleSoft Administrator Podcast. It has been spread over three episodes. There is lots of other good stuff on the website and other episodes that are well worth listening to.
I have blogged recently about the effectiveness of the Tree Performance options in improving the performance of nVision reports. However, a consequence of the Tree Performance Access Method suppress join; use literal values is that the resulting SQL in nVision will have a criteria for every leaf on each of the selected nodes on that tree.