Jim Marion

Subscribe to Jim Marion feed
A blog containing development tips I have learned through the years as a PeopleSoft developer.Jim Marionhttp://www.blogger.com/profile/12995110203807924786noreply@blogger.comBlogger283125
Updated: 9 hours 37 min ago

"Find Definition References" for Page and Field Configurator

Mon, 2022-11-21 13:33

A student recently asked:

Is there an Edit | Find Definition References equivalent for Page and Field Configurator?

Great question! In Application Designer, we can open a field and choose Edit | Find Definition References to find all usages of that field. Unfortunately, Page and Field Configurator does not have an equivalent. The good news, however, is Page and Field Configurator is metadata driven. In other words, we can create our own "Find Definition References" equivalent by writing SQL. Here is a short example to get you started:

SELECT *
FROM PS_EOCC_CONFIG_FLD
WHERE FIELDNAME = 'DESCR'

The EOCC_CONFIG_FLD record contains the Component name, Record name, and Field name, allowing us to effectively "Find Definition References" for any of those three items.

At JSMpros, we teach PeopleTools Tips like this every week. Be sure to check our website to see what we are offering next!

TokenChpoken

Tue, 2022-11-08 09:26


Several years ago, ERPScan published a series of articles describing PeopleSoft security attack vectors. While reading the series, keep in mind it was written nearly a decade ago, and PeopleSoft has made changes to security to mitigate the issues raised by ERPScan. For example, their article about the Access Token ends with the note, "this vulnerability was patched in Oracle CPU for October 2014." Note to self: Apply CPUs! But the topic that keeps coming up is TokenChpoken.

What is TokenChpoken?

When you authenticate (log in) to PeopleSoft, PeopleSoft sends a cookie to your browser. Thereafter, PeopleSoft identifies you by that cookie. For every request, PeopleSoft asks, "who are you?" and that cookie supplies the answer. This cookie is critical to cross-product SSO for unified navigation, Interaction Hub, etc. TokenChpoken describes how to decrypt that cookie, change the OPRID, and assume the identity of someone else. Pretty scary! But is it legitimate? As described by the TokenChpoken write-up, someone leveraging this approach must know your user ID, the SSO node name, and the node password must be discoverable through a modern brute-force attack. If you renamed your nodes and use strong passwords, you are a long way from a TokenChpoken "vulnerability." But that doesn't eliminate the potential. It is now a risk calculation.

Is TokenChpoken still relevant for today's PeopleSoft? In PeopleTools 8.56, PeopleSoft implemented a "knock knock/callback" pattern with a check token. Dan Iverson has a great write-up on this 8.56 feature. Likewise, as of 8.56, if I restart my web server while browsing PeopleSoft, PeopleSoft renders the message "unauthorized token detected." It seems like PeopleSoft now keeps a list of issued tokens in memory, and a restart clears that list. These are fantastic safeguards against a potential TokenChpoken Switch User. My thought is,

"If PeopleSoft won't accept its own token after a restart, why would it accept a modified token?"

But is this enough?

A few years ago, Colton Fischer came up with a simple way to test functionality as a different user. You log into PeopleSoft as yourself, press a bookmark in your web browser, supply the node name, node password, and the target user ID, and instantly become someone else. You may find his project here. As a developer and tester, this sounds fantastic! Through a "master password," I can assume the identity of anyone for testing purposes, of course. How does it work? It is essentially TokenChpoken in the web browser. What does that mean? TokenChpoken is alive and well.

Mitigation

As documented by Dan Iverson, setting the Check Token and node password on your nodes, as well as changing node names from something other than the default PSFT_xx, is a great start. And that start may be enough. But you might want to try Colton's bookmarklet to see if you can become someone else. If so, here is another idea: Eliminate the PS_TOKEN cookie. Eliminating the PS_TOKEN is a bit controversial as this is the "key" to PeopleSoft SSO, and it may not be the right solution for you. But here is how it works: As a request leaves a load balancer or web server, the web server/load balancer replaces PS_TOKEN with a different, randomized cookie. On re-entry, the web server/load balancer maps that random cookie to the original PS_TOKEN. PeopleSoft is unaware and functions as usual. If all of your PeopleSoft instances are behind the same load balancer and use the same domain, then SSO may work as usual, and token replacement may be a great option. If you want an off-the-shelf solution, check out Pathlock's ERP Firewall, which has built-in TokenChpoken mitigation.

Since most PeopleTools classes involve nodes and security, we talk about TokenChpoken regularly. To learn more about this topic and other PeopleTools tips, check out our website to see what we are offering next!

Triggering FieldChange from JavaScript

Fri, 2022-10-28 10:06

We love a challenge, and we believe anything is possible with PeopleTools. It is never a question of "can you?" but "how?" A customer recently shared a challenge with us:

We use a handheld scanner to enter values into a text field of a Fluid Page. After scanning, we want FieldChange PeopleCode to load data into the remainder of the page. Our solution worked great in PeopleTools 8.58, but quit working after upgrading to 8.59.

Since many scanners act as automated keyboards, sending keystrokes derived from barcodes, there are several ways to handle this. The simplest way is to include a button immediately following the data entry field and use this button to trigger FieldChange. But this got us thinking about another scenario:

How do you trigger FieldChange if you use JavaScript to update a data entry field?

 The process involves three steps:

1. Use JavaScript to update a data entry field. The JavaScript might look something like this:

document.getElementById('MYRECORD_MYFIELD_ID').value = 'The new value';

2. Stage field changes by triggering the onchange handler

document.getElementById('MYRECORD_MYFIELD_ID').onchange();

3. Trigger PeopleSoft's Ajax processing

submitAction_win0(document.win0, id);

Notice the win0 in step 3? That is a system-generated name that reflects the current window ID. PeopleSoft uses the Meta-HTML %FormName at design time.

Here is a short example I put together for the PeopleTools 8.59 Event Mapping configuration page, complete with HTML element IDs, that demonstrates using %FormName. The purpose of the fragment is to set the service name for an event and trigger PeopleSoft processing:

Please note: this is an unsupported example that worked for a specific use case but may not work for others. We provide it as an example of what's possible and as a starting point for your own solution.

Are you interested in learning more PeopleSoft Fluid tips and tricks? Be sure to enroll in one of our upcoming events!

Decustomization Strategies Free Webcast!

Wed, 2022-10-26 16:08

Join us Thursday, November 3, 2022, for a free 30-minute webcast describing PeopleSoft decustomization strategies such as:

  • When should you Decustomize?
  • What tools are available?
  • How do you use those tools?

Be sure to register immediately, as the webcast is next week! It all starts at 12:15 Central.


Announcing Configuration Day 2022!

Tue, 2022-10-25 10:18

Announcing PeopleSoft Configuration Day! Join me online Thursday, November 17th for a full day PeopleSoft education experience filled with tips and best practices. Space is limited so register now!

Register Now!

Here are some of the topics we will cover and questions we will answer:

Configuration versus Customization

  • Are Page and Field Configurator changes really configurations?
  • What about Event Mapping or Drop Zones?
  • Why does Oracle call these features "isolating customizations?"

PeopleSoft Test Framework

Isolated customizations do not appear on compare reports. But without compare reports, how do you know what to test and what to retrofit? Learn how to use PTF to regression test configurations and isolated customizations. Experience the new PTF Chrome-based recorder when you join us Thursday, November 17th.

Security

Learn about the data privacy framework and how it differs from Page and Field Configurator's Data Masking. Learn how functional business analysts may use roles to secure, hide, and mask fields.

Extending Oracle-delivered page Content

Learn how to use Related Content and Drop Zones to add more content to Oracle-delivered pages. Find out where these features are similar and where they differ. Learn when to use which tool.

HCM Application-Specific Configurations

What do My Team, Job Data, and Benefits have in common? HCM-specific configuration options. Should you use these options or the more generic PeopleTools configuration alternatives? Join us on Thursday, November 17th to find out!

Activity Guides

Should you use PeopleTools Activity Guides directly or Activity Guide Composer? Find out on Thursday, November 17th!


Register now to find the answers to these and many more questions on Thursday, November 17th.

The cost for this event is $447 per person. If you have a group of 10 or more, contact us at info@jsmpros.com for a quantity discount.

Register Now!

REST Consumer Base URL Maintenance Idea

Sat, 2022-10-22 11:50

"Legacy" Integration Broker used nodes to identify endpoints, and we migrated nodes separately from Messages and modern Service Operations. This design offered the following benefits:

  • Reuse across 8.47- Messages and 8.48+ Service Operations,
  • Different endpoints between development and production, and
  • The ability to test node connectivity without invoking a live service.
Modern PeopleSoft REST consumption, however, requires us to specify the full endpoint URL on every Service Operation. Here is an example. Let's say I want to send absence requests to the Oracle HCM cloud. Since the current version is 11.13.18.05, I would post to a URL that looks something like: https://some.server.com/hcmRestApi/resources/11.13.18.05/absences. If I also wanted to create workers, I would post to https://some.server.com/hcmRestApi/resources/11.13.18.05/workers. Do you see the similarities? I would have two service operations pointing to the same URL base. And that is just for POST. There are also GET, PUT, and PATCH operations, which would result in further redundancy. Now, let's say I need to change my server domain name or service version. That would require me to locate and update every Service Operation that uses the old base URL.

My other concern with the current design relates to the separation between development and production. Since the full endpoint URL is stored with each Service Operation, a migration from development through to production may require an update to the endpoint URL. In a sense, this requires us to place untested configurations in production.

To work around the current design, many developers resort to code-only metadata-less integrations where they use simpler metadata constructs such as URL definitions, App Classes, and Message Catalog entries for shared reusable fragments.

We believe there is value in Integration Broker metadata, but I think we just need one change. I just proposed the following idea in the PeopleSoft IdeaLabs to simplify the maintenance of both REST Service Operations and the new 8.60 Application Services Framework consumer services. Please vote for this idea if you believe it would be beneficial.

What if Component App Classes Were Configurable?

Tue, 2022-10-18 00:27

With Fluid, PeopleSoft implemented an interesting design pattern: App Classes as Event Handlers. Properly implemented, there are some fantastic reasons to choose this pattern:

You can see Oracle's latest pattern on just about every Fluid component. A component that uses this pattern might have PreBuild PeopleCode that looks something like this:

import SOME_PACKAGE:SomeClass;
Component SOME_PACKAGE:SomeClass &handler;

&handler = create SOME_PACKAGE:SomeClass();
&handler.PreBuild();

But I had this idea... What if the code looked more like this:

import SOME_PACKAGE:SomeBaseClass;
Component SOME_PACKAGE:SomeBaseClass &handler;

Local string &className;

REM ** Select actual implementation of SomeBaseClass from a configuration table;
SQLExec("...", %Component, &className);

&handler = CreateObject(&className);
&handler.PreBuild();

Then we could override delivered behavior by subclassing and configuring our own handlers to override the delivered handlers. And I think this is the best reason to use App Classes as component event handlers. What would it take to implement this solution? Oracle would need to select the implementation class from SQL rather than hard-code its implementation into component PreBuild. But is it worth it? You know that is a fantastic question! You might say Event Mapping offers the same result but is more flexible. Let us know your thoughts in the comments!

At JSMpros, we teach PeopleTools and PeopleCode concepts like this regularly check out our website to see what we are offering next!

PeopleTools 8.60 PTF: Where is IE 11?

Sat, 2022-10-15 17:47

 I was just reviewing the fantastic PeopleTools 8.60 Highlights video and noticed something missing from the PTF Execution/Runtime Options. Here is a screenshot


Do you see something missing? Where is Internet Explorer? Internet Explorer retired on June 15, 2022, and is no longer a "supported" browser, but releases of 8.59 still allowed us to use IE for record and playback as long as we chose IE from the browser list. But I don't see it in the 8.60 screenshot! This is an important consideration as you evaluate PeopleTools 8.60. What do you think of this change? Share your thoughts in the comments!

Ready to learn more about PeopleSoft's Test Framework? Check out our on-demand recorded and live virtual offerings. Want to train your whole team? Contact us for group pricing and scheduling.

