What user experience should you build for customers without an Appian login who need to report an incident?

What user experience should you build for customers without an Appian login who need to report an incident?

• A. A portal
• B. A site
• C. An app
• D. A record type

Answer: (A)

Building a user experience for customers without an Appian login who need to report an incident requires a solution that allows external users to interact with a simplified interface. A portal is designed specifically for such scenarios, as it can facilitate external access to specific functionalities while maintaining security and data integrity. A portal can be configured to present forms or interfaces tailored for incident reporting, enabling users to fill out necessary information without needing an Appian login. This design is particularly effective for non-logged-in users, as it can be set up with public access while still funneling responses into the Appian system for processing. In contrast, a site generally serves as a broader aggregation of various components and could be more complex than needed for a simple reporting function. An app typically caters to users who are logged in and may require additional permissions and configurations that aren't suitable for external parties. A record type is primarily used to define how data is organized or structured and is not a user-facing experience. Therefore, a portal is the most suitable option for creating a user experience that allows customers without an Appian login to report incidents.

Building a user experience for customers without an Appian login who need to report an incident requires a solution that allows external users to interact with a simplified interface. A portal is designed specifically for such scenarios, as it can facilitate external access to specific functionalities while maintaining security and data integrity.

A portal can be configured to present forms or interfaces tailored for incident reporting, enabling users to fill out necessary information without needing an Appian login. This design is particularly effective for non-logged-in users, as it can be set up with public access while still funneling responses into the Appian system for processing.

In contrast, a site generally serves as a broader aggregation of various components and could be more complex than needed for a simple reporting function. An app typically caters to users who are logged in and may require additional permissions and configurations that aren't suitable for external parties. A record type is primarily used to define how data is organized or structured and is not a user-facing experience.

Therefore, a portal is the most suitable option for creating a user experience that allows customers without an Appian login to report incidents.