Worker Canvas Tabs for Skills, Channel Capacity & Worker Attributes

[ldvlgr]

Summary

This enhancement adds Tabs to the Worker Canvas for Skills, Channel Capacity & Worker Attributes.
The existing native WorkerSkills component is removed from the Worker Canvas and added as the first tab.
Supervisor Channel Capacity is moved to the 2nd tab and Worker Attributes viewer to the 3rd tab.
Also included here is a new Tab with Worker Details and the ability to update the team, department, location and manager attributes on the worker. Editable fields are configurable.

Checklist

• Tested changes end to end
• Updated documentation
• Requested one or more reviewers

[github-actions]

0 ESLint error(s) and 0 ESLint warning(s) found in pull request changed files.
0 ESLint error(s) and 0 ESLint warning(s) found in files outside of the pull request.

✅ No issues found!

[jared-hunter]

this is a great looking feature - some things we need to tidy up to keep it inline with the conventions in the template.

Main issue:

• As it stands attribute-viewer and supervisor-capacity dont work unless you also enable worker-canvas

Reason:
this is because there are no hooks for those features on the worker canvas anymore

Solution:
To fit with the pattern of cross-feature dependencies we have

if feature B depends on feature A performing operational logic. Feature A should expose an action that can be invoked by feature B (example of conversations exposing an action for invoking an external warm transfer and custom-transfer-directory using it)

if feature B depends on feature A for rendering location. Feature B should check if Feature A is enabled, and render appropriately (example in canned-responses rendering differently depending on presence of enhancedCRMContainer)

In this case its a bit of both....

worker-canvas-tabs should expose an action to register the tab (you can see an example in enhanced crm container, registering the action here and how it is used to hook in components for rendering here

Then the attribute-viewer and supervisor-capacity features can run independently or with worker-canvas

The alternative solution (and actually my preference) is to combine these features together so that the worker-canvas-tabs piece is always enforced by the feature (why would you not want that?)

so maybe something like a supervisor-worker-canvas-enhancements that brings these al together under one umbrella

let me know your thoughts