ProtectedconstructorStatic ReadonlyDOCUMENT_Static ReadonlyLIFECYCLE_Static ReadonlySTATE_Static ReadonlyWRITE_StaticInstanceChecks coarse write-authority and delete-state gates before saving or deleting entity.
Returns null when permitted, or a human-readable refusal message when denied.
The Global Object Store is a place to store global objects that need to be shared across the application. Depending on the execution environment, this could be the window object in a browser, or the global object in a node environment, or something else in other contexts. The key here is that in some cases static variables are not truly shared because it is possible that a given class might have copies of its code in multiple paths in a deployed application. This approach ensures that no matter how many code copies might exist, there is only one instance of the object in question by using the Global Object Store.
Whether ResolverBase.UpdateRecord MUST load the authoritative stored row from the database
rather than hydrating from client-supplied OldValues___ (preventing status/frozen-field spoofing
on entities where TrackRecordChanges === false).
Evaluates synchronous lifecycle invariants (append-only update guard, initial state on create,
state transitions, role/operation transition gates, post-create field immutability, and per-state
field-freeze rules) and appends any violations to result.
Protected StaticgetReturns the singleton instance of the class. If the instance does not exist, it is created and stored in the Global Object Store. If className is provided it will be used as part of the key in the Global Object Store, otherwise the actual class name will be used. NOTE: the class name used by default is the lowest level of the object hierarchy, so if you have a class that extends another class, the lowest level class name will be used.
OptionalclassName: string
Evaluates declarative and programmatic entity lifecycle policies (state machines, field-freeze rules, post-create immutability, and
WriteAuthoritygates).