Status constraints
Status constraints are constraints over the Primary state when it is a particular status.
They are shown as a rounded box under the status state box to which the constraints apply:
In the Agreement example use case, status constraints are used to show which state properties must be populated for a particular status. In particular, the aim is to:
- Mandate that rejectionReason and rejectedBy are set to null when in the PROPOSED status.
- Mandate that rejectionReason and rejectedBy are filled in when in the REJECTED status.
Whether the fields should be null or populated in the AGREED status has not been specified.
Was this page helpful?
Thanks for your feedback!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.
We're sorry this page wasn't helpful. Let us know how we can make it better!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Create an issue
Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.