How Does Pulsar Process Global Variables in Validation Rules?

When building validation rules in Salesforce, global variables play an important role. But when using Pulsar, there are some limitations to keep in mind—especially when working offline.

Which Global Variables Are Supported By Pulsar?

Pulsar supports a limited set of global variables during validation rule processing. These are:

• $API.Session_ID

• $API.Enterprise_Server_URL_XXX

• $API.Partner_Server_URL_XXX

• $Label.<Custom_Label_Name>

• $Profile.Id

• $Profile.Name

• $Setup.<Custom_Setting_Name>

• $User.<fieldName>

• $Organization.Id

• $RecordType

Why It Matters

Understanding which global variables Pulsar supports helps avoid silent failures. If a rule fails during sync, users may assume their data was validated and saved correctly when it wasn’t.

By limiting global variable use to the supported list, you can ensure validation works both offline and online—preserving data accuracy and system integrity.

What Happens If I Use Unsupported Global Variables?

If you use any other global variables not listed above, Pulsar won’t evaluate the validation rule. The validation rule will be skipped during the record saving process. Instead, the data will be saved locally on the device only. The next time the user is online, Pulsar will sync the data to Salesforce, and the validation rules may take effect on the server instead.

This behavior can lead to inconsistencies, especially in environments where data needs to be validated offline before saving. For this reason, avoid using unsupported global variables.

Can I Still Use Salesforce Validation Syntax?

Yes. But if you stick to validation rules in Salesforce, make sure you only reference the supported global variables listed above.