Hi @amybillmayer,
Hmm. You got me thinking...
Although not (yet) listed as a standalone entry in our www.atappstore.com catalog, as one of the first steps in our Workfront Merge (or Split) service, we run our Merge Validator solution to compare the Source instance against the Target instance in order to (literally) highlight any differences using the Excel file it generates.
By default, the Merge Validator includes The Basics (i.e. Overview, Statuses, Priorities, Severities, Job Roles, Expense Types, Hour Types, Groups, Teams, Schedules, Parameters, Parameter Groups, Custom Forms, Companies, Portfolios, Programs, and Projects). Each object has its own tab in the Excel File comparing the Source data on the left, the Target data on the right, with any differences (missing or changed) highlighted in yellow. Here's an example of the Priorties tab:
Once we've conducted a Workfront Merge (or Split), we run the Merge Validator again to see "what made it", but in addition to The Basics, also turn on some other options...two of interest that twigged when I read your requirements being Template Task Dates and Template Assignments. Here's what it looks like, with those options selected:
Following this line of thought, I hopped into my preview environment (which was sync'd over the weekend from my production environment) and made a few changes to the Templates (namely deleted one, renamed one, changed a duration on a Template Task, deleted a Template Task, and added a Template Task with Assignments). I then ran the Merge Validator with the settings above to capture the data (and highlight the data) in a similar fashion.
Here's where I'm going.
I suspect that like you, many organizations would be interested in monitoring changes within Workfront over time for auditing / regulatory purposes. For such organizations that also have a client refreshable Sandbox environment (e.g. SB02), I'm imaging the following:
- On Nov 1, refresh prod to SB02
- On Nov 2, run the Merge Validator with the options of interest "on" to confirm that prod = SB02 (i.e. "no highlighting")
- During November, carry on with business as usual in prod
- On Nov 30, run the Merge Validator again to highlight what has changed for the month, then "sign off and officially file" as the organization sees fit
- On Dec 1, rinse and repeat
If you or any others reading are interested in repurposing the Merge Validator in this manner, I'd be happy to chat further via doug.denhoed@atappstore.com.
Regards,
Doug