FieldFX eForm Setup

Introduction

In FieldFX, you can must setup a Parent eForm or a Child eForm, underneath the parent.

Complete these tasks in order. Before you begin, review the Guidelines.

Prerequisites

To setup and use FieldFX eForms, you need to:

Have these user licenses Have these permissions Complete these tasks
and review these topics
before continuing
For eForms to appear when viewing Jobs or Tickets in the FieldFX Mobile App, the eForm object must be added to the object’s page layout - Related List section.

Guidelines

When setting up FieldFX eForms, keep in mind these details about the Master-Detail, SyncID, and Job Share Trigger fields:

Master-Detail Field

SyncId Field

Job Share Trigger Field

Use the Job Share Trigger to download only the child records you want in FieldFX Mobile that are associated with a parent object.

Example 1. Job Share Trigger

If there are 5 JSA (Job Safety Analysis) records associated with one Job record in mobile, only the 5 JSA records that is associated with the Job will be downloaded to mobile, not all records in the JSA object.

You should have for the Job Share (Job_Share__c) field at least Read permission in the form object in a profile or in a permission set that is associated with a Fieldfx mobile user.

Enable Job Share Trigger Field

  1. Ensure that you have the Job Share Trigger added to each of your eForm Config records.

  2. Ensure that you have read permission and have the Doc Share field populated.

  3. Under Setup > Object Manager > Form_Name > Field & Relationships, ensure there is a Job_Share__c field.

    Form_Name is the name of your form.

    The Job_Share__c field must be a lookup data type field to the job.

  4. Under Setup > Object Manager > Form Name > Triggers, ensure there is a trigger called <form name>Trigger_FX5Auto.

    Form_Name and <form name> is the name of your form.

    If there is a Job_Share__c field, the trigger is automatically created.

Example: Job Safety Audit (JSA) eForm - Typical Fields

For a JSA form in the oil and gas industry, the eForm would typically include the following fields per the intended purpose:

All these fields aren’t necessarily needed for a JSA form.
Category Suggested Fields

General
Information

  • Job Title

  • Job Location

  • Date & Time

  • Company Name

  • Customer Name

  • Work Order or Job Number

  • Project or Lease Name

  • Crew Members & Roles

  • Supervisor/Foreman Name

Hazard
Identification

  • Work/Task Description

  • Job Steps/Phases (with each step detailed)

  • Potential Hazards for Each Step

    • Example: Falls, fires, explosions, toxic exposure, etc.

  • Hazard Security (Risk Assessment Level)

Control Measures
& Mitigation

  • Personal Protective Equipment (PPE) Required

    • Example: Hard hats, gloves, fire-resistant clothing, respirators, etc.

  • Safety Procedures & Precautions

  • Engineering/Administrative Controls

  • Emergency Procedures (Evacuation, First Aid, etc.)

  • Required Permits (Hot Work, Confined Space, etc.)

Equipment & Tools

  • Tools & Equipment Used

  • Inspection Requirements

  • Lockout/Tagout (LOTO) Requirements

Signatures
& Approvals

  • Completed By (Technician/Operator)

  • Supervisor/Manager Approval

  • Crew Member Signatures

  • Acknowledgment Date & Time

FieldFX eForm Configurations

An FieldFX eForm configuration controls when an FieldFX eForm is available for use.

You must add an FieldFX eForm configuration for every basic FieldFX eForm.

Child RX Forms use the FieldFX eForm configuration for their parent FieldFX eForm.

Add an FieldFX eForm Configuration

Click to expand
  1. Access FieldFX Back Office.

  2. Open the eForm Configs tab.

  3. Click New.

  4. In Key SObject, select:

  5. In eForm SObject, for example, enter JSA__c for the API name of the FieldFX eForm object.

    The sObject name, which is case-sensitive, must be the object’s API name.
  6. Specify when to use the FieldFX eForm:

    If you don’t select one of the following options, users can add the FieldFX eForm to any job / ticket.
    Section Field Action

    Information

    Key SObject Record Type

    Select a record type to use the eForm for that record type.

    Filtering

    Account

    Select a customer to use the eForm for that customer.

    Office

    Select an office to use the eForm for that office.

    Segment

    Select an office to use the eForm for that office.

    Price Book

    Select a price book to use the eForm for jobs/tickets linked to that price book.

    If the Price Book field isn’t available, you may have to add it to the eForm Config Page Layout.
  7. Click Save.

  8. Configure sharing settings to grant access to the FieldFX eForm configuration.

Continue with Record Types.

Record Types

You can Set up record types if you need to complete eForms differently based on a certain aspect of a job.

For example, if needed, you can add Downstream, Midstream, and Upstream record types for an FieldFX eForm. The user would complete these differently at downstream, midstream, and upstream work sites.

How Record Types Appear in FX Mobile How Record Types Appear in the FieldFX Mobile App

Screenshot of different record types for an FieldFX eForm in FX Mobile

When you add record types, add a page layout for each record type. This allows you to display different fields on each version of the FieldFX eForm.

Add Record Types for an FieldFX eForm

Click to expand
  1. Access FieldFX Back Office.

  2. Switch to Salesforce Classic.

  3. From Setup, enter object in the Quick Find box, then select Object Manager.

  4. Open the FX Form object.

  5. Under Record Types, click New.

  6. In Existing Record Type, select "--Master--".

  7. In Record Type Label, enter the record type.

  8. Select Active then click Next.

  9. Click Save & New.

  10. Repeat these steps for other record types as needed.

  11. Click Save to finish and then click Back to Custom Object at the top of the page.

Add Page Layouts for Record Types

Click to expand
  1. Access FieldFX Back Office.

  2. Switch to Salesforce Classic.

  3. From Setup, enter object in the Quick Find box, then select Object Manager.

  4. Open the FX Form object.

  5. Under Record Types, click New.

  6. In Existing Record Type, select "--Master--".

  7. In Record Type Label, enter the record type.

  8. Select Active then click Next.

  9. Click Save & New.

  10. Repeat these steps for other record types as needed.

  11. Click Save to finish and then click Back to Custom Object at the top of the page.

Assign Page Layouts to Record Types

Click to expand
  1. Access FieldFX Back Office.

  2. Switch to Salesforce Classic.

  3. From Setup, enter object in the Quick Find box, then select Object Manager.

  4. Open the FX Form object.

  5. Under Record Types, click New.

  6. In Existing Record Type, select "--Master--".

  7. In Record Type Label, enter the record type.

  8. Select Active then click Next.

  9. Click Save & New.

  10. Repeat these steps for other record types as needed.

  11. Click Save to finish and then click Back to Custom Object at the top of the page.

Grant permission to use the record types

Click to expand
  1. From Setup, enter permission in the Quick Find box, then select Permission Sets.

  2. Open a permission set.

    If the permission has a Namespace of FX5, it is part of the FieldFX Managed Package and is locked and can’t be edited.
  3. Under Apps, click Object Settings.

  4. Open the FieldFX eForm object.

  5. Click Edit.

  6. Under Record Type Assignments, select the record types.

  7. Under Object Permissions, select Read, Create, and Edit

    For FX Forms, if you didn’t select Unique when adding the SyncId field, grant View All permission for the FX Form object.
  8. Under Field Permissions, grant Read and Edit permission for every field.

  9. Click Save.

  10. At the top of the page, click the arrow next to Object Settings and select Visualforce Page Access.

  11. Click Edit.

  12. Add the Visualforce page for the FX Form or Child eForm to Enabled Visualforce Pages.

  13. Click Save.

  14. Repeat these steps for other permission sets as needed.