ACD101 Appian Associate Developer Questions and Answers

1. Write to Multiple Data Store Entities smart service (Writing to the ACME_invoiceItem table and ACME_invoice table).

1. Write to Data Store Entity smart service (Writing to the ACME_invoiceItem table).

2. Script Task to update foreign keys.

3. Write to Data Store Entity smart service (Writing to the ACME_invoice table).

1. Write to Data Store Entity smart service (Writing to the ACME_invoice table).

2. Script Task to update foreign keys.

3. Write to Data Store Entity smart service (Writing to the ACME_invoiceItem table).

The choiceLabels and choiceValues datatypes do not match.

The choiceValues has too few values.

The choiceLabels have too few labels.

Create and use reusable interfaces.

Use red text to highlight important information.

Use a section layout within a section layout.

Make the same update manually both in Dev and Test environments.

Make the update in the Dev environment, then compare, and deploy the update to the Test environment.

Make the update directly in the Test environment.

Add the new field manually to the ACME_Employee database table and run a database script to resync the Acme employee record.

In the record data model, you add the new field in the ADD SOURCE FIELDS. Save the field with the Update Table checkbox active.

In the record data model, you add the new field with ADD RELATIONSHIPS. Save the newly created relationship and use the field.

Visibility on the Status column in the Vehicle record list set with conditional logic.

A source filter set to exclude vehicles with status " inactive " .

A user filter for the status field with a default option corresponding to " active " .

Query the data inside a local variable used to display the departure times. Set the refreshinterval to “1”.

Query the data inside a local variable used to display the departure times. Set the refreshAlways to “True”.

Add a one minute timer to the process model to query the data and refresh the interface.

Reference AC!StoredValues in the Outputs tab of the Write to Data Store Entity node.

Add a script task to query for the most recently updated vehicle using loggedInUser().

Dot notate into the ID field of the process variable written to the database, which is automatically updated by the Write to Data Store Entity smart service.

Provides a method for an Appian application to interact with an external application or service.

Provides a method for end users to interact with an Appian application.

Provides a method for an Appian application to interact with a database.

Select the Performance tab and set test values.

Select the Test button and set test values.

Select the Gear icon, select Properties, and set test values.

Assertion

SQL Scripts

Test inputs

Context Data

Test Outputs

The record types must have data sync enabled.

The record types must be on a virtualized data source.

The record types must be stored in the local Appian business database.

Move the existing output variable to the inputs tab, and name it “vehicle”. Add output variable defined as rule!VIM_getDealershipName(ac!vehicle.dealershipId) and save that value to pv!dealershipName.

Add another output variable defined as rule!VIM_getDealershipName(pv!vehicle.dealershipId) and save that value to pv!dealershipName.

Add a new script task, and add an input variable defined as rule!VIM_getDealershipName(ac!vehicle.dealershipName) that saves into pv!dealershipName.

Dependents and Reliants

Dependents and Precedents

Inheritance and Association

paragraphField

textField

richTextDisplayField

Add a new field “ORDER_ID” on the ACME_ORDER_ITEM table and set the field as a foreign key to the ACME_ORDER entry.

Add a new field “ORDER_ITEM_ID” on the ACME_ORDER table and set the field as a foreign key of the ACME_ORDER_ITEM entry.

Add a new field “ORDER ITEM_ID” on the ACME_ORDER table and set the field as a second primary key of the ACME_ORDER_ITEM entry.

Go to File > Properties > Alerts. Configure the Custom Alert settings.

Go to File > Properties Set the proper Process Display Name

Go to File > Properties. Select the Public Events checkbox to allow anyone to fire triggers.

Look up the function in the Appian Documentation.

Search the Appian Knowledge Base Articles.

Post a question on Appian Community.

The data type of a local variable is determined by its value.

Local variables can only store primitive data types, such as numbers and strings.

Local variables must have an initial value set when defining them.

Subprocesses

a!startProcessLink()

a!recordLink()

a!startProcess()

Record Actions

Attributes in Custom Data Types (CDT) will change.

There is no impact from the change.

Column ordering in the database table will change.

Viewer permission for the process model that will move the document.

Administrator permission for both folders.

Editor permission for the file.

Call the rule by using a local variable.

Use the keyword syntax.

Use Index().

Option A

Option B

Option C

ac!

pv!

rv!

{“0123456789”,”…”}

“0123456789…”

“0123456789ABC”

RPA

Process Mining

Workflow

Call the interface rule on a rule input.

Use keyword syntax.

Always use consistent ordering of rule parameters.

Set an object description that reads: “Returns a set of form instructions to display, given the type of form and characteristics of the logged in user”.

Save a rule input of type ‘text’ for the object called ‘objectDescription’, and set a text value that generally describes the object such that other developers could quickly gain understanding of the object’s purpose.

Set an object description that includes any notes you may need if you were to become responsible for providing Production Support on that area of the application in the future. You should also include “BP – 1/12/2022 – Created” somewhere in the description.

The user was not in the user group configured for the process model security.

The process report that drives the runtime database does not have security set properly.

The button was not configured to submit the form.

Create a record type with data sync enabled using the PRODUCT table, and apply a source filter on IS_ACTIVE to filter out inactive products.

Create a record type with data sync enabled using the PRODUCT table, and create a user filter using IS_ACTIVE.

Create a record type without data sync enabled using the PRODUCT table, and apply record-level security to filter out inactive products.