Overview

The Custom App component in Sprinklr allows brands to seamlessly integrate third-party or external applications directly into guided workflows. These apps can be developed using the Custom Apps module available under platform settings (manage customer section)and then rendered within guided workflow screens to enhance user interaction.

For example, an airline can integrate applications for seat selection, meal preferences, or other personalized services into their workflows. Brands also have the flexibility to design custom applications that mimic the UI of external or third-party apps. Once created, these apps can be uploaded to Sprinklr and further customized using templated props to pass specific variables, enabling the delivery of tailored widgets based on unique needs.

This feature empowers organizations to provide a more interactive and personalized experience by embedding custom or external app interfaces directly into their workflows.

​

Various Fields in Custom App Widget

• API Name: This is the unique identifier for this button. For this widget, you need to ensure that there are no hyphens and spaces in this API Name field input. Ensure that the name does not start with a number or underscore.

• Widget: When you create a custom app, it will appear in a dropdown menu. You can click on the dropdown, see your custom app listed there, and then select it to use within the platform. The widget allows you to easily choose and display your custom app wherever needed.

• Controlling Field: Controlling fields allow you to display data based on certain inputs from previous components. For example, if you've built a custom app for payments and you want to show the payments based on dates, you can set the Date as the controlling field. This way, the app will display payments for a specific date range.

  Similarly, if you have a list of cities or states, you can choose country as the controlling field. This will make the list of states populate based on the selected country. Essentially, controlling fields let you filter and display data dynamically based on user choices.

• Templated Props: Templated props are inputs provided to the app that determine the data it will display. For example, if you're building an airline UI, you can use the PNR (Passenger Name Record) as a templated prop. When the PNR is entered, the app can display details of all the available seats. Essentially, templated props act as dynamic inputs that customize the app's output based on the specific data you provide.

• Visibility Conditions: It is 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 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.