About Stored Values

Use a Stored Value to store information, such as:

Organization name
Organization image
E-mail addresses
E-mail signatures
Values to toggle on/off integrations (example: Twitter)
Alert colors

For example, use a Stored Value to:

Store an organization name and image and put them on Dashboards, Forms, Portal Sites, etc. for a cohesive branding look. Then, if a User changes the Stored Values, the change will affect all instances in the system.
Designate the current system as Development or Production. If the system is in a development environment, Users can set the Current System Stored Value to DEV so that e-mails are sent to test e-mail accounts rather than to actual Customers (using Automation Processes, Approvals, One-Step Actions, etc.). When ready to transition the system to a live environment, set the Stored Value to Production.
Note: Addresses for e-mail senders and recipients are also set by Stored Values. Refer to Configure Test and Production Accounts for detailed procedures about setting these Stored Values, as well as about transitioning the system.

A Stored Value can be:

Text (or images)
Numbers
Dates/Times
Logical (True/false)
Color

In CSM, a Stored Value can be used in/on a:

Query In Comparison Clauses as values to search for in a specified Field.
One-Step Action: In Actions where Users can specify values to use in Business Object Fields, e-mail messages, Tweets, temporary filenames, command-line arguments, URLs, etc.
Expression: To set values in Comparison Clauses.
Dashboard: To set images for Widgets.
Business Object: To set Field values and properties and to auto-populate Fields.
Automation Process: To limit records.
Approvals As values to use in set Field Actions.
Constraints: As values to limit what a Users sees or can select from in a Field, Related Item Selector, tab in a Form Arrangement, or Prompt).

CSM provides several OOTB Stored Values to help get you started. Use these OOTB Stored Values as-is, edit them, or create your own using the Stored Value Manager.