bcgov / bcgov/entity

UI Design - Acceptance of updated Qualified Supplier Terms

Open
#17,441 1 comment 0 reactions 0 assignees View on GitHub
Assets PI 26 - Discuss UX
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

Scenarios:

When the modernized system launches a new Qualified Supplier terms will be launched with updated terminology and liability insurance. There are two scenarios to address.

1. A client is accessing the modernized system as a Qualified Supplier for the first time. This client did not use the request to become a qualified supplier and instead was automatically granted qualified supplier access based upon their previous access in BC Online. That client would not have accepted the modernized Qualified Supplier agreement yet so needs to be prompted with it.
2. A client has an account that was set up in the modernized system and currently has access as a Qualified Supplier. They have accepted the initial Qualified Supplier Agreement. That agreement is updated, and we must present, and receive acceptance, for the updated Qualified Supplier Agreement.

----------------------------------------------------------------------------------------
Feedback from Kim, that has been reviewed with Kevin:

We concur that the technical requirements are met with the following two actions:

1. The account administrator (Applicant in the QSA) being notified in some format of the updated QSA terms (QSA section 9.1 - notice to be provided to the Applicant) - this could be via a number of methods - i.e., via a notice in the account, on the MHR page for Qualified Suppliers generally, via a direct communication, or on the Administrator's next log in to the system, etc.; AND
2. A user (Team Member in the QSA) acknowledging the updated QSA terms - this only needs to be one user on the first use of the system after the terms are updated, and not all users each time they enter the system) (this is not expressly stated in Section 9.1 of the QSA, but as acceptance is agreed by ongoing Team Member use, from a policy perspective it is important to have this notice pop up on the first use). It may also be helpful to link this to the Applicant/account administrator notice (i.e., the user could be directed to advise the administrator of the change). _confirmed it would also be acceptable to have all team members accept if that was easier technically and design wise. Note, I believe that is the current approach with the overarching terms of use in the system_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.