ACD101 Questions and Answers

Option A

Option B

Option C

Only basic data types should be used for rule inputs. Custom Data Types (CDTs) or records should always be queried within the expression rule rather than passed in via rule input.

The data type for rule inputs should be set only for Custom Data Types (CDTs).

If the value passed in via rule input may be a list of numbers, the rule input must be configured as an “Array”.

Making updates to the app.

Providing end users access to the finished product.

User acceptance testing.

Once created, both expression rules and interfaces cannot be renamed.

Expression rules containing more than 4,000 characters should be converted to interfaces.

When editing an expression rule, interface components do not render for display.

Reduce your process’ delete and archival interval under Data Management > Automatic Process Clean-Up. Most Voted

Split the process into subprocesses so that only a part of the overall process is active. Most Voted

Start the process with the memory optimizer option toggled “On”.

Reduce the number of process variables. Most Voted

Do not store large data chunks like text strings in process variables. Most Voted

Compress text into a .ZIP file before storing them in process variables.

Maria

0

1

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.

Multiple users can accept the task at the same time up until the point that the first user completes it.

For each user in the group, a task is generated and assigned to them to complete.

One user in the group can accept the task for themselves and complete it.

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 choiceLabels and choiceValues datatypes do not match.

The choiceValues has too few values.

The choiceLabels have too few labels.

RPA

Process Mining

Connected Systems

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.

The size of the label font increases to show significance.

An asterisk (*) appears at the end of the label to notify the user that the field must have a rule.

The label font of the field goes from normal text to bold in order to draw attention.

Configure the rule inputs table on the Forms/Process Start Form tab to correctly refer to the values from your process model.

Configure the interface so that the local variables refer directly to values in the ac! (activity class) domain.

Configure the process properties on the Data Management tab to correctly refer to your form rule inputs.

A manager wants to obtain a view of their team ' s performance.

A retail customer wants to conduct a public survey for their recently launched product.

An employee who does not have an account wants to register for their company ' s vehicle fleet a management system.

A user needs to submit support requests when they are using their mobile device in areas with bad network coverage.

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.

Knowledge Center

Decision Object

Folder

Feed

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.

Dependents and Reliants

Dependents and Precedents

Inheritance and Association

The maximum number of activity chained nodes is exceeded and breaks.

The second User Input Task is assigned to the process initiator.

The second User Input Task is assigned to the Acme business user group.

The record types must have many-to-many relationships.

All record types in the relationship must be backed by an integration.

Data sync must be enabled for the record types.

Primary

Secondary

Destructive

Configure the Data Management tab.

Configure the activity class parameters of a Write to Data Store Entity node, a

Configure inputs on the Data tab of a User Input Task.

Maria

0

1

Updated Today

Updated 01/01/2023

Updated 01/01/2023 4:00 PM GMT+00:00

List

Views

Data model

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.

Call the interface rule on a rule input.

Use keyword syntax.

Always use consistent ordering of rule parameters.

Create individual interface objects for each chunk of code that is logically grouped, especially for those that may be reused in other areas of the application.

Create only one interface object per developer assigned to the feature. This balances the performance cost of calling additional interface objects with the need to prevent developers from overwriting each other.

Since the components are related, all code should be centralized in a single interface object. This minimizes the performance cost incurred by Appian calling multiple interface objects.

Record List

Tempo

News Feed

Interface

Action