Users in each of our functional areas take the responsibility for monitoring patch releases that effect their part of the system. I review the list of "Documents added or updated" in Lawson's knowledge base regularly (daily if possible) to see if there are any issues addressed that we are experiencing. I also query the CTP database at least once a week and review all patches released since the last time I checked.
If I find something that fixes an issue we're experiencing, I forward the CTP to my IS liason who logs the CTP and requests that it be added to the upcoming patch application schedule in our dev system. IS tests in dev, then schedules CTP for application in our test system.
Once appied in our Test system, the users are responsible for testing. IS also notifies user representatives from other departments if a patch could effect their area as well so they can perform their own testing. When all affected users have signed off, the patch is scheduled for application in our production system.
User representatives from each functional area meet with IS biweekly to discuss patches and other development. Patches are routinely moved up and down in priority and rescheduled as needed.
Mark Petereit HRIS Analyst McLeod Health Florence, South Carolina
Before applying CPTs it is good to get a patch preview. This will show you all the forms that are affected by that patch. This would help you with your testing of the patches.