Certification Behavior: Reviewer vs TTA - Note, to Certify Conflicts, there can be no Conflict States of Unknown
- Use case 1:
- Automatic conflicts are determined. Then, a SRP member declares their conflicts, Certifies conflicts, and then cannot interact with conflict certification again.
- After the fact, they realize they need to change a Conflict State (either to available or to conflict). They contact (externally) the TTA Member.
- Use case 2:
- Automatic conflicts are determined. Then, a SRP member views their conflicts and disagrees with an autoConflict. They do not certify and instead notify the TTA member that the autoConflict should be changed.
- Option 1:
- We add a save button that allows the TTA member to update but not certify, as there will be Conflict States of Unknown. This button could work for Use Case 1 as well.
- Mark F. has concerns about edge cases in the UI.
- Option 2:
- The TTA member tells the SRP Member to declare their conflicts and certify.
- TTA Member goes into the Conflict Declaration UI and changes one (or more) Conflicts states as needed. TTA Member hits Certify.Certification , which is successful.
- Proposed Consequences:
- ISRs either become available or unavailable as necessary for the SRP Member.
- ISRs that are now Conflict State of Conflict that had Review Types other than None should automatically have Review Types changed to None.
Concerns:- What happens if the Review States are Finalized?
- What happens if an external ISR is added after the main panel's ISRs are Finalized?
- Should the system prevent changes to Conflict State based on Review State?
- Implementation Details:
- A TTA member can certify as many times as necessary. Certify is is a bulk action.
- A SRP Member only can see the Conflict Declaration UI if they are Uncertified. TTA members can always see the Conflict Declaration UI.
- Conflict State transitions are Role specific:
- Valid Conflict State transitions for a TTA Member:
- Available → Available
- Available → Conflict
- Conflict → Available
- Conflict → Conflict
- AutoConflict → Available
- Valid Conflict State transitions for SRP Member:
- Unknown → Available
- Unknown → Conflict
- Use case 2Concerns:
- Automatic conflicts are determined. Then, a SRP member views their conflicts and disagrees with an autoConflict. They do not certify and instead notify the TTA member that the autoConflict should be changed.
- Option 1:
- We add a save button that allows the TTA member to update but not certify, as there will be Conflict States of Unknown. This button could work for Use Case 1 as well. Mark F. has opinions.
- Option 2:
- The TTA member tells the SRP Member to declare their conflicts and certify. After the SRP member has Certified, the TTA member can then go back and do Use Case 1.
- What happens if the Review States are Finalized?
- What happens if an external ISR is added after the main panel's ISRs are Finalized?
- Should the system prevent changes to Conflict State based on Review State?Propose to do option 2.
| 
