Understanding system pipeline fields

The system includes predefined pipeline fields that capture essential details for managing and tracking records across different pipelines. These fields are built into BoldSales to support core functionalities such as record creation, automation workflows, and integrations. They are automatically included in relevant pipelines and cannot be removed, ensuring consistency and reliability in tracking pipeline data.

Accessing pipeline fields

You can view pipeline fields in two ways:

All pipeline fields

• Navigate to Setup > Modules and Fields > Pipelines or use the search bar in Setup and type Pipelines.
• Click All Pipeline Fields to see every field across all pipelines.

Pipeline-specific fields

• Navigate to Setup > Modules and Fields > Pipelines.
• Under Manage Pipelines, choose the pipeline you want.
• Open the Fields tab to view or manage fields for that specific pipeline.

System pipeline fields

Name *

The title or name given to the pipeline record for easy identification, making the record recognizable at a glance.

Stage *

Indicates the current stage of the pipeline record (such as Qualification, Proposal, Negotiation, or Closed won/lost). Stages reflect the progress of the opportunity and are essential for tracking and managing the sales cycle effectively.

Amount

Represents the monetary value associated with the pipeline record. This is typically the estimated revenue that the opportunity could generate if successfully closed.

Type

Specifies the category of the pipeline record (such as New Business, Existing Business etc.). This classification helps in segmenting opportunities and analyzing performance.

Source

Shows the origin of the pipeline record (such as Referral, Website, Organic search, or Call). Understanding the source helps in evaluating the effectiveness of marketing channels and lead generation strategies.

Priority

Helps rank pipeline records based on importance or urgency (such as High, Medium or Low), enabling sales teams to focus on the most critical opportunities first.

Owner

Identifies the user responsible for managing the pipeline record. Assigning an owner ensures accountability and clarity on who is driving the opportunity forward.

Closed won reason

The reason why the opportunity was successfully closed. Capturing this information helps in understanding what contributed to success and can inform future strategies.

Closed lost reason

The reason why the opportunity was lost. This insight is valuable for identifying patterns, improving processes, and reducing future losses.

Next step

Notes the next planned action for the pipeline record, such as scheduling a meeting, sending a proposal, or following up with the client. Keeping this updated ensures momentum in the sales process.

Description

Provides additional details or context about the pipeline record. This can include background information, client requirements, or any notes that help in managing the opportunity effectively.

Closing date

The expected or actual date when the pipeline record will close. Accurate closing dates are critical for predicting revenue and planning resources.

Contract start date

The start date of the contract associated with the pipeline record. This is important for managing deliverables and billing cycles.

Contract end date

The end date of the contract associated with the pipeline record. Tracking this ensures timely renewals and prevents service interruptions.

Order start date

The start date for an order of the pipeline record. This is relevant for operational planning and fulfillment.

Order end date

The end date for an order of the pipeline record. It helps in managing timelines and ensuring customer satisfaction.

Company

Stores the company associated with the pipeline record. This connection provides context and allows easy access to related information such as company details and history.

Contacts

Stores the one or more related contacts associated with the pipeline record. Associating contacts ensures that communication is streamlined and all stakeholders are accounted for.

Contract term

Specifies the duration of the contract in months. This is useful for calculating billing cycles and renewal timelines.

These fields come built-in and cannot be deleted. However, they can be renamed for better relevance.
Fields marked with an asterisk (*) are mandatory.

Insight fields

Insight fields are system-generated and automatically capture activity and interaction data related to pipeline records. These fields cannot be customized, but they appear on the pipeline detail page and can be used for filtering and automation. They provide real-time visibility into engagement without manual input, helping users track activity history and follow up effectively.

Last activity

Stores the most recent past activity associated with the pipeline record, based on the date and time closest to the current time.

The most recent activity is:

• Event when an event’s Start date (date and time) is the closest past date and time.
• Task when a task’s Due date (date and time) is the closest past date and time.
• Note when a note’s Created on date and time is the most recent past date and time.
• Call when a call’s Start date and Start time is the most recent past date and time.
• Email when an email’s sent or received date and time is the most recent past date and time.

Last activity on

Stores the date and time of the activity identified as Last activity, using the relevant timestamp for that activity type.

Upcoming activity

Stores the nearest future activity associated with the pipeline record, based on the date and time closest to the current time.

The upcoming activity is:

• Event when an event’s Start date (date and time) is the closest future date and time.
• Task when a task’s Due date (date and time) is the closest future date and time and the task is not closed.

Upcoming activity on

Stores the date and time of the activity identified as Upcoming activity, using the relevant timestamp for that activity.

Last assigned on

Stores the date and time when the pipeline record’s owner was last changed.

Last email sent on

Stores the date and time of the most recent email sent for the pipeline record.

Last email received on

Stores the date and time of the most recent email received for the pipeline record.

Email count

Stores the total number of emails, sent or received, for the pipeline record.

Last outgoing call on

Stores the date and time of the most recent outgoing call.

Last incoming call on

Stores the date and time of the most recent incoming call.

Call count

Stores the total number of calls (incoming and outgoing) logged for the pipeline record.

Last outbound conversation on

Stores the date and time of the most recent outgoing conversation type (email sent or outgoing call).

Last inbound conversation on

Stores the date and time of the most recent incoming conversation type (email received or incoming call).

Last conversation type

Stores the most recent conversation type that occurred for the pipeline record (email sent, email received, incoming call, outgoing call).

Last conversation on

Stores the date and time of the Last conversation type.

Conversation count

Stores the total number of conversations (emails and calls) linked to the pipeline record.

Record age (in days)

Stores the total number of days the pipeline record has existed in the system.

Current stage modified by

Stores the user who last updated the pipeline record’s current stage.

Current stage modified on

Stores the date and time when the pipeline record’s current stage was last updated.

Current stage age (in days)

Stores the number of days the pipeline record has remained in its current stage.

Created on

Stores the date and time when the pipeline record was created.

Created by

Stores the user who created the pipeline record.

Modified on

Stores the date and time when the pipeline record was last updated.

Modified by

Stores the user who last updated the pipeline record.

Customizing system pipeline fields

System fields in pipelines can be customized to improve usability and ensure they align with your sales process. While you cannot delete or change their field type, you can modify aspects such as visibility, mandatory status, dynamic behavior, and field order.

Field visibility

Field visibility determines how each field appears in the pipeline creation form and on the detail page.

In the pipeline create form, only fields marked as Included in create form in the fields page will appear when creating a new pipeline record.

In the pipeline record’s detail page, all available fields, including those not filled during record creation, will be visible on the detail page. This ensures users can view and update additional information later.

To include a field in the create form,

• Navigate to Setup > Modules and Fields > Pipelines.
• Select the pipeline and open its Fields tab.
• Locate the field you want to include in the creation form.
• In the Form settings column, click Edit.
• Check Show in create form.
• Click Save to apply.

Alternatively, you can check the Show in create form option in the field details page, which you can access by clicking the field name in the field listing page.

The create form settings apply only to the detailed create form. They do not affect the quick create form, which appears as a pop-up and is configured by default for faster record creation and cannot be customized.

Required fields

Required fields define which fields must be completed before saving a pipeline record. This ensures that critical information is always captured. By default, Name and Stage are required fields.

To make other fields mandatory:

• Navigate to Setup > Modules and Fields > Pipelines.
• Select the pipeline and open the Fields tab.
• Locate the field you want to make mandatory.
• In the Form settings column, click Edit.
• Check Show in create form and Make this field required.
• Click Save.

Alternatively, you can check the Make this field required option in the field detail page, which you can access by clicking the field name in the fields page. Note that Show in create form must be checked before that.

Field order

In the create form and in the details page of the pipeline record, fields appear in the order you set on the fields page.
To reorder fields,

• Click Reorder fields icon in the top section of the fields listing page. This opens the Reorder Fields drawer.
• Alternatively, click the more actions menu of the field and select Reorder to open the drawer.
• Drag and drop the field into the desired order.
• Click Save to apply.

Other field customization options

When you click a field name in the fields listing page, you will be redirected to the details page, and you can configure the following:

Field name

The label shown to users wherever this field is used. It can be edited to make it clear and descriptive.

API name

This name is used to reference the field in the API and other integrations. It cannot be changed.

Field type

The data type (e.g., Single-select dropdown, Date and time) of the field. This determines how the field behaves and what data it can store. It cannot be changed.

Options

Provides the list of options users can select from when entering data in the field. These options are applicable only for fields with selective field types, such as Single-select dropdown, Radio button, and Checkbox list.

Description

A brief explanation of the field’s purpose. Helps users understand what information to enter. This description can either be shown below the label or as a tooltip based on whether the Display description as tooltip option is checked or not.

Instructions

Specific directions or format requirements to guide users in entering information correctly and avoiding errors. This will be displayed below the input field.

Placeholder text

Provide a short hint about what to enter. This text appears inside the field until the user starts typing.

Field display and editing configurations

• Show in create form – Check this option to display the field when creating a pipeline record.
• Make this field required – Check this option to make the field mandatory when creating a pipeline record.
• Conditional logic – Allows you to set rules that determine the behavior of this field based on values from other fields. Configure conditions to dynamically display this field as optional or mandatory in the create form or during inline editing on the details page, adapting to the editing requirements.
• Controlling field (Field dependency) – Allows you to add a master field that controls the behavior of this field, turning it into a dependent field. This dependency allows for configuring the dependent field’s state (visible, required when visible) or the automatic population of values based on the controlling field’s inputs.
• Make this field non-editable on the details page – Prevents users from editing the field after creation.

If a field is included in the create form, you cannot add a controlling field or apply conditional logic to it. Similarly, if a field is already dependent on a controlling field or displayed based on conditional logic, it cannot be directly included in the create form.