Which two scenarios are ideal for using Appian Portals? (Choose two.)
Appian Portals are designed for scenarios where users who do not have an Appian account need to interact with Appian applications. This makes them ideal for public-facing applications such as surveys (Option B) or for allowing external users to initiate processes like registrations (Option C). They are not intended for internal use by employees (Option A) or for scenarios requiring offline capabilities (Option D). Reference:
Appian Documentation: Appian Portals
A customer wants to display a small toolbar with three icons - a "sad face," a "face with neutral expression," and a "happy face" - on the bottom of every page in their application.
Users will be instructed to use the icon that best expresses their current experience using the application. This will allow the customer to collect valuable data about users.
Which object type should be called from each page to implement this feature?
In Appian, interfaces are used to design and render user interface elements, allowing for the creation of custom layouts and components that can interact with users. In this scenario, the toolbar with emotion icons is a UI element that needs to be consistently presented across various pages. Using an interface ensures that these icons can be interactively used by users to express their sentiments, and the data collected can be analyzed for user experience insights. Interfaces are capable of embedding such UI elements and can be invoked or included across multiple pages within an application, making them the ideal choice for this requirement. Reference:
Appian Documentation on Interfaces: Provides detailed guidance on how to design and use interfaces to create user-centric UI components.
What is an Appian best practice for calling interface rules on your interface?
An Appian best practice for calling interface rules within your interfaces is to always use a consistent ordering of rule parameters. This practice enhances the readability and maintainability of your interfaces, ensuring that other developers can understand and modify the interface more easily. Reference:
Appian Documentation: Designing Interfaces
How do you refer to metadata of a process model object within process model expressions? For example: the creator, name, or description.
Process Model Properties within Appian are referred to using the pm! domain prefix in process model expressions. This includes metadata such as the creator, name, or description of the process model. Reference:
Appian Documentation: Process Model Properties
You have a record action that should only be visible to certain users under conditions specified by an expression.
How should you configure this?
To control the visibility of a record action based on certain user conditions or expressions, the security settings of the record action itself must be configured. This involves defining conditions or expressions within the record action's security settings that evaluate whether a user meets the criteria to see and interact with the action. This method allows for dynamic control over the accessibility of actions based on user roles, specific attributes, or other contextual factors, ensuring that only authorized users can see and execute the action under specified conditions. Reference:
Appian Documentation on Record Actions: Details how to configure and secure record actions, including visibility and permissions, to tailor the user experience within record views.
