Update valid statuses for ControlledGlossaryTerms #7550
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR provides the following changes:
Testing
New FVT tests have been added to the Asset Manager OMAS FVT that ensure a ControlledGlossaryTerm can be moved through all of its InstanceStatuses. Also that the userDefinedStatus can be set through this API.
There is also a test that ensures undefined attributes are rejected.
I also used postman to check that the updates to the valid instance statuses in currently defined subtypes that should have inherited the valid instance statuses from their super type are now doing so. For example, GovernancePolicy should inherit is valid instance statuses from GovernanceDefinition. This is now working ...
This is the new type definition for ControlledGlossaryTerm:
Release Notes & Documentation
Additional notes