We have a custom object called a Peer Review. A peer review object consists of a peer review ID, as well as several custom fields. A user can currently create a NEW peer review, DUPLICATE an existing peer review. However, we would like the user to also be able to create a REVISION of an existing peer review. This action would need to be similar to the revision control of a Job Plan or a Purchase Order, where the user would choose to "Revise Peer Review", and Maximo would duplicate the Peer Review with the same Peer Review ID, increment the revision number (which we will need to add), and place the revised Peer Review into some sort of Pending Revision status, until the user makes the necessary changes and "ACTIVE"s the new revision. At that point, the previous revision of the peer review would change to a "REVISED" status.

I don't mind if we need to add this to an automation script and activate it with a push button if that's what needs to happen.

I know this sounds like a tall order, but I'm curious is there are any tips or existing functionality that I can replicate?

Thanks!

Mark

I'm not a programmer, so I'm missing some details here. This is just theory and have not actually implemented this type of solution before.

When you duplicate a revised PO the PO and POLINE table will not copy over the revision rows and the revision is back to 0. What you're describing sounds like something in a single table and a revision is really a duplicated record with a custom field that will increment the duplicated record by 1. The Peer Review ID can not be a unique key in the database as you stated you want the ability to have duplicate Peer Review IDs. That may require a separate field that is the unique key for the table. When you duplicate a record, you can run automation script logic to increment the peer review id by 1, change the status, and anything else you want before the duplicated record is saved.

sshull explains more about duplicating records:

https://www.ibm.com/mysupport/s/question/0D50z000060eTc1CAE/duplicate-service-request-with-some-additional-functionality?language=en_US

As part of your duplication logic, you can increment the revision num by 1 and change the status to your desired status...

https://bportaluri.com/2019/10/automation-scripts-new-save-duplicate.html

PO revisioning will be the best start for this. Add a new attribute REVISIONNUM, a sigoption "REVISE", non persistent object similar to POREVISION to enter comments for revising, automation script to increment revision number. Look into POAppBean and PO.class to start with