You have two Custom Data Types (CDT): ACME_invoice and ACME_invoiceItem that have a flat relationship.
The invoice item table has a field that is a foreign key to the invoice table. You are leveraging the database to automatically generate their primary keys.
How should you structure the process model to add a new invoice and the new invoice items to the system?
When dealing with related data types where one has a foreign key to another, you must first create the record in the primary table (ACME_invoice) and then use the generated primary key to create related records in the secondary table (ACME_invoiceItem). This is why you first write to the ACME_invoice table, then update the foreign keys in a Script Task, and finally write to the ACME_invoiceItem table.
Appian Documentation: Relational Databases
Your customer wants to change the name of a field of an existing Custom Data Type (CDT) to match a renamed database field.
The CDT is backed by a database entity, whose data store has the Automatically Update Database Schema option disabled. The old column name was BIRTHDATE and the new column name is DATE_OF_BIRTH.
How should you proceed?
When a field name in an existing Custom Data Type (CDT) needs to be changed to match a renamed database field, and the Automatically Update Database Schema option is disabled, the correct approach is to rename the field in the CDT within Appian. After renaming the field in the CDT to match the new database column name (from BIRTHDATE to DATE_OF_BIRTH in this case), you should verify the changes and publish the data store to reflect the updates. This approach ensures that the Appian data model remains in sync with the underlying database schema. Reference: Appian Documentation - Data Types and Data Stores
ACME Automobile uses Appian to manage their vehicle fleet. Vehicle records can have a status of either "active" or "inactive".
Users are primarily concerned with active vehicles and want to see only those records by default when viewing the Vehicle records list. However, it is important for users to be able to see the unfiltered list of Vehicle records on demand to address occasional auditing requests from managers.
Which configuration supports the desired Vehicle record list behavior?
To achieve the behavior where users see only 'active' vehicle records by default but can also view all records when needed, you should configure a user filter for the status field on the Vehicle record list. This user filter should have a default value set to 'active', which will filter the list to only show active records initially. However, users will still have the option to adjust the filter to see all records, thus accommodating occasional auditing requests. Reference: Appian Documentation - Record List Filters and User Filters
Which set of out-of-the-box features is only available when data sync is enabled on a record type?
Data sync enables additional features for record types in Appian. With data sync enabled, you can define relationships between different record types, add fields to a record type that do not appear in the source database (hidden fields), and configure record-level security to control access to individual records based on user roles or other criteria. These features are part of the enhanced functionality provided by data sync to ensure efficient data management and security within Appian applications. Reference: Appian Documentation - Record Type Features and Data Sync
You are creating a form used to order a pizz
a. You use a radio button component for the selection.
The pizza selection labels include a list of toppings. You do not want the selection labels to be truncated.
Which layout should you choose?
For a pizza ordering form where you do not want the radio button selection labels to be truncated, the Stacked layout is the most appropriate. This layout will list the options vertically, giving each one adequate space and preventing truncation, which is particularly useful when the labels include longer text, such as a list of toppings. Reference: Appian Documentation - Interface Components
Raylene
9 days agoCorrina
21 days agoGoldie
24 days agoChauncey
1 months agoAsuncion
2 months agoFranchesca
2 months agoGeoffrey
2 months agoKeneth
2 months agoColette
3 months agoDevorah
3 months agoDenna
3 months agoJulianna
3 months agoTy
3 months agoAzzie
4 months agoTorie
5 months agoJoni
6 months agoOren
6 months agoCarisa
7 months agoLawanda
7 months agoGlenn
8 months ago