Security Settings

Named Credentials

This section of the Security section for a Salesforce org keeps named credentials secure and a central configuration storing:

  • Endpoint URL of an external system

  • Authentication method such as Basic, Auth, OAuth 2.0

  • Optional custom headers

  • Credential storage so usernames and passcode aren’t hardcoded in Apex

Use named credentials instead of hardcoding login details in code or logic for FieldFX (or other integration) by its label name.

How Named Credentials Work in FieldFX

FieldFX uses Salesforce Named Credentials whenever it needs to communicated outside Salesforce. These are typical use cases:

Use Case What Named Credentials Do How Named Credentials Help

Syncing with FieldFX Services
(Sync Services, Job Data, Pricing)

FieldFX Mobile and Back Office sometimes sent/receive data external FieldFX servers or APIs.

This securely stores the authentication info (like API keys or tokens) to those FieldFX web services.

Integrations with Other Systems

Connecting FieldFX with EPR, accounting, or inventory systems through APIs

Defines the endpoint URL and how Salesforce should log in (OAuth, username/password, or certificate).

Custom Callouts or Middleware

Custom Apex or middleware

The integration references the Name Credential instead of embedding the password directly in code.

Sync Profile Manager Admin Tool (New)

When it connects the sync tool to manage users and filters.

If it communicates with a secure FieldFX endpoint, the connection is validated using Name Credentials.

Benefits

Security

Credentials are encrypted and never visible to standard users or exposed in Apex code.

Simplified Maintenance

You can updated passwords or tokens in one place without editing code or integrations.

Centralized Control

Admins manage all external connection settings from Setup.

Auditing and Compliance

Salesforce tracks credential changes and usage, helping with audits and compliance standards.

Create a Named Credential

  1. In your org, access Setup.

  2. Search for Named Credentials using the Quick Find box.

  3. Select Named Credentials.

    At the Named Credentials view, you can see the named credentials for the org. If there aren’t any, none will appear.

  4. Click New.

  5. Complete the following fields:

    These values are example and may differ from your org’s settings.
    Field Example Value Description

    Label

    FieldFX Mobile Sync

    The display name for this credential.

    Name

    FieldFX_Mobile_Sync

    API Name used in code or integration.

    URL

    https://fieldfxsync.liquidframewords.net

    The endpoint URL.

    Enabled for Callouts toggle

    On

    Allows the Named Credential (and any linked External Credential) to be used for outbound API requests from Salesforce or FieldFX. When toggled on, Salesforce can securely send data or make requests to external system using that credential. When toggled off, all callouts through it are blocked.

    Authentication

    External Credential
    (Required)

    AWS_S3_External_Credential or
    FieldFX_Mobile_API_Credential

    Ensures that any connection or integration uses a Salesforce-managed External Credential for authentication instead of stored usernames or passwords. This adds a security layer by requiring all external access to be authenticated through Salesforce’s secure credential framework.

    Client Credential
    (Required)

    my_intergration_app_clientid_12345

    Stores the identifier (Client ID or key) used by FieldFX or Salesforce to authenticate with an external system through OAuth 2.0 or API-based integration. It tells the external service which application is making the request.

    Callout Options

    Generate Authorization Header
    checkbox

    checked or unchecked

    Generate an authorization header and apply it to each callout that references the name credential.

    Allow Merge Fields in HTTP Header
    checkbox

    checked or unchecked

    Use credential fields as formula fields in named credential custom headers, external credential custom headers, and Apex HTTP headers.

    Allow Merge Fields in HTTP Body
    checkbox

    checked or unchecked

    Allow Apex code to construct the callout’s HTTP body with credential fields available as formula fields.

    Outbound Network Connection

    checked or unchecked

    Outbound network connections send requests through a channel that you configure. Private connections don’t use the public internet.

    Managed Package Access

    Allowed Namespaces for Callouts

    https://api.fieldfx.com

    List of namespaces that identifies the managed packages which are allowed to make callouts using this named credential.

  6. Click Save.

  7. Click Test Connection (if available) to verify that Salesforce can reach the endpoint.

    If successful, Salesforce securely stores your credentials for reuse.

    When FieldFX (or custom Apex integrations) reference your Named Credential directly.

  8. If needed, assign permissions ensure the integrations user has permission to use the Named Credential and the FieldFX Integration Profile includes proper API permissions.

Recommended Reading

For more information, see:

FieldFX Documentation Salesforce Documentation

  • .