[FEATURE] - Default Values on Pages #638
Description
Feature Request: Default Text for Standard Page Titles and Fields
Community Context
This feature request originated from a Community Sprint and addresses a common need among managed package users who cannot add default field values through native Salesforce capabilities.
Problem Statement
When creating events or records, users frequently miss populating important fields that should always contain information. This is particularly problematic for:
- Page titles that should follow consistent naming conventions
- Standard fields that require default values for data consistency
- Rich text fields where default content would improve standardization
Since this is a managed package, end users cannot leverage native Salesforce capabilities to set default field values, creating a gap in data quality and consistency.
Proposed Solution
Implement the ability to configure default text values for standard page titles and other key fields within the managed package or add some initial values within the package. This would include:
- A configuration interface for administrators to set default values for page titles
- Support for standard text fields to have pre-populated default content
- Ideally, extend this capability to rich text fields for enhanced standardization
- Template variables or merge fields to support dynamic default values (e.g., date, user name, record type)
Alternative Approaches Considered
While exploring solutions, the following alternatives were evaluated:
Custom Flow/Action Approach
- Record Creation Flow: Implement a Flow that prefills information when records are created
- Post-Record Action: Use automation to populate default values after record creation
While these alternatives are technically feasible, they require additional setup and maintenance. A native solution within the managed package would provide a more seamless user experience.
Use Cases and Benefits
This functionality would benefit multiple scenarios:
- Event Management: Ensure consistent page titles and descriptions across all events
- Content Standardization: Maintain uniform formatting and required information in rich text fields
- Data Quality: Reduce human error by pre-populating fields that should always contain specific information
- User Efficiency: Save time by eliminating repetitive data entry for standard content
- Compliance: Ensure required disclaimers or standard text appear consistently
Recipe Consideration
While a recipe-based solution could address this need, default page titles and field values are fundamental requirements that users will consistently need. Implementing this as a core feature rather than a recipe would:
- Reduce complexity for administrators
- Ensure consistent behavior across all instances
- Eliminate the need for custom configuration in each org
Implementation Scope
To maximize value, consider implementing this feature with the following capabilities:
Phase 1: Core Functionality
- Default text for page titles on standard pages
- Configuration interface for administrators
- Support for static default values
Phase 2: Enhanced Features
- Dynamic merge fields (date, user, record type)
- Conditional defaults based on record criteria
- Support for rich text fields
Phase 3: Advanced Capabilities
- Template library for common default text patterns
- Multi-language support for default values
- Bulk configuration tools for multiple fields/pages
Stakeholder Engagement
Development and Testing Participation: Yes, we are willing and interested in being actively engaged throughout the development and testing process. This includes:
- Providing feedback on design mockups and user flows
- Participating in beta testing
- Sharing additional use cases as they emerge
- Contributing to documentation and best practices
Success Metrics
The following metrics would indicate successful implementation:
- Reduction in records created with empty required fields
- Improved consistency in page title formatting
- Decreased time spent on repetitive data entry
- Positive user feedback on ease of use
- Increased adoption of standardized content templates
This feature would significantly improve data quality, user efficiency, and content standardization across the platform while addressing a key limitation of managed packages.
Feature Request: Default Text for Standard Page Titles and Fields
Community Context
This feature request originated from a Trailblazer Community sprint and addresses a common need among managed package users who cannot add default field values through native Salesforce capabilities.
Problem Statement
When creating events or records, users frequently miss populating important fields that should always contain information. This is particularly problematic for:
- Page titles that should follow consistent naming conventions
- Standard fields that require default values for data consistency
- Rich text fields where default content would improve standardization
Since this is a managed package, end users cannot leverage native Salesforce capabilities to set default field values, creating a gap in data quality and consistency.
Proposed Solution
Implement the ability to configure default text values for standard page titles and other key fields within the managed package. This would include:
- A configuration interface for administrators to set default values for page titles
- Support for standard text fields to have pre-populated default content
- Ideally, extend this capability to rich text fields for enhanced standardization
- Template variables or merge fields to support dynamic default values (e.g., date, user name, record type)
Visual Reference
The following screenshot illustrates the desired functionality:
Note: Image shows the configuration interface where default page title text can be set
Alternative Approaches Considered
While exploring solutions, the following alternatives were evaluated:
Custom Flow/Action Approach
- Record Creation Flow: Implement a Flow that prefills information when records are created
- Post-Record Action: Use automation to populate default values after record creation
While these alternatives are technically feasible, they require additional setup and maintenance. A native solution within the managed package would provide a more seamless user experience.
Use Cases and Benefits
This functionality would benefit multiple scenarios:
- Event Management: Ensure consistent page titles and descriptions across all events
- Content Standardization: Maintain uniform formatting and required information in rich text fields
- Data Quality: Reduce human error by pre-populating fields that should always contain specific information
- User Efficiency: Save time by eliminating repetitive data entry for standard content
- Compliance: Ensure required disclaimers or standard text appear consistently
Recipe Consideration
While a recipe-based solution could address this need, default page titles and field values are fundamental requirements that users will consistently need. Implementing this as a core feature rather than a recipe would:
- Reduce complexity for administrators
- Ensure consistent behavior across all instances
- Eliminate the need for custom configuration in each org
Implementation Scope
To maximize value, consider implementing this feature with the following capabilities:
Phase 1: Core Functionality
- Default text for page titles on standard pages
- Configuration interface for administrators
- Support for static default values
Phase 2: Enhanced Features
- Dynamic merge fields (date, user, record type)
- Conditional defaults based on record criteria
- Support for rich text fields
Phase 3: Advanced Capabilities
- Template library for common default text patterns
- Multi-language support for default values
- Bulk configuration tools for multiple fields/pages
Stakeholder Engagement
Development and Testing Participation: Yes, we are willing and interested in being actively engaged throughout the development and testing process. This includes:
- Providing feedback on design mockups and user flows
- Participating in beta testing
- Sharing additional use cases as they emerge
- Contributing to documentation and best practices
Success Metrics
The following metrics would indicate successful implementation:
- Reduction in records created with empty required fields
- Improved consistency in page title formatting
- Decreased time spent on repetitive data entry
- Positive user feedback on ease of use
- Increased adoption of standardized content templates
This feature would significantly improve data quality, user efficiency, and content standardization across the platform while addressing a key limitation of managed packages.