Here is a summary of the sync process from the perspective of the audit log
Create a pre-sync upload audit log entry.
Send the upload packet to the post process.
Mobile deletes the upload queue and proceeds, although the logout button is disabled.
Post sends each event to SFDC individually.
When post completes it either creates an Upload Complete Audit log entry or an Upload Failed audit log entry
The logout button on Mobile re-enables.
Defect card #5706 was caused by something going wrong during step#4. Step #5 never happened.
The proposal is to make these changes:
Change the managed package so that an audit log entry is editable.
BR: this can be done via the AUditLogTrigger class and the “allowedObjectsOverride” which allows you to provide fields that can be updated via “PackageObjectHandler.EnforceBuiltInFieldsReadOnly(objs, oldMap, allowedObjectsOverride);” Requires a MP change...
Modify the sync process above so that step #5 does not create a new audit log entry. Instead, it updates the pre-sync upload audit log entry.
We need to determine the best way to educate sys admins on the new process.
Does Packet Viewer need to change?
BR: yes – PV receives the new AuditLogId and updates the original AL with the new ID and marks it as Cleared/Resolved. It also passes the current AL ID to post which tags the new AL with the originating AL
Test Plan
Stories
{{ table query: SELECT Number, Name, Owner, Status, 'Story Points' WHERE Type = Story and Feature = THIS CARD ORDER BY Status }}
Mingle Card: 5946 This card originated from defect card #5706
Here is a summary of the sync process from the perspective of the audit log
Defect card #5706 was caused by something going wrong during step#4. Step #5 never happened.
The proposal is to make these changes:
Test Plan
Stories
{{ table query: SELECT Number, Name, Owner, Status, 'Story Points' WHERE Type = Story and Feature = THIS CARD ORDER BY Status }}