Magidoc

SetupSectionBlocker
Object

One refusal a section makes, in the words of the refusal, beside the surface that clears it.

The destination rides with the sentence because the client used to derive it by substring-matching the sentence itself, which made every rewording a silent re-route.

Fields

#

message

Non-null

What this section refuses, in the words of the refusal it causes

targetSection

Non-null

The Finance surface holding the control that clears it, as a client surface key

prerequisiteKey

The criterion key this refusal cannot be acted on without, where one exists.

An accounting-boundary refusal asks the reader to choose a GL account, so on an empty chart of accounts it names work whose prerequisite does not exist; the next act there is the criterion, not the refusal. Declared per blocker rather than inferred from criterion order, which would demote a refusal that has no prerequisite — a sync failure stops every posting and keeps winning whatever else is unmet.

Usages

#

References

#