ACD101 Questions Bank

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.

Web Services, Salesforce, Database

Web Services, Process Reports, Database

Salesforce, Process Models, Database

Duplicate the existing Appian object and rename it to include the date of the release that will contain the new object.

This follows the best practice of not reusing objects that are more than one (1) year old.

Reuse the existing Appian object to perform the calculation after validating it works properly for your use case.

Reusing the object helps to enforce consistency with application of the formula across the application.

Duplicate the existing Appian object and reuse the same name.

This follows the best practice of maintaining traceability of object creation to developers while avoiding duplication of code.

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).