Pass the Archer Archer Certified Administrator Archer-Expert Questions and answers with CertsForce

The Mail Merge functionality in Archer allows administrators to take record data and push it into a pre-formatted Word or PDF template. This is a common requirement for generating formal "Exception Letters" or "Audit Reports."

As taught in the Archer Administration II curriculum, when a user is viewing a record and wishes to generate one of these documents, they must click the Export button. Upon clicking Export, the user is presented with several options: standard exports (like CSV or Rich Text) and any Mail Merge Templates that have been associated with that specific application and made available to the user's role. Option B (Email) is used for sending on-demand notifications, not for generating formatted document templates based on Word/PDF layouts.

Scheduled Report Distributions behave differently than standard "On-Demand" reports. According to the Archer Administration II curriculum, when a report is scheduled for distribution (e.g., emailed as a PDF or Excel file), the Archer platform must "impersonate" a user to run the query and generate the file.

The platform uses the security context of the user who configured the Scheduled Report Distribution (typically an administrator). This means that all recipients of the email will see the exact same data—the data that the administrator is authorized to see. This is a critical security consideration: if an administrator has "System Administrator" rights and schedules a report for a group of low-privilege users, those users may see sensitive data in the attachment that they would not be able to see if they logged into Archer directly. Option B is incorrect because the system does not run a separate query for every individual recipient's unique permissions at the time of the email burst.

The Archer Web Services Transporter is used for "Archer-to-Archer" data feeds. For the "Load Fields" button to work, Archer must be able to successfully authenticate and connect to the source instance's API to retrieve the report metadata.

As detailed in the Archer Administration II Data Feed module, if no fields appear, it almost always indicates a communication failure between the Feed Manager and the Web Service. The Transport Configuration section (found on the Source Connection tab) contains the critical connection details: the Base URL, the Instance Name, and the User Credentials. If the credentials are incorrect, the URL is mistyped, or the "Session Token" cannot be generated, Archer cannot "see" the source report's structure, and thus the field list will remain empty. Checking the connection settings is the primary troubleshooting step before looking at filters or target mappings.

The Advanced Workflow Job Troubleshooting tool is a runtime utility designed to manage individual "instances" of records currently enrolled in a workflow. It is used to fix records that are stuck due to errors. According to the Advanced Workflow Beyond the Basics guide, this tool is purely for operational maintenance (Cancel, Reset, Restart, or "Force" movement).

Editing the Advanced Workflow structure (changing the flowchart, adding nodes, or modifying logic) cannot be done within the Troubleshooting tool. Workflow design changes must be made in the Application Builder under the Workflow tab. Attempting to "fix" a logic error by changing the design is a development task, whereas the Troubleshooting tool is an administrative task for existing data. Furthermore, editing a workflow requires saving a new version and potentially migrating active jobs, a process entirely separate from the record-level "Reset/Cancel" functions found in the Job Troubleshooting interface.

In modern Archer environments (post-version 6.x), the Archer Job Engine Service is the primary service responsible for executing asynchronous tasks, including Data Feeds. When a Data Feed is initiated, it is placed in the queue. If the status remains "Pending," it indicates that the task has been recognized by the database, but no service has "picked it up" to begin processing.

As detailed in the Archer Administration II troubleshooting modules, the Job Engine is the "worker" that handles these requests. If this service is stopped, paused, or stuck on the application server, all scheduled and manual feeds will remain in a "Pending" state indefinitely. While the Queuing Service (Option D) is involved in the initial placement of the task, the actual execution and the transition out of "Pending" into "In Progress" is the responsibility of the Job Engine. The Indexing Service (Option C) handles search keyword indexing and is unrelated to data feed execution.

While the standard Archer Application Builder supports a wide array of field types, the Questionnaire module uses a more specialized subset of fields within the Question Library . According to the Questionnaires and Assessment Maintenance curriculum, questions are designed to gather specific response data that can be scored.

Valid question types include Values List (for multiple choice), Date (for timestamped responses), Numeric (for quantitative data), and Text (for qualitative comments). The User/Groups List is also a valid question type, often used to identify stakeholders or owners during an assessment. However, an Attachment is not a standalone question type in the library. In Archer Questionnaires, attachments are typically handled as "supporting evidence" linked to a specific question or the record as a whole, but you cannot define a question as an "Attachment type" in the same way you define a "Values List" question.

In Archer, Private Fields are a high-security feature where access is restricted to specific Users or Groups, regardless of their Access Role permissions. When an administrator manages these permissions, the concept of Cascading is vital for hierarchy management.

As taught in Archer Administration II , if you grant a parent group access to a private field and select the "Cascade" option, Archer automatically extends those permissions to every child group within that hierarchy. This follows the standard inheritance model used throughout the platform's security architecture. Without cascading (Option C), only the direct members of the parent group would see the field data, and administrators would have to manually add every subgroup individually. Selecting cascade ensures that as the organization grows and new subgroups are added under the parent, those new members will automatically inherit the necessary access to view or edit the protected field.

When troubleshooting a failure in Advanced Workflow (AWF) notifications, the administrator should start at the most granular level of the recent change. Since the scenario mentions updates were made to the On Demand Notification Templates (ODNT) , that is the most likely point of failure.

According to the Advanced Workflow Beyond the Basics curriculum, for an AWF notification to fire, the node in the workflow must be correctly mapped to an ODNT, and that template must have a valid Recipient (e.g., a field mapping or a specific user) and a "Status" of Active . If the template was accidentally set to Inactive or if the Recipient field mapping was broken during the update, the email will never trigger. While Options A, B, and D are valid system-wide checks, they are less likely to be the cause if other notifications in the system are still working correctly; therefore, validating the specific template is the standard first step.

In Archer, the LDAP Synchronization process is a comprehensive identity management tool. According to the Archer Administration II curriculum, its primary purpose is to ensure that the Archer user database mirrors the corporate directory (Active Directory/LDAP). It is not limited to just creating accounts or linking groups; its most critical function is the automation of the user lifecycle .

When the sync runs, it checks for changes in the LDAP source. If a user’s department or email changes in Active Directory, Archer updates the user profile data accordingly. Most importantly for security, if a user is disabled or removed from the LDAP group/OU being synced, Archer can automatically deactivate the account (or move it to a "terminated" status) based on the "Missing Person" configuration in the LDAP setup. This prevents unauthorized access by former employees. Options C and D are "Only" statements that describe small portions of the tool's capability, whereas Option B captures the ongoing maintenance and security synchronization that is the hallmark of the Archer LDAP service.

The RESTful API in Archer utilizes the OData (Open Data Protocol) standard to provide powerful querying capabilities. According to the Archer Administration II integration documentation, OData allows developers to use specific URL parameters—such as $filter, $select, $top, and $orderby—to refine the data returned by the API.

Without OData, a REST call might return every field for every record in an application, leading to significant overhead and slow response times. By using OData, the client can "narrow down the responses" by requesting only specific fields (using $select) or only records that meet certain criteria (using $filter). This is fundamentally different from the SOAP API (Options B and D), which relies on structured XML search requests. OData is what makes the RESTful API efficient for mobile applications and external integrations that require specific, lightweight data payloads.