AWA vs Manual Assignment – HR Tasks & Cases Reporting Requirement

sreeha
Tera Contributor

Hi 

i have a requirement to create a consolidated report/dashboard to provide better visibility into work allocation and processing efficiency within HR Operations.

 

🔍 Objective

The report should help distinguish and analyze the following:

1.AWA Auto-Assigned Work Tasks or HR cases automatically assigned via Advanced Work Assignment (AWA)

2.Manually Assigned Work Tasks or HR cases assigned manually to agents (outside AWA)

2 REPLIES 2

SupriyaWaghmode
Mega Sage

Hi @sreeha , 

 

If you prefer a simpler report filtering structure without database joins:
  1. Create a custom choice field on sn_hr_core_case called Assignment Method (u_assignment_method) with choices: AWA Auto and Manual.
  2. Configure a Business Rule or utilize the AWA Workflow Extension points to set this field to AWA Auto the moment an agent clicks "Accept" in the Agent Workspace inbox.
  3. Set a default value or a separate before insert/update Business Rule that marks the field as Manual if assigned_to changes outside of the workspace session.
   4. Designing the Dashboard Metrics
Once the data is joined or flagged, you can configure a single, highly visual HR Operations Dashboard with the following :
 
Volume Breakdown (Visibility)
  • Widget Type: Donut / Pie Chart
  • Metric: Total Active/Closed HR Cases group by Assignment Method 

if my response helped, please mark it as the accepted solution so others can benefit as well. 

 

Thanks & Regards ,

Supriya Waghmode 

sanjaygupta
Tera Guru

Hello @sreeha 

You can approach this in the following order, starting with the out-of-the-box options.

1. Check the out-of-the-box AWA dashboard

The Advanced Work Assignment dashboard for Tasks is available through the Performance Analytics - Content Pack - Advanced Work Assignment plugin.

It includes an Auto-Assigned Work Items indicator, with breakdowns by Service Channel and Queue. This is a good starting point, although it may not cover your complete HR Operations reporting requirement.

2. Review AWA Work Items and Events

Navigate to Advanced Work Assignment > Work Item > All.

The Work Items [awa_work_item] table contains useful fields such as:

  • Document ID and Document table: Identify the related case or task.
  • Assigned to, Queue and Assignment group: Show assignment details.
  • State: Accepted, Canceled, Pending Accept or Queued.
  • Canceled reason: Includes Manually assigned.
  • Allocated by: Identifies the user who assigned the work item.
  • Previous Work Item: References an earlier work item for the same document.

AWA Events can provide additional assignment details. Relevant event types include:

  • Assignment
  • Manual Assignment
  • Routing

You can also review Caused By, Timestamp and Event Details to understand who triggered the event and when.

Important: Do not classify every record with a matching AWA Work Item as automatically assigned. A work item can also exist for a manually assigned record, and the Accepted state alone does not prove that the assignment was automatic. A work item canceled with the reason Manually assigned is a useful indicator of manual assignment within AWA.

3. Build a consolidated report

To report on HR Cases together with their associated work items, consider creating a Database View using:

  • sn_hr_core_case
  • awa_work_item

Join the case sys_id with the work item's document_id, and also match the work item's document_table with the HR Case table name.

Use a left join if you want to retain cases that do not have a matching work item.

Keep in mind that a case can have multiple work items over time. To avoid duplicate counts, use distinct case counts or identify the relevant work item for each reporting requirement. The Previous Work Item reference can help trace earlier work items.

4. Consider customization if the out-of-the-box data is insufficient

If the available AWA data does not meet your reporting requirements, consider creating a custom Assignment Method choice field on the HR Case table and HR Task table, if applicable.

Possible values include:

  • AWA Auto
  • AWA Manual
  • Manual / Outside AWA

Populate this field based on verified assignment events and the relevant assignment process, rather than treating every change to Assigned to as a manual assignment.

If historical reporting is required, preserve assignment timestamps and history instead of storing only the latest assignment method.

Test the logic with sample records before implementing it in production.

5. Suggested dashboard metrics

  • AWA vs. manual assignment distribution.
  • Assignment distribution by queue and assignment group.
  • Workload by assigned agent.
  • Weekly or monthly assignment trends.
  • Average time from case creation to assignment.

6. Clarifications to confirm

  • Are HR Tasks (sn_hr_core_task) actually routed through AWA in your instance? The standard HRSD AWA configuration documents HR Case and Chat service channels, so verify whether your HR Tasks use a configured AWA service channel.
  • What should count as manual assignment: assignment outside AWA, manual assignment within AWA, or reassignment of a case that was initially assigned through AWA?

These details will help determine the correct reporting logic for your HR Operations dashboard.