About Stored Values
Use a stored value to store information, such as:
- Organization name
- Organization image
- Email addresses
- Email 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, and Portal Sites for a cohesive branding look. Changes you make to the stored values affect all instances in the system.
- Designate the current system as Development or Production. If the system is in a development environment, you can set the Current System Stored Value to DEV so that emails are sent to test email accounts rather than to customers. When you are ready to transition the system to a live environment, set the stored value to Production.
Addresses for email senders and recipients are also set by stored values. See Configure Test and Production Accounts for detailed procedures about setting these stored values and transitioning the system.
A stored value can be:
- Text or images
- Logical (true/false or on/off)
Stored values 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, email messages, Tweets, temporary filenames, command-line arguments, and URLs.
- 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 as-is, edit them, or create your own using the Stored Value Manager.