nerdexam
RSA

050-SEPROGRC-01 · Question #68

Assuming the formula for a calculated field has been written correctly, which of the following is a probable reason why a calculation is not updated when a record is saved?

The correct answer is D. Field values affecting the calculated field's formula were not changed prior to the record save. RSA Archer calculated fields only recalculate on record save when at least one of the source fields referenced in the formula was modified during that editing session.

Customization and Configuration of Archer Modules

Question

Assuming the formula for a calculated field has been written correctly, which of the following is a probable reason why a calculation is not updated when a record is saved?

Options

  • AThe field is set to Private.
  • BThe field has been left off the layout.
  • CThe user does not have access to the application.
  • DField values affecting the calculated field's formula were not changed prior to the record save.

How the community answered

(36 responses)
  • A
    6% (2)
  • B
    17% (6)
  • C
    6% (2)
  • D
    72% (26)

Why each option

RSA Archer calculated fields only recalculate on record save when at least one of the source fields referenced in the formula was modified during that editing session.

AThe field is set to Private.

The Private setting controls field visibility to users but has no effect on whether the calculation engine executes the formula when a record save is triggered.

BThe field has been left off the layout.

Omitting a calculated field from the layout affects whether users see it on the form, but the field's formula still executes on save regardless of its presence in the layout.

CThe user does not have access to the application.

If the user successfully saved the record, they already had sufficient access to the application, so application access is not the cause of the calculation not updating.

DField values affecting the calculated field's formula were not changed prior to the record save.Correct

RSA Archer triggers a recalculation of a calculated field only when the record is saved and one or more fields referenced in that field's formula have been changed. If the user saved the record without modifying any of the dependent source fields, no change event exists to prompt recalculation, so the calculated field retains its prior value. This is the most probable cause when the formula syntax itself has already been confirmed correct.

Concept tested: RSA Archer calculated field recalculation trigger conditions

Topics

#calculated fields#formula evaluation#record save behavior#troubleshooting

Community Discussion

No community discussion yet for this question.

Full 050-SEPROGRC-01 Practice