Confiforms Audit Log

[Rayman Bacchus]

Today, my question concerns the IFTTT macro for  Audit

I created three IFTTT's onCreated, onModified, onDeleted to track what was done under a specific createdid (at least this is what I think the Audit function will do)

Is there a way for me to show the Audit Log on a tab in a Confluence Page (I use Deck of Cards, and Card for the Confluence page).  So on the last "card"....I want to show the audit history of a particular record.

I want something like this

Field, UpdatedData, OldData, DateofChange, Event

Is this even possible?  I don't see anywhere in Audit where olddata, updateddata is stored.

This is what I currently have, but although I updated FraudApps - and it's not showing in the log

[Alex Medved _ConfiForms_ · Accepted solution]

Have a look at this page https://wiki.vertuna.com/display/CONFIFORMS/Using+new+Audit+IFTTT+action

created field in the audit log form will show the "DateofChange", and the audit log form has all the fields that you have in your original form

In addition it has two more fields

_event

_ref

To get an event and reference to entry (in original form)

[Rayman Bacchus]

As always, THANKS A TON Alex.  Your knowledge is very appreciated.

One question - is there a field in the audit_log that says WHAT field changed? I was thinking a hasChanged() but do I need to do that for all fields in the form?

[Alex Medved _ConfiForms_]

The audit log logs every change unless you make it configurable via condition

[Rayman Bacchus]

THis is very close to what I like to see:

I was hoping to have Event, Created timestamp, Last Updated By, FieldThat Changed, old field data, new field data.

However, I don't think that is possible.  I know there is a _previousState command but I'm not even sure how to use that command and I don't think it works in a TableView.  I cant have the field = _previousState.[entry.fieldsthatchanged]

[David C]

@Alex Medved _ConfiForms_ Would you be able to assist with how @Rayman Bacchus was able to pull the IFTTT event field information (what syntax was used)? I have looked all throughout the Confiforms wiki and I can't figure out how to successfully pull the universal event information (onCreated, onModified, etc.)

[Alex Medved _ConfiForms_]

Hi @David C 

Have you looked at this page https://wiki.vertuna.com/display/CONFIFORMS/Using+new+Audit+IFTTT+action ?

There is literally not much to configure - just to add an IFTTT of the Audit type and decide what event it should be listening (or add multiple if you want to cover multiple events)

Alex

[David C]

Yes I have successfully created the audit tableview/list view and added a Create/Modify/Delete IFTTT audit. I just don't know the syntax to pull the value into the view.

[Alex Medved _ConfiForms_]

Hmm, same as with "normal" forms, just the name of the form is with _log in the name

So, if you form name is myform then the audit log form will be myform_log

Same fields as in the original form with 2 extra virtual fields in the audit log form called (field names)

• _ref
• _event

[David C]

That seemed to do the trick with _event. One final question, I am trying to full remove the test data I am inputting into the original form audit history form and even deleting the original submission, it is still showing in the audit log. Is there a way to remove the couple from the audit log?

[Alex Medved _ConfiForms_]

Probably the best option is to use REST API to remove the data from an audit log form

https://wiki.vertuna.com/display/CONFIFORMS/ConfiForms+Server+REST+API+version+1#ConfiFormsServerRESTAPIversion1-DeleteConfiFormsEntriesbyfilter

[David C]

Thanks Alex, I just added in a simple field that determines if they are a test candidate or not and then filtered via that in the list view. One final question on this topic:

For large scale data sets is there a way to only show the information that has changed dynamically rather that displaying all fields:

Such as the below:

Where change information will show the field value (obviously all form fields would need to be added to said field, but only show changed information in the user UI similar to the hasChanged function?

[Alex Medved _ConfiForms_]

As any ConfiForms IFTTT action you can make it to run conditionally, and only when you want - for example, tracking for changes only the certain fields.

This is done by defining the condition parameter in the macro 

[David C]

I want the IFTTT macro to run on all changes (therefore no parameters set within the macros) but I only want the list view UI to show the individual Field macros when they change, otherwise they would not display to the user.

Line 1: onModified: "Change information" field shows the email field changed.

Line 2: on Modified: "Change information" shows the candidate name and phone number because those changed on modification

Line 3: onDeletion: no fields are shown because none of the fields changed upon that IFTTT update 

Etc.

[David C]

[Alex Medved _ConfiForms_]

There is no easy way to show "only what has changed"

The full log is created - all the old values are stored

[Rayman Bacchus]

It is for this reason I never really implemented the Audit Log for my intakes.  I know the audit log is there if I need it, but I wanted to show it in a tab on a Confluence page.  However, since it showed me everything instead of only the fields that changed I decided it would not be worth implementing for my process.

[David C]

@Alex Medved _ConfiForms_ would it be possible to create a "audit" field and then use an IFTTT to "Update the Confiforms Entry" of the "audit" field by daisy chaining an IF statement that would record the field entry if it hasChanged, otherwise skip such as:

IF(hasChanged(FieldA),FieldA, IF(hasChanged(FieldB),FieldB,....

etc.

[Alex Medved _ConfiForms_]

What will this give? I mean what is the intended result?

The idea of the audit log is to log the state of the record BEFORE the update. That is why it logs ALL the fields. So, you have an exact picture of how the record looked like before the update.

[David C]

In the audit tutorial provided it is clear with 2-3 fields what has generally changed. However for forms such as the one we have with 30-50 fields per record (depending on navigation through built in logic) the table view can be very daunting to understand what has changed. What are your thoughts on the IF recommendation?