Not sure how to get started with PTF? Here is what we recommend: As a developer, start by recording regression tests. Every time you apply a Drop Zone, Event Mapping, or Page and Field Configuration, record a simple regression test to prove your alteration still works. This approach will help you build an amazing maintainable regression test library over time.

PeopleTools 8.60 GA

Thu, 2022-10-13 14:48

 Are you wondering when PeopleTools 8.60 will be generally available? Watch for it on OCI tomorrow! Here are the announcements from this week's PeopleSoft Reconnect conference:

  • PeopleTools 8.60.01 GA cloud-first release date is October 14, 2022
  • PeopleTools 8.60.02 GA on-premise release date is December 1, 2022
We posted a list of changes for 8.60 in our Blueprint 4D conference notes. Check it out!

JSMpros monitors releases very closely to ensure we deliver relevant, timely training using modern tools and infrastructure. That is why we teach all of our classes on PeopleTools 8.59 today and will switch to 8.60 when it is ready.

PeopleSoft ReConnect 2022: I'm Presenting!

Wed, 2022-10-05 14:05

PeopleSoft ReConnect begins next week! Are you ready? I'm just putting the finishing touches on my presentations. I have a ton of great ideas to share with you. Here is a list of sessions I'm delivering. See you there!



Fluid Fundamentals 90-minute Webcast

Tue, 2022-09-20 10:04

 I am constantly amazed at the flexibility of PeopleSoft's Fluid UX. Through AddJavaScript and AddStylesheet, we can make the user interface do or appear however we desire. But in all our cleverness, we can't neglect the fundamentals such as:

  • What are the differences between Classic and Fluid?
  • What are the purposes of the various Fluid layouts?
  • How do I align columns and fields in Fluid?
  • What do I do with related display fields? Why won't they appear beside their control fields?
  • How do you render grids on mobile?
  • Is there a place for the scroll area in Fluid?
We regularly teach Fluid development principles. As developers become familiar with Fluid's CSS capabilities, they begin writing their own CSS. Is that OK? Should we write our own CSS? Absolutely! A better question is, "when?" When should we write our own CSS? When should we inject our own JavaScript? These are the questions we answer through Fluid fundamentals. Whether you have years of experience with Fluid or you are just starting your Fluid journey, we all learn by getting back to the basics: The Fundamentals. So join us on September 29th from 1:00 to 2:30 PM Central for 90 minutes of Fluid Fundamentals. Register now!

Mock Service URLs for PeopleSoft Testing

Mon, 2022-09-19 14:21

 As you create, learn, and discover Integration Broker's capabilities, it is helpful to have mock APIs for testing purposes. Here is a list of my favorites.

Many of these services have secure and non-secure alternatives. The value of insecure testing is you don't have to import certificates. On the other hand, the secure versions help you prove your PeopleSoft certificate import skills.

Do you have some sample APIs you use? If so, please share them in the comments!

At JSMpros, we teach PeopleSoft REST and SOAP integrations regularly. Want to learn more? Check out our Integration Tools Update course to learn best practices and strategies for incorporating REST and JSON into your development process!

Simple Code-only REST Request

Wed, 2022-09-14 16:13

PeopleSoft is a metadata-driven application. It stands to reason, therefore, that the solutions we create require metadata. Sometimes metadata, which is supposed to be configurable, forces us down an immutable (non-configurable) path. Integration Broker is a fantastic example of semi-mutable, bordering on immutable metadata. As we prototype, we often make changes. But the testing associated with prototyping locks various metadata pieces. Sometimes we just want to test without metadata and backfill after we choose the proper path.

Here is a very simple metadata-free REST request example I run from a local App Engine program for prototyping and testing purposes.

Now, an important question:

Once you have a working "simple" solution, do you backfill and update with proper Integration Broker metadata?

Let us know your thoughts in the comments below!

At JSMpros, we teach Integration Tools concepts regularly. Check out our website to see what we are offering next!

Recordings Available!

Mon, 2022-09-12 13:29

