Veeva Settings are similar to other custom objects and provide the ability to define specific application behavior for a Vault or profile

A Veeva setting uses built-in logic that lets you personalize settings for your Vault or for specific profiles. The logic checks the Vault and profile for the current user and returns the most specific, or lowest, value setting. Settings for a Vault are overridden by profile settings.

Ensure all users have at least read permission to the veeva_settings__v object and at least read permission to all fields on the veeva_settings__v object.

To view or edit a Veeva Setting:

1. Navigate to Business Admin > Veeva Settings.
2. Select the global veeva_settings__v record.
3. Select Edit to make Vault level changes for one or more Veeva settings.
4. Select Save.

When viewing the Veeva Setting detail page, the list of records in the Custom Fields section displays both configuration settings and strings (labels, error messages, etc.). Only configuration settings should be modified using Veeva Settings. Strings referenced by the application will continue to be administered using Veeva Messages.

For information on creating profile-specific Veeva settings, see Configuring VMOCs or Settings for an Application Profile.

Only global and profile-level settings are supported. User-level settings are not supported.

Business admin users can also configure other profile-specific custom settings, for example, Approved Email Settings or Multichannel Settings.

When using profile-level Veeva Settings, enable the Enhanced Sync setting on the VMOC for the veeva_settings__v object. This avoids a Force Full Refresh, saving time when users switch between profiles during integrations.

Veeva Settings are often populated by Veeva Messages.

For Veeva Messages containing text requiring a LongTextArea field type, special logic applies:

• The Veeva Setting contains text in the following format: MessageName;;MessageCategory
• The setting points to the Veeva Message in the category indicated within the setting’s text
• The actual value of the configuration is set within the Veeva Message
• You can still apply profile level settings, but you need to create separate copies of the Veeva Message that is pointed to by each of the settings
• Each Veeva setting displays as the original Veeva Message name
• The active Veeva Message for all configurations automatically migrates to the new Veeva setting; administrator action is not required as any customizations you have made are applied as the default value
• Vault level Veeva Settings cannot be deleted
• Only one application profile can be associated with a veeva_settings__v record
• Unlike Veeva Messages, modifications made to Veeva Settings are not overwritten during an upgrade
• If you use Profile Specific Settings and the iPad platform, add the following to the WHERE clause to the VMOC for the veeva_settings__v object or the appropriate custom settings object. This ensures only the applicable profile specific settings synchronize:
  • WHERE application_profile__v = @@USER_APP_PROFILE_ID@@ OR (application_profile__v = null AND security_profile__v = null)