You are an Archer administrator.

This is a critical performance and behavior concept taught in Archer Administration II . Conditional Layout (CL) rules are intended to be "dynamic," meaning they should fire as the user interacts with the record (on-the-fly). However, Archer's Calculation Engine primarily runs on the server side during a "Save" event. If a CL rule depends on the value of a Calculated Field , the UI cannot determine the rule's outcome until the calculation has been processed by the database.

Consequently, the section remains hidden while the user is editing because the calculated value hasn't been updated in the current session yet. To make CL rules fire "instantly" before a save, administrators should use non-calculated fields (like Values Lists or Text fields) as the trigger. If a calculated field must be used, the behavior described—where the layout only updates after the record is committed to the database—is the expected platform limitation. Options C and D would not specifically cause a "save-only" refresh; a Date field (unless it is a calculated date) would trigger the CL rule immediately upon selection.