Did you know we record all of our events? Replays are available through our online learning platform. Be sure to check out the webinar collection. Each replay includes sample code downloads, handouts, a Q&A roster, and links to additional resources. Topics include:

  • Integration (REST, SOAP, Cloud, Application Services Framework)
  • Fluid (Fundamentals, Drop Zones, Grids, Navigation, Complex CSS)
  • PeopleCode Application Classes
  • Isolated Customizations and Configuration Alternatives (Drop Zones, Event Mapping, Related Content, Related Actions, Activity Guides, Page and Field Configurator)

Do you prefer interactive training with plenty of hands-on activities? Check out our schedule to see what we are offering next!

Metadata-less Integration (Easy REST)

Wed, 2022-08-31 10:28

 As PeopleSoft customers move to REST, I've noticed an interesting trend: choosing code over metadata. Most of the examples I've seen online are labeled Easy or Simple. Some of the examples use fully supported documented approaches, whereas others use undocumented internal testing methods. Here are some of my favorites:

Based on those examples, REST PeopleCode really is easy! But what does that say about the metadata approach? Is it hard? Is it complex? To answer that, let's review the metadata definitions necessary to craft a REST request:

  • UR Document (if the target has parameterized URLs)
  • URI Message (if the target has parameterized URLs)
  • Request Document (if POST, PUT, or PATCH)
  • Request Message (if POST, PUT, or PATCH)
  • Response Document
  • Response Message
  • Service
  • Service Operation
  • Service Operation Security

And when you are done with the metadata configuration, you must still write code to invoke the REST request. Interestingly, invoking a REST metadata-based request requires roughly the same amount of PeopleCode as a "simple" or "easy" PeopleCode request.

So what does all that Metadata buy us? In other words, why choose metadata over pure code?

  • Logging: We can set the log level in the routing.
  • Security: OAuth and Basic Auth options can be set at the routing level.
  • Parsing: Document-based messages will parse JSON, XML, and Rowsets for us.
  • Maintenance: We can update/change URLs online rather than through PeopleCode (although a URL definition is a very simple way to maintain URLs across instances).

What if you don't require these features? Perhaps choosing the simple PeopleCode approach is better? Let us know your thoughts in the comments!

We teach PeopleTools REST and Integration regularly through our three-day Integration Tools Update course. Check out our website to see what we are offering next!

Which Query Security Tree?

Wed, 2022-07-20 15:24

Here is the scenario:

A user needs to create a query, but doesn't have security access to view a record. The user asks you for help.

Before running or writing queries, a user must have access to records through Query Security Trees. We assign records to trees, trees to permission lists, permission lists to roles, and roles to users. The solution is trivial: grant security access through a security tree. The difficult part is deciding which tree and which permission list. When I receive a request like this, I have two groups of questions:

  1. Is there already a query security tree that grants access to the target record? If so, which one and which permission lists? Would any of those permission lists be appropriate for this user?
  2. Is there already a query security tree available to this user that would be a good fit for this record?

Here are some SQL statements I created to help answer these questions.

Find existing trees that include the target record:

Finding Permission Lists that grant access to a specific record is more challenging. Locating permission lists that contain a tree that contains a record is trivial. Narrowing that list based on Access Group is more challenging because Access Groups represent node hierarchies and therefore require recursive logic:

Do you have SQL statements and tricks to help you manage Query Security? If so, share them in the comments!

At JSMpros, we teach PeopleTools tips like this every week. Check out our website to see what we are offering next!

Announcing: PeopleSoft Developer Day 2022!

