Added Role Name to the Requirements tables#1115
Open
marcusgraca wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
To enable proper usability of the Requirements tab in the reports, we need to associate each requirement with its corresponding Role Name.
In the current model, the Role Name is only linked to requirements that are in a "Pending" state, returning NULL when the requirement has the status "Completed" or "Exempted".
This change adjusts the logic so that the Role Name is also captured when a requirement is marked as Completed or Exempted.
Additionally, the model in the OData Controller was updated to expose these columns in the FamilyRequirementStatuses and IndividualRequirementStatuses tables.