Skip to content

About Feature: Fields in Vymo


Fields in Vymo are critical meta-properties or characteristics essential for capturing data about leads, partners, activities, and users. Vymo categorizes fields into two primary types:

Global Fields:

  • Definition: Consistent across the entire company.
  • Accessibility: Limited to dropdowns and Business Objects.
  • Note: Globally applicable but restricted to specific features.

Module Fields:

  • Definition: Customized according to the specific requirements of each module.
  • Customization: These can be customized and reused from the "Available Fields" section.
  • Global Capability: Only fields with dropdown UI type and master UI type can be referred globally.

Dependent Features

Fields significantly impact various modules and functionalities in Vymo, including:

Lead or Partner Modules:

  • Application: Used in lead and partner data entry forms.
  • Workflow: Influence lead progression through different states.

User Module:

  • Application: Utilized in user data entry forms.
  • Customization: Allows tailoring user-related information.

Campaign Management:

  • Application: Essential for defining and managing campaigns.
  • Reporting: Influences data presentation in campaign reports.


  • Application: Impact data entry forms for various activities.
  • Tracking: Influence how activity-related data is recorded and presented.

Types of Fields:

Vymo supports various field types, each serving distinct purposes:

Standard Fields:

  • Commonly used fields like text, number, date, etc., for basic information.
  • Enable predefined options selection, ensuring data consistency.

Master UI Type Fields:

  • Fields with broader scope, allowing global references and customization.

OIFs (Object Interaction Fields):

  • Specialized fields for interactions between different objects within the system.

Validations and Regexes:

  • Fields support validation rules for data accuracy and adherence to patterns.
  • Regex (Regular Expression) support for advanced data pattern matching.


  • Review the predefined set of fields based on the module type (Lead, Partner, or User) then create or edit these fields.

User Personas and Journeys:

  • Administrator: Can design and configure fields based on business needs.
  • End User: Utilizes the fields for data input or viewing.

See also

Did this page help? No help at allYes, totally!
Back to top