How to Create and What Custom Fields Are Used For
Learn how to create custom fields in the octapipe pipeline and understand their applications in project management
Support Team
Last Update há 4 meses
Custom fields allow you to add specific attributes to cards, such as “Estimated ROI” or “Quality Score”, enriching workflows and reports. See how to create and configure these fields below.
1st Step: Accessing the Pipelines Module
In the upper left side menu, click “Pipelines”.
1st Step: Accessing the Pipelines Module
In the upper left side menu, click “Pipelines”.
2nd Step: What Are Custom Fields
Custom fields allow you to include additional and specific information in cards, making management more detailed and customized.
3rd Step: What They Are Used For
• Adapt the pipeline to business needs.
• Standardize data collection in cards.
• Facilitate filters and reports in the Kanban board.
• Automate rules based on specific values.
4th Step: Creating a Custom Field
• Type: field format (text, number, date, etc.).
• Layout: choose “Single” or “Double” to define the width.
• Placeholder: guidance text displayed inside the field (optional).
• Mask: formatting pattern (e.g., (000) 000-0000) (optional).
• Is the Field Required?: enable if the field must be filled in.
• Is the Field Read-Only?: enable to protect automatic values (optional).
Custom fields allow you to include additional and specific information in cards, making management more detailed and customized.
3rd Step: What They Are Used For
• Adapt the pipeline to business needs.
• Standardize data collection in cards.
• Facilitate filters and reports in the Kanban board.
• Automate rules based on specific values.
4th Step: Creating a Custom Field
- Open “Module Settings” represented by the Gear Icon in the upper right corner.
- Select the “Fields” tab.
- Click “Add Custom Field”.
- In the “Create Custom Field” modal, fill in:
• Type: field format (text, number, date, etc.).
• Layout: choose “Single” or “Double” to define the width.
• Placeholder: guidance text displayed inside the field (optional).
• Mask: formatting pattern (e.g., (000) 000-0000) (optional).
• Is the Field Required?: enable if the field must be filled in.
• Is the Field Read-Only?: enable to protect automatic values (optional).
5th Step: (Optional) Setting Visibility Rules
• In Operator, define the condition (e.g., Equal).
• In Value, choose the desired value (e.g., In Progress).
2. Click “Apply Filter” to create additional rules. Only cards that meet the conditions will display the field.
- Click the “Visibility” tab and define the rules:
• In Operator, define the condition (e.g., Equal).
• In Value, choose the desired value (e.g., In Progress).
2. Click “Apply Filter” to create additional rules. Only cards that meet the conditions will display the field.
6th Step: Finalizing the Creation
Click “Create Field” to finish.
Best Practices:
• Evaluate the impact before creating fields to avoid unwanted effects on cards and automations.
• Use placeholders and masks strategically to guide input and prevent errors.
• Document all field information in a centralized repository for future reference.
• Apply visibility and required rules carefully to avoid overloading forms.
Conclusion:
You have learned how to create custom fields in a pipeline and understand their functions and benefits. If you have any questions, contact our support team.
• Evaluate the impact before creating fields to avoid unwanted effects on cards and automations.
• Use placeholders and masks strategically to guide input and prevent errors.
• Document all field information in a centralized repository for future reference.
• Apply visibility and required rules carefully to avoid overloading forms.
Conclusion:
You have learned how to create custom fields in a pipeline and understand their functions and benefits. If you have any questions, contact our support team.