Archer-Expert Exam Dumps : Archer Certified Administrator-Expert

To build a hierarchical view within a single application (like a "Manager" field in the Contacts application that points back to another record in the Contacts application), Archer utilizes Internal References . As taught in the Archer Administration II Advanced Search module, when an application references itself, you can use Directional Search logic to traverse the hierarchy.

By configuring the search to look "Upstream" or "Downstream" through the internal reference, Archer can recursively find all subordinates under a manager or all managers above an employee. This allows the system to flatten a complex organizational tree into a readable report. External References (Option B) are used between different applications, and Statistical Search (Option D) is used for mathematical aggregations (Sum, Count, Average). Only the combination of Internal References and Directional Search provides the specialized recursive logic required to map out a multi-level organizational hierarchy.

According to the Archer API Guide and Administration II materials, the Archer APIs have specific formatting requirements based on their architecture. The SOAP API (Simple Object Access Protocol) is strictly bound to the XML-based SOAP protocol. It uses a Web Services Description Language (WSDL) to define the structure of its messages, and these messages must be formatted as XML . It cannot process or return JSON payloads.

In contrast, the RESTful API is more flexible; while it defaults to JSON for modern integrations, it is capable of supporting both XML and JSON depending on the "Content-Type" and "Accept" headers provided in the request. The Content API , which is a specific subset of the Archer RESTful infrastructure, also follows these multi-format capabilities. Therefore, the statement that the SOAP API can use JSON is the incorrect one. For administrators building integrations, understanding this distinction is vital, as modern web applications typically prefer JSON, but legacy Archer SOAP services will reject any request that is not valid XML.

In the Archer platform, a "Calculated Field" is not a separate field type you select from the initial list (like Text or Date). Instead, almost any standard field type can be transformed into a calculated one. According to the Archer Administration II curriculum, the foundational step is to create the field first and then go into the field’s General Tab properties to check the box labeled "Calculate its value."

Once this option is enabled, the "Formula" and "Calculation Properties" tabs appear, allowing the administrator to define the logic. You cannot write a formula (Option A) or validate it (Option D) until the field has been designated as a calculated field. Option C is irrelevant as a "first step," as calculations can be applied to many field types, not just User/Groups lists. By enabling the calculation property first, you signal to the Archer Calculation Engine that this field's value will be managed by the system rather than by manual user input.