Purpose: This guide explains how to utilize and customize the Board View for Custom Objects designed as Workflows or Pipelines. With step-by-step instructions, it helps you tailor the layout and settings to improve workflow tracking, streamline processes, and gain better insights into your data
TABLE OF CONTENTS
How to Access Board View
1. Navigate to Data > Custom Objects tab
2. Locate the View menu at the top right corner
3. Click on the Board icon to apply a Board View
Hint: The Board View option is available exclusively for Custom Objects that are configured as Workflows or Pipelines
How to Customize Board View Layout
Board View Settings
The board view settings can be updated based on your preferences. Follow the steps below to edit the settings:
1. Click on a Custom Object that has Workflow/Pipeline set
2. Locate the Settings icon near the View menu
3. Click on the drop-down arrow (V) and select Board View Settings from the list
4. Make the necessary changes to these settings:
4.1 Primary and Secondary Stage Summary Metric - The summary metric that will show on the stage header
- No Summary
- # Records
- Total $ Value
4.2 Stage Column Width
4.3 Card Display Customization - Choose which fields will be displayed on the Entity Card, when viewing it from the Board. Click on the icon to hide the field and no longer needed
Hint: Time in Stage is the total time a record has been in that particular stage. If a record has been moved between stages, the Time in Stage will be the cumulative time in that stage
5. Click Save
Note: You can add up to 5 custom fields to be displayed on a card
Stage Settings
1. From the Board View Layout go to Stage Settings tab
2. Customize available stage name, its status and % to close
3. Add a new stage (optional)
4. Once ready, click Save
Related Articles:
- View Layout Options for Contacts / Custom Objects
- How to use the Table View for Contacts / Custom Objects
- How to use the Chart View for Contacts / Custom Objects
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article