Skip to content

24648- Enable new role support for contact_centre_staff#3198

Merged
rodrigo-barraza merged 18 commits intobcgov:mainfrom
rodrigo-barraza:feature/24648
Jan 9, 2025
Merged

24648- Enable new role support for contact_centre_staff#3198
rodrigo-barraza merged 18 commits intobcgov:mainfrom
rodrigo-barraza:feature/24648

Conversation

@rodrigo-barraza
Copy link
Contributor

@rodrigo-barraza rodrigo-barraza commented Jan 7, 2025

Issue #:
bcgov/entity#24648

Description of changes:
Hiding various buttons, and disabling some actions for users with the role contact_centre_staff.

image

image

image

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the sbc-auth license (Apache 2.0).

@seeker25
Copy link
Collaborator

seeker25 commented Jan 7, 2025

pushing out a build, just putting do not merge for a couple

@rodrigo-barraza rodrigo-barraza marked this pull request as ready for review January 7, 2025 23:49
@ochiu
Copy link
Collaborator

ochiu commented Jan 8, 2025

/gcbrun

@bcregistry-sre
Copy link
Collaborator

Temporary Url for review: https://bcregistry-account-dev--pr-3198-au1sskp7.web.app

@ochiu
Copy link
Collaborator

ochiu commented Jan 8, 2025

@rodrigo-barraza can't access the staff dashboard with just the contact_centre_staff group on its own

Screenshot 2025-01-07 at 9 46 32 PM

I did some quick and loose updates on this PR https://github.com/bcgov/sbc-auth/pull/3182/files#diff-d93db5d449e4fa9564fbab4824387879235c21d4a5db11a7e19b69aedd2878fb

They may not be totally correct as I was just trying to get a version of the UI that we could verify the API permissions changes with. But you probably need some updates for the router.

@rodrigo-barraza
Copy link
Contributor Author

@rodrigo-barraza can't access the staff dashboard with just the contact_centre_staff group on its own

Screenshot 2025-01-07 at 9 46 32 PM

I did some quick and loose updates on this PR https://github.com/bcgov/sbc-auth/pull/3182/files#diff-d93db5d449e4fa9564fbab4824387879235c21d4a5db11a7e19b69aedd2878fb

They may not be totally correct as I was just trying to get a version of the UI that we could verify the API permissions changes with. But you probably need some updates for the router.

Added support for users with contact_centre_staff as their role, but without admin.

@ochiu
Copy link
Collaborator

ochiu commented Jan 8, 2025

/gcbrun

@bcregistry-sre
Copy link
Collaborator

Temporary Url for review: https://bcregistry-account-dev--pr-3198-au1sskp7.web.app

@ochiu
Copy link
Collaborator

ochiu commented Jan 8, 2025

Probably need to hide involuntary dissolution tile as per parent ticket, maybe document service, you would need to check with Patty and Ethan.
Screenshot 2025-01-08 at 7 44 28 AM

Columns not showing data
Screenshot 2025-01-08 at 7 44 57 AM

Check box should be read only as well
Screenshot 2025-01-08 at 7 45 43 AM

Screenshot 2025-01-08 at 7 46 43 AM

Screenshot 2025-01-08 at 7 49 23 AM

When I click transactions it just takes me to account info
Screenshot 2025-01-08 at 7 51 16 AM

@rodrigo-barraza
Copy link
Contributor Author

Probably need to hide involuntary dissolution tile as per parent ticket, maybe document service, you would need to check with Patty and Ethan. Screenshot 2025-01-08 at 7 44 28 AM

Columns not showing data Screenshot 2025-01-08 at 7 44 57 AM

Check box should be read only as well Screenshot 2025-01-08 at 7 45 43 AM

Screenshot 2025-01-08 at 7 46 43 AM

Screenshot 2025-01-08 at 7 49 23 AM

When I click transactions it just takes me to account info Screenshot 2025-01-08 at 7 51 16 AM

Spoke with Patty, we decided that involuntary dissolution and document record service should both be hidden.
Fixed columns not showing data.
Made checkbox read-only.
We decided to hide the download affidavit button since it should be view only.
Tabs are now visible, but actions should be hidden.
Transactions should be working.

@rodrigo-barraza
Copy link
Contributor Author

/gcbrun

@bcregistry-sre
Copy link
Collaborator

Temporary Url for review: https://bcregistry-account-dev--pr-3198-au1sskp7.web.app

@ochiu
Copy link
Collaborator

ochiu commented Jan 8, 2025

On the main dashboard this probably needs to be hidden

Screenshot 2025-01-08 at 11 06 06 AM

Screenshot 2025-01-08 at 11 06 22 AM

Also, I still don't seem to be able to access Transactions

]

public mounted () {
this.canDoActions = !this.currentUser?.roles?.includes(Role.ContactCentreStaff)
Copy link
Collaborator

@ochiu ochiu Jan 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be better to just abstract this a bit since we are re-using v-can and the common utils Permissions?
We can add a permission there and not need to add the role check here specifically?

^ The above applies to other places as well

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed transactions, and moved logic to permissions and v-can:

@ochiu
Copy link
Collaborator

ochiu commented Jan 9, 2025

/gcbrun

@bcregistry-sre
Copy link
Collaborator

Temporary Url for review: https://bcregistry-account-dev--pr-3198-au1sskp7.web.app

@ochiu
Copy link
Collaborator

ochiu commented Jan 9, 2025

@rodrigo-barraza
Thanks for the updates, I think the only think left I am seeing is the issue with Continuation Authorization Reviews component needs to be hidden as per previous comment.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jan 9, 2025

@ochiu
Copy link
Collaborator

ochiu commented Jan 9, 2025

/gcbrun

@bcregistry-sre
Copy link
Collaborator

Temporary Url for review: https://bcregistry-account-dev--pr-3198-au1sskp7.web.app

@rodrigo-barraza rodrigo-barraza merged commit b673f89 into bcgov:main Jan 9, 2025
11 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants