[Allie]

The name of the facet component must match one of the pre-defined facet names on the parent component. This name determines where the content of the facet component is rendered. Consequently, the order in which a facet component is defined within the body of a parent component does not affect the appearence of the parent component. for more detail click this link

 

[Allie]

Encrypted Custom Fields are a new field type (released after winter 08) that allows users to store sensitive data in encrypted form and apply a mask when the data is displayed (e.g., Credit Card Number: XXX-XXX-XX-1234).
Some important points :

User profiles who have the “View Encrypted Data” configuration enabled will be able to view the field normally.
Users who do not have the “View Encrypted Data” profile will see the mask.
User profiles that have the “Modify All Data” permission will not be able to see the value of encrypted data fields.
The field length is restricted to 175 characters in size.
Encrypted Field cannot be type cast as Unique or External ID.
An encrypted field cannot be configured with a default value.
You can’t use encrypted fields in report filters and list views.
You can’t use the encrypted fields in SOQL “where/order” clauses.
Also we can not use encrypted field formula fields, workflow rules, workflow field updates, approval process entry criteria, and approval step criteria.
If you clone a record that has encrypted custom fields, Salesforce will copy the data from the field ONLY if the user has the “view encrypted data” permission.
You can access the data of encrypted field in apex, i.e value is always unmasked.

 

Did this answer your question? If not, let me know what didn't work.

• This reply was modified 9 years, 1 month ago by  Allie.