#13 – PeopleTools Patching

This week, Kyle shares his lessons learned from a recent PeopleTools patching project, we discuss the pro’s and con’s of Unified Navigation, new PeopleSoft Rundeck plug-ins, and changes to the 9.2 upgrade with PeopleTools 8.55.

We want to make this podcast part of the community discussion on PeopleSoft administration. If you have comments, feedback, or topics you’d like us to talk about, we want to hear from you! You can email us at podcast@psadmin.io, tweet us at @psa_io, or use the Twitter hashtag #psadminpodcast.

You can listen to the podcast here on psadmin.io or subscribe with your favorite podcast player using the URL below, or subscribe in iTunes.

Podcast RSS Feed

Show Notes

2 thoughts on “#13 – PeopleTools Patching

  1. I agree wholeheartedly with the concept of keeping a daily activity log. I have 13 years of logs containing both my PeopleSoft and other IT-related activities for my current job, stored in OneDrive for Business. They are invaluable when searching for a resolution to a problem that I know I already encountered weeks, months, or years ago. I especially enjoy being able to tell a user: “oh yeah, we ran into [such-and-such problem] on [insert specific date here] and fixed it by [my resolution].” If an issue requires more research or detail then just a few lines in the activity log (i.e., screenshots, log traces, etc.), it goes into the issue log documentation and then I just refer to the issue number in my activity log.

    The logs started out as Word documents, then converted into an InfoPath form for the department when we upgraded to Office 2007 that we’ve been using ever since. Now that Microsoft has dropped InfoPath from Office 2016, though, I need to look into a redesign using OneNote. I like the idea of snapping it to the side of my second monitor so it’s up all the time (currently I just have a shortcut on the Start menu with a keyboard shortcut (Ctl-Alt-2) to open InfoPath when I need to add a new log item).

    1. Wow, InfoPath, that brings back some memories. Kyle really likes OneNote, but I’ve yet to jump on that bandwagon. We have enough of our technical documentation in a wiki (Instiki) and changing to another tool feels like too much work. It may or may not be hard, but we’re comfortable with the setup and it’s working well for us.

      It’s great to hear of other people keeping daily logs. There are days when I feel like I’ve done nothing (or nothing I wanted to do), but when I look back at my log I can see why. Maybe there were production issues that took my time, or a side project was started, etc. The log also helps me focus on what I’m working on too. If I’m actively documenting what I’m working on, I’m less likely to get distracted and start working on something new.

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax