You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a requirement has an "id" field, store it in a new structure on RequirementContext, requirement-state. Then allow the "requirement-is-satisfied-by-id" expression to check ctx.requirement-state, raising an error if the ID doesn't exist yet.
Requirements would need to populate this field when they are audited, I think.
Need to ensure uniqueness on the ID field.
Future optimization: check the full document for any expressions that need this value, and skip setting it if there are none.
The text was updated successfully, but these errors were encountered:
If a requirement has an "id" field, store it in a new structure on RequirementContext, requirement-state. Then allow the "requirement-is-satisfied-by-id" expression to check ctx.requirement-state, raising an error if the ID doesn't exist yet.
Requirements would need to populate this field when they are audited, I think.
Need to ensure uniqueness on the ID field.
Future optimization: check the full document for any expressions that need this value, and skip setting it if there are none.
The text was updated successfully, but these errors were encountered: