How to audit / track field level data changes to Records, require comments, and display changes?

Question

Here's what I'd like to do: 
 1. Track changes to one specific date field within a Record 2. Require a comment whenever the date field is updated via an existing Related Action 3. Display the tracked changes and comments inside the Record 
 To provide some context, the record in question has multiple sites associated with it, each with a date (future/scheduled) for monitoring. I'd like to be able to know/see each time this date is updated and why (comment), although it can be updated in two places: via the Update Sites related action, OR inside of a process (Once monitored on or before the scheduled date, User Input Task requires a new date to be set before process completes and then updates the record). 
 I'm not sure how to first, require the comment when editing just this one field inside the record, and second, taking this field change and comment and displaying them somewhere. Thanks for any suggestions!

ChristineH · Accepted Answer

I would create a history table (historyID (pk), fieldname, newValue, comment, cratedate, created by). Create a cdt to match and put in datastore. 
In your process, called by related action, add comment field to form and save to comment in new pv of type the new cdt. add a script task to then populate other fields (minis id) from other cdt that has new date and process details like initiator and date with now(). Then write to ds to persist data. 
Hope that makes sense.

Jamal Case · Answer

1. To track changes that's made to a specific field, you can just write these changes to a history log table after the form is submitted. 
 2. You can do some logic to show a paragraph field that's required for the comments when the date field is changed. Here's a code snippet for an example: 
 /*17.2*/ 
 =a!formLayout( 
 contents: { 
 with( 
 local!orignalDateField:index(rule!TEST_getFormDetails(ri!id).data,"dateField",{}), 
 a!columnsLayout( 
 columns: { 
 a!columnLayout( 
 contents: { 
 a!sectionLayout( 
 label: "Example", 
 contents: { 
 a!dateField( 
 label: "Date Field", 
 labelPosition: "ABOVE", 
 value:ri!dateField, 
 saveInto: ri!dateField, 
 refreshAfter: "UNFOCUS", 
 validations: {} 
 ), 
 a!paragraphField( 
 label: "Reason for change", 
 labelPosition: "ABOVE", 
 value:ri!comments, 
 saveInto: ri!comments, 
 refreshAfter: "UNFOCUS", 
 showWhen: local!orignalDateField<>ri!dateField 
 ) 
 } 
 ) 
 } 
 ) 
 } 
 )) 
 } 
 ) 
 3. Write a query to pull the data from the history log table. 
 Hopefully this can be a starting point for your implementation.

vijayd · Answer

I believe you will be using a process model on back of a related action. I would recommend to create a history table and track all the changes you want to log into that history table and then create a view in the record to display all the changes in a grid.