Tue, 2022-07-12 18:11
a.jsm-button { background: rgb(216, 88, 66); border-radius: 0.2em; color: white; display: inline-block; padding: 1em 1em; text-decoration: none; text-transform: capitalize; transition: all .2s ease; } a.jsm-button:hover { transform: translate3d(0, -3px, 0); box-shadow: 0 10px 20px #d8594240; }

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

Register Now!

I have some fantastic new content to share with you; tips and ideas that will help you deliver better, modern solutions with less effort. We lead our Developer Day webcast once per year, and pack it with a variety of PeopleTools topics. This year we'll focus on the following topics:

  • Fluid: we want you to build highly engaging, informative, modern, mobile-friendly solutions, and we want you to do it with less effort. With that in mind, we have some Fluid-specific tricks to share with you.
  • Integration: digital assistants are incredibly popular. But what makes them possible? Integration. Cloud, on-premise, payment gateways, purchasing... there are so many opportunities for integration and we want to make sure you know all the productivity secrets.
  • Isolating Customizations: with continuous delivery and the cloud's "always current" policy, it is critical that we learn to uptake new features as fast as possible. But to do that, we must reduce our customization retrofit timeline. We have great ideas to share with you in this regard, including regression testing best practices.
  • PeopleCode: nearly every PeopleSoft solution involves PeopleCode. But here's the problem: PeopleCode can be hard to read. We want to help you by showing you ways to write better, human-readable PeopleCode.

 

Register now to reserve your seat for this dynamic one-day event on Thursday, August 18th. 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!

It's a wrap! Blueprint 4D 2022 PeopleTools Recap

Fri, 2022-06-10 19:05

We just finished the fantastic Blueprint 4D conference, full of great sessions and incredible networking. It is always a pleasure to meet our JSMpros student alumni and connect with members of the PeopleSoft community.

The conference started with a great lineup from Product Strategy, including Paco sharing a broad perspective of what to expect in future PeopleSoft applications, and then focused strategy breakout sessions. It is very clear PeopleSoft is still a top-tier ERP solution. If you are a PeopleSoft developer, here are some things to watch in future releases:

  • New theme for PeopleTools 8.60. We've been watching the steady transition to the Oracle Redwood theme, and it appears the transition is complete.
  • Global Search is visible all the time, not just on homepages. To make room, PeopleSoft moved the page title down a row, in line with the component header.
  • Recent and favorite icons from the 8.59 homepage move up to the left side of the header. To make room, the back button is collapsed to an image.
  • The global actions header is now detached from an optional component-specific header. While the proliferation of dot-dot-dot menus may seem confusing, I'm pleased with the change as it is now visibly clear if a component has custom actions.
  • Configurable search is coming! Configurable search appears to be based on keyword search, which is a viable option if real-time indexing is enabled. Configurable search will be available for both Classic and Fluid. In summary, configurable search lets you configure search fields and list box items, rather than relying exclusively on search record metadata. Besides Configurable Search, using keyword search (Elastic at this time) also allows you to search for transactions from the global search bar, and the global search bar will show transaction search suggestions from your keyword search history.
  • Fluid is getting SQL Search. My interpretation of this new feature is that Fluid will finally leverage search record metadata to build search pages for us just like Classic. This will be a great time saver since current Fluid search strategies include Pivot Grids, Elastic Search, custom search pages, and custom components.
  • PeopleSoft will transition from Elastic Search to OpenSearch to be consistent with Oracle Cloud. No mention of the impact on Kibana. The timing for this is unknown as the 8.60 planned release will use ELK 7.10. Regardless, the change should be transparent as our users use the PeopleSoft search framework, not Elastic directly. Elastic changed the license with 7.11, which is why Oracle is staying with 7.10 for now, and will migrate to OpenSearch, which is based on ELK 7.10. Oracle encourages to continue creating Kibana dashboards, building indexes, etc as the change should be transparent.
  • Future releases of Cloud Manager should support using Data Science to automatically scale up and down based on load and customer-configured thresholds.
  • CSS custom properties (variables) will replace branding macros. I am very excited about this. We just released a YouTube video showing how to apply a hover effect to rows through CSS. As of 8.59, we must hardcode the hover color, border, etc. In the video, I specifically stated these colors are different than 8.57 and earlier, and hard-coded colors could present a maintenance challenge. If we can leverage PeopleSoft CSS variables, we may be able to reduce future maintenance. With each release, we still expect variable changes (new variables, etc.) just as prior releases brought new Branding Macros, but finding and updating the list with future additions should be trivial with a text compare tool.

Campus Solutions
  • PI 24 delivered Drop Zones to the following three components: Personal Details, Biographic Details, and Emergency Contacts. This is fantastic as it allows us to collect additional information about students without customizing the Oracle-delivered pages.
  • Future Fluid components will include Drop Zones and CAF.
  • 2023 planned Fluid releases include Transfer Credit, Degree Progress, Research Activities, and Program Enrollment.
  • Roadmap items include Integration with Student Management Cloud and Student Financial Planning (cloud)
  • Continued WCAG 2.1 enhancements.
  • Continued Classic Plus conversions.
Notes from Sasank's 8.59 PeopleTools session

  • Search: suggestions show history, corporate history, and the menu.
  • For your history and corporate history to appear in the list, you must enable the following indexes: PTSF_RECENT_KW and PTSF_RECENT_MENU
  • For your recent history to appear, you should also enable real-time indexing.

PeopleTools Platforms Roadmap

We could summarize the 8.60 platforms roadmap by stating that PeopleSoft has or will certify on platforms supported by the vendors of those platforms at the time of release. For example, 8.60 drops support for Windows Server 2016. A more accurate way to state that is Microsoft dropped support for Windows Server 2016, making it no longer supported by Oracle. Likewise, IE11 is missing from the browser certification matrix. Given the Oracle OpenSearch announcement made by Dave Bain. It was interesting to note PT 8.60 will release with Elastic 7.10, Kibana 7.10, Logstash 7.10. The 7.10 release predates the ELK 7.11 license change. Mark assured us ELK's support policy and end of service dates are irrelevant because Oracle maintains their own version of ELK with their own patches and their own support. In that sense, you might say we are already on Oracle OpenSearch as OpenSearch is a fork of ELK 7.10.

On another interesting note, PeopleTools 8.60 adds Excel from the Office 365 suite to the list of supported Excel versions. As Mark noted, however, this is not necessarily a product/version certification, but a license model, as Office 365 is not a version, it is a subscription license. This could be interesting as Office 365 is always current and doesn't necessarily follow numbered release versions.

Cloud Manager 14 Highlights
  • Data Science for Auto Scaling: Automatically scale up nodes on increased load. Uses Health center to identify anomolies for scaling.
  • Support for custom domain names to Cloud Manager.
Page and Field Configurator Planned Features
  • Allow page changes dynamically as the user updates information in response to FieldChange events.
  • Use system variables as criteria (date, time, etc.).
  • Streamline selection of fields for the administrator.
  • Track changes made by users to pages (change tracker). This will be field and role-based and will store before and after values. Users will be able to view change history through related content associated with the transaction. Page and Field Configurator configuration component will have a button to activate the Related Content on the target component for you. This related content will work with both Classic and Fluid. Note: This does not replace PeopleTools Audit Tables.
  • Page and Field Configurator will track views of sensitive information, logging each time a user accesses that sensitive information. By the way, this is a common feature of the Pathlock/Appsian Security Platform, usually implemented through click-to-view.
  • Changes coming for search pages: ability to change labels and apply default values.
And finally, as the conference wrapped up, Oracle completed its acquisition of Cerner. I'm expecting to hear more announcements at the HIUG Interact conference next week!

Thank you to everyone that shared at Blueprint 4D! Be sure to mark your calendars for May 8-11 for the 2023 Blueprint 4D conference!

At JSMpros, we lead PeopleTools training using the latest releases and up to date curriculum. Be sure to check out our website to see what we are offering next!

Join me at Quest Blueprint 4D 2022!

Wed, 2022-06-01 17:21
BLUEPRINT 4D
See it. Build it. Do it. Imagine it.

I cannot believe the #BP4D conference starts this weekend! Are you ready? Remember to register for your favorite sessions. There are so many great topics on the agenda. PeopleTools 8.60, the great implementations, and amazing ideas from PeopleSoft customers and consulting partners all at BP4D!

On Wednesday, June 8th, be sure to check out my signature session PeopleTools Tips and Techniques to learn phenomenal new ideas.

Let us know your favorite sessions and topics in the comments section below.

I look forward to seeing you in Las Vegas!

PTF Chrome Recorder

Thu, 2022-04-14 15:51

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.

Pages