Question

Ana has been asked to grant FLS to the field Account.Product_Amount__c for Sales users. The field already exists in Production, and she is not interested in committing any changes in the field. Which steps should Ana follow to commit the FSL?

a. Exclude the field from the User Story selection
b. Add the field to the User Story without making changes
c. Use the Ready to Promote checkbox for the field
d. Create a separate User Story for FLS changes

Answer 1

Ana should grant Field-Level Security (FLS) directly through the Salesforce setup interface for Sales users in the Production environment, and no changes to the field itself or deployment through User Stories are necessary.

Step-by-step explanation:

When Ana is asked to grant Field-Level Security (FLS) to the field Account.Product_Amount__c for Sales users in Salesforce, she should follow the necessary steps within the setup of the Salesforce Production environment, without committing any changes to the field itself as she is not interested in altering it. Assuming Ana has administrative privileges, the general steps would include:

• Navigating to the field settings in the Salesforce object manager.
• Accessing the FLS settings for the Sales users' profile or permission set.
• Updating the FLS to provide the necessary access (e.g., read-only or editable) to the Sales users.

These changes in Production are typically made directly in the Salesforce user interface and do not require a User Story or any 'Ready to Promote' process unless using a specific deployment methodology or change management application. Therefore, options a, b, c, and d provided in the question do not directly apply to standard Salesforce FLS changes unless within a specific development framework or tool that requires these practices.