Overview

The rating feature enables you to provide feedback or evaluate a product, service, or experience using a scale of values, often represented by stars. This intuitive tool is versatile and can be seamlessly integrated into guided workflows to achieve various objectives.

Use Cases of the Rating Feature:

1. Customer Feedback: Share your thoughts on the quality of a product or service.

2. Satisfaction Assessment: Express how satisfied you are with a purchase or transaction.

3. User Experience Evaluation: Rate your overall experience with an application or website.

4. Product/Service Comparison: Compare the relative quality of different products or services.

The rating feature enhances decision-making and provides valuable insights, empowering businesses to improve offerings and optimize satisfaction.

​

Various Fields in Rating Input

• API Name: The API Name is a unique identifier used to reference a particular object, field, or component in an application programmatically. It is typically used in backend code, integrations, or API calls. API Names are often system-generated and follow a specific naming convention, such as using underscores instead of spaces (e.g., Customer_Status__c). 

• Label: The Label is the user-friendly name for an object, field, or component that is displayed in the user interface (UI). It is designed to be easily understood by end-users and often includes spaces or capitalization for readability (e.g., "Customer Status"). 

• Help Text is the text that will be displayed to the end user to understand the Label Meaning. 

• Mark Field as Mandatory: to mark the field mandate, if the field is not field it will not allow the user to move to the next step.  

• Number of items: This setting determines how many stars will be displayed in the user interface. By default, it is set to 5. 

• Size of the icon: This option allows you to specify the size of the star icons. If you do not make a selection, the default size will be 56x56 pixels. 

• Enable Reporting: This toggle allows to specify whether the auto-drafted values in the screen component should be included in reporting. When enabled, this ensures that auto-saved data is captured and made available for analytics, addressing gaps in reporting accuracy caused by un-submitted workflows.

• Configure Error Message: This field allows you to create a warning message for users when they keep the field empty. 

• Visibility Conditions: A rule or set of rules that determine whether a specific element, field, or component is visible to users in an application or interface. These conditions are typically based on factors such as user roles, permissions, field values, or contextual data. Visibility conditions ensure that users only see relevant information, improving usability and security. 

  • Example  

    • Condition: Display a "Priority Escalation" section if the "Ticket Priority" is set to "High."

    • Implementation: 

      • Visibility Condition: Ticket_Priority == 'High' 

    • Result: The "Priority Escalation" section appears only for high-priority tickets.