Sync Rules for Attachments

Basics

Attachments sync between FieldFX Back Office and FieldFX Mobile based on a number of rules.

The following flowcharts illustrate the sync rules for Attachments.

FieldFX Back Office → FieldFX Mobile

Attachments sync to FieldFX Mobile based on the following rules:

Criteria Question Yes No

Is the file attached through Chatter?

Proceed to the next criteria question

Attachment does not sync

Is the file tagged with "SyncToMobile" flag?

Proceed to the next criteria question

Attachment does not sync

Does the Job/Ticket sync?

Proceed to the next criteria question

Attachment does not sync

Does the User follow the job/ticket?[1]

Attachment syncs

Attachment does not sync

Flowchart of Back Office to Mobile attachment sync criteria
Figure 1. This flowchart shows the rules for when attachments sync from Back Office to FieldFX Mobile

FieldFX Mobile → FieldFX Back Office

Attachments sync to FieldFX Back Office based on the following rules:

Criteria Question Yes No

Has the parent record synced to Back Office?

Proceed to the next criteria question

Attachment syncs during the next sync[2]
(when under the hourly Chatter API limit[3])

Is there an active Internet connection?

Proceed to the next criteria question

Attachment syncs during the next sync[2]
(when under the hourly Chatter API limit[3])

Is the User under the hourly Chatter API limit?[3]

Attachment syncs immediately[2]

Attachment syncs during the next sync[2]
(when under the hourly Chatter API limit[3])

Flowchart showing decision process for attachments syncing from FieldFX Mobile to Back Office
Figure 2. This flowchart shows the rules for when attachments sync from FieldFX Mobile to Back Office

1. Users follow their jobs and tickets automatically if you select Auto Follow Job and Ticket in the FX Settings.
2. If you attach a file to a record and sync twice, the file no longer displays in FieldFX Mobile and only displays in FieldFX Back Office.
3. There is a per user, per hour limit for Chatter API requests. Salesforce no longer communicates this limit.