AltSync Setup
Prerequisites
-
To set up the AltSync feature, you should have the following knowledge:
-
To set up the AltSync feature, you need the following licenses:
-
To set up the AltSync feature, you must:
-
To set up the AltSync feature, you need the following permissions:
-
System permissions:
-
API Enabled
-
Author Apex
-
Customize Application
-
Manage Profiles and Permission Sets
-
View Setup and Configuration
-
The AltSync unmanaged package available with version 1.309 or greater replaces the former FX5AltSync package, which is deprecated. |
About AltSync
The AltSync function allows for customizable sync rules and works in conjunction with the Sync engine.
Read more about how AltSync works. |
An AltSync solution can be quickly installed from an unmanaged package. Or, AltSync can be installed manually for greater customization.
AltSync Package
Basics
The quickest way to set up the AltSync feature is to install the AltSync unmanaged package.
The AltSync package gives you instant control over the key transactional data that syncs to FieldFX Mobile.
Transactional data includes records on any of the following objects: Job, Ticket, Ticket Item, Ticket Log, Price Book, Quote, Quote Item, FX Forms, and any master-detail children of FX Forms. |
You can customize AltSync for objects, depending on the version of Sync.
How It Works
-
Utilizes three custom fields on various objects:
-
AltSync checkbox: Boolean field to indicate whether the record should sync to mobile.
The flag can be set to
True
orFalse
manually, by an AltSync Trigger during day to day transactions, or by the nightly AltSync processes.Child transactional data objects should use lookups to their parent object to define the flag.
For example, Ticket Items should look to the parent Ticket.
Tip: The
AltSync__c
field works in conjunction with theSync__c
field. When both fields exist on the object, both fields must evaluate toTrue
for the record to sync to mobile devices. -
AltSyncSource field: A text field with a value of either None or Linked.
Value set by Trigger or process when the record is referenced by another record.
For example, the value is set to Linked on an Account when a Ticket for the Account has activity.
-
AltSyncStamp field: Time stamp when the AltSync flag is set to
True
.This datetime stamp is used as an expiration date to determine whether the AltSync flag for the record needs to change to
False
.
-
-
The AltSync package adds an AltSync flag checkbox, AltSyncStamp datetime field, and AltSyncSource text field to four objects:
-
Account
-
Contact
-
FX5__Equipment__c
-
FX5__Well__c
-
-
the AltSync package adds an
AltSync__c
field to each of the following objects, and includes a formula for most of them:Object Formula Impact Account
None unless the AltSync flag is set to True by a Trigger, the nightly AltSync process, or a manual change to the AltSync flag.
Contact
None unless the AltSync flag is set to True by a Trigger, the nightly AltSync process, or a manual change to the AltSync flag.
Crew Planning
FX5__Job__r.AltSync__c
Crew planning records sync when the job syncs
Equipment
None unless the AltSync flag is set to True by a Trigger, the nightly AltSync process, or a manual change to the AltSync flag.
Equipment Planning
FX5__Job__r.AltSync__c
Equipment planning records sync when the job syncs
Job
FX5__Price_Book__r.AltSync__c && FX5__Sync__c
Jobs sync when it is syncable (flag controlled by a Status Workflow trigger) and the job’s price book syncs
Price Book
FX5__Is_Active__c
Price books sync when they are active
Price Book Item
FX5__Price_Book__r.AltSync__c
Price book items sync if its price book syncs
Quote
FX5__Status__r.FX5__Sync__c
Quotes sync when in a syncable status
Quote Item
FX5__Quote__r.AltSync__c
Quote items sync when the quote syncs
Ticket
FX5__Job__r.AltSync__c && FX5__Sync__c
Tickets sync when the ticket is syncable and the job syncs
Ticket Checklist Steo
FX5__Ticket__r.AltSync__c
Ticket checklist steps sync when the ticket syncs
Ticket Item
FX5__Ticket__r.AltSync__c
Tickets items sync when the ticket syncs
Ticket Log
FX5__Ticket__r.AltSync__c
Ticket Logs sync when the ticket syncs
Well
None unless the AltSync flag is set to True by a Trigger, the nightly AltSync process, or a manual change to the AltSync flag.
Installing the AltSync Package
-
Contact LiquidFrameworks Support to get an installation link for the AltSync package
-
Open your email app
-
Change the org-wide sharing defaults:
-
From Setup, enter "sharing" in the Quick Find box, then select Sharing Settings
-
Under Organization-Wide Defaults, click Edit
-
Locate Job in the list
-
In Default Internal Access, select "Private"
-
Locate the second Price Book object in the list
-
In Default Internal Access, select "Private"
-
Click Save
-
Click OK
You will receive an email confirmation once your sharing settings recalculate.
-
-
Review the following objects for an existing AltSync field and delete the field if found:
-
Account
-
Contact
-
Crew Planning
-
Equipment
-
Equipment Planning
-
Job
-
Price Book
-
Price Book Item
-
Quote
-
Quote Item
-
Ticket
-
Ticket Item
-
Well
Caution: If you do not delete an existing AltSync field on one or more of these objects, the FX5AltSync package cannot install.
-
-
Install the AltSync unmanaged package:
-
Click the installation link you received for the AltSync package
The installation page opens
-
Under What if existing component names conflict with ones in this package, select Do not install
-
Select Install for All Users
-
Click Install
-
Click Done
You will receive an email confirmation once the installation finishes
-
-
Update permissions:
-
Grant all users Read access to the AltSync checkbox on the following objects:
-
Account
-
Contact
-
Crew Planning
-
Equipment
-
Equipment Planning
-
Job
-
Price Book
-
Price Book Item
-
Quote
-
Quote Item
-
Ticket
-
Ticket Item
-
Well
-
-
Grant all users access to every LFW Apex class
-
-
Update page layouts:
-
Add the AltSync checkbox to page layouts for the following objects:
-
Account
-
Contact
-
Crew Planning
-
Equipment
-
Equipment Planning
-
Job
-
Price Book
-
Price Book Item
-
Quote
-
Quote Item
-
Ticket
-
Ticket Item
-
Well
-
-
Custom AltSync Checkboxes
Adding an AltSync Checkbox
-
Open the Settings page for the object
-
Add the AltSync checkbox:
-
Under Custom Fields & Relationships, click New
-
Select Formula
-
Click Next
-
In Field Label, enter "AltSync"
-
Under Formula Return Type, select "Checkbox"
-
Click Next
-
In AltSync (Checkbox), enter a formula to use
Example 1. AltSync on an Equipment objectUse the following formula for an AltSync checkbox on the Equipment object. This formula configures the Sync Engine so that equipment records don’t sync when they have Out of Service selected.
FX5__Out_of_Service__c = false
-
Click Next
-
Click Visible twice
-
Click Next
-
Select the page layouts on which to include the checkbox
-
Click Save
-
-
Grant permissions for the AltSync checkbox
Activity Based Sync
How it works
Sync Lookup Settings manages AltSync flags on lookup records by the activity on transactional data.
Transactional data includes records on any of the following objects: Job, Ticket, Ticket Item, Ticket Log, Price Book, Quote, Quote Item, FX Forms, and any master-detail children of FX Forms. |
Sync Lookup Setting records in Custom Metadata Type specify how many days to detect activity for a lookup record.
The settings also determine how many days the lookup record’s AltSync flag should remain True
after the last detected activity for hte record.
The default Timespan value specifies 30 days to detect activity and keep the lookup record AltSync as The process to review and adjust AltSync flags on lookup records runs nightly. |
Sync Lookup Settings exist for
-
Account
-
Contact
-
Equipment
-
Well
Modify the Timespan Values for Sync Lookup Records
-
From Setup, enter
Metadata
in the Quick Find box, then click Custom Metadata Types -
Click Sync Lookup Setting
-
Click Manage Sync Lookup Settings
-
Click Edit next to the object with the Timespan Days value you want to change
-
Enter the desired Timespan Days value, then click Save
Add Additional Lookup Data Objects to Sync Lookup Settings
-
You can enable additional objects for the Sync Lookup Manager to manage the AltSync flag based on transactional lookup activity.
-
The object should exist as a lookup from a transaction data object (see the list in the Note above).
-
On the lookup object, confirm that the following fields exist or create them:
-
AltSync__c: Boolean field to indicate whether the record should sync to mobile
The flag can be set to
True
orFalse
manually, by an AltSync Trigger during day to day transactions, or by the nightly AltSync processes.Child transactional data objects should use lookups to their parent object to define the flag.
For example, Ticket Items should look to the parent Ticket.
-
AltSyncSource__c: A Text field with a value of either None or Linked
Value set by Trigger or process when the record is referenced by another record.
For example, the value is set to Linked on an Account when a Ticket for the Account has activity.
-
AltSyncStamp__c: Datetime field set when the AltSync flag is set to
True
This datetime stamp is used as an expiration date to determine whether the AltSync flag for the record needs to change to False.
-
-
In the Sync Lookup Settings Custom Metadata Type, add a record for the lookup object:
-
From Setup, enter
Metadata
in the Quick Find box, then click Custom Metadata Types -
Click Sync Lookup Setting
-
Click Manage Sync Lookup Settings
-
Click New
-
Make the following entries:
-
Label: Name or description of the lookup object
-
Sync Lookup Setting Name: Accept the default value Salesforce generates
-
Lookup Type: API name of the lookup object
-
Timespan Days: Number of days that lookups should be detected and that should pass after the last detected activity before the record’s AltSync flag is set to
False
-
-
Click Save
-
Recommended Reading
-
AltSync
Learn how the AltSync feature works