Guided Workflow Screen Components - Location Input
Updated
Overview
The Location Input component enables agents to interact with geographic locations directly within the Sprinklr UI. This node allows you to search for a location, select it on an interactive map, and automatically capture the latitude and longitude coordinates. These coordinates can then be stored as part of a case entity and displayed on the screen whenever needed.
Since Sprinklr’s API requires latitude and longitude to transmit location data, this node ensures compliance by making those values a mandatory part of the captured data. It streamlines location-based workflows by enabling:
Location search based on agent input
Selection and sharing of pinpointed addresses
Saving and displaying location coordinates for future reference
This feature simplifies workflows involving geo-specific actions while enhancing accuracy and agent efficiency.
Various Fields in Location Input Component
API Name: It is the unique identifier that can be used as a reference to the value of this component.
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").
Mark Field as Mandatory: Click this option if you want to make this field mandatory.
Add Help Text: This is the text that will be displayed to the end user to help them understand the label’s meaning.
Default Value: It is the preset value used when the end user enters nothing.
Note: Default Value Format:
The default value will be in the format: A, B
Where:
A = Latitude
B = Longitude
Example: 28.83574075225593,78.76274578046814
Behavior:
If no default value is provided, the map will attempt to show the user’s current location.
If the user’s location cannot be accessed, the map will default to New York City.
Google Maps Credential: The Google Maps credentials required for the Location Input node will typically be provided by the client. However, in cases where the node is being used in a non-client-specific environment, Sprinklr’s default credentials can be used. Refer to Steps to Add Google Map Credentials in the Sprinklr Platform .
Map ID: A valid Map ID can be generated in your Google Cloud Console.
Map Height: You can adjust the height of the input field. You can set the minimum height to 300px.
Width: You can define the area/width of the input field.
Alignment: You can define the display
Start Alignment: The content (text, images, or elements) is aligned to the left side.
Center Alignment: The content is aligned to the center (horizontally and/or vertically).
End Alignment: The content is aligned to the right side.
Enable Reporting: This toggle allows you 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.
Input Disability Conditions: A rule or set of criteria that determines whether a specific element, such as a field, button, or component, should be disabled (i.e., grayed out and non-interactive) in a user interface. It restricts user interaction based on certain conditions, ensuring that actions are contextually valid or preventing errors.
Example:
Based on Field Value:
Condition: Disable the "Submit" button if the "Terms and Conditions" checkbox is unchecked.
Result: The user cannot submit the form until they accept the terms.
Based on User Role:
Condition: Disable the "Delete Record" button for users without "Admin" permissions.
Result: Only admins can delete records, while other users see the button but cannot interact with it.
Based on Data Completeness:
Condition: Disable the "Next" button until all required fields are filled.
Result: Users are prevented from moving forward until they complete the required steps.
Visibility Condition: A rule or set of rules that determines 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 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.
Configure Error Message: This field allows you to create a warning message for users if the value is left empty.
Steps to Add Google Map Credentials in the Sprinklr Platform
To add an external Credential, go to All Settings > Manage Customer > External Authentication > Add Credential > Enter the External Credential Name, set the Authentication Type as Key-Based Auth, and enter the Public Key and Secret Key.
Note: If you are an admin and want to allow users to add their Public Key and Secret Key for external authentication, create a role with the below permissions and assign it to the appropriate users or user groups.
