Submit your Suggestions for Vista Web

When a document is used across a large number of hiring (e.g., 100) profiles in the onboarding system, there are currently two methods of updating said document:

1. Modify the existing document and/or custom task

2. Create a new document and/or custom task from scratch

The upside of solution 1 is that if the changes are simple, you can make them within the record, and have the changes update instantaneously across all 100 hiring profiles. The problem is that you are changing a document and/or custom task that is in a live environment - severely limiting your ability to test the changes being made before they are rolled out. If you make a mistake during the update, things can go sideways very quickly, and rolling the changes back is not always simple.

The upside of solution 2 is the exact opposite - you are free to test as much as you need. The downside being - once you have it complete, you then have to manually deactivate the old document and reassign the new document / custom task to all 100 hiring profiles all over again (and hope you don't miss one along the way).

If you were able to create new version numbers of the same documents - linked to a single record, it would solve this dilemma. For example:

• Version 1 of my application is live.

• In order to update the document, I access Version 1 through the Hiring Process Builder and create a new Version 2 - the two records are linked, but Version 1 remains active, while Version 2 remains unassigned to any hiring profiles.

• I finalize my work on Version 2 and, once satisified with my testing, change the "live" version to Version 2.

• Version 2 replaces Version 1 across all hiring profiles.