Welcome to Community Week 2025! Join us to learn, connect, and be recognized as we celebrate the spirit of Community and the power of AI. Get the details  

How to create a breakdown based on Task Type?

David Hepburn
Tera Guru

For PA Indicators based on the [task] table (and child tables), how does one create a Task Type breakdown?

David Hepburn, III (he / him) | Paramedic
CSA, Senior Enterprise Application Analyst
ServiceNow DevOps
Children’s Health System of Texas
Dallas, Texas, USA
1 ACCEPTED SOLUTION

David Hepburn
Tera Guru

Since Task Type is not a standard reference field in the [task] table, determining the setup for a Task Type breakdown can prove difficult. There was a post a few years ago here; however, we discovered an easier way to do it.

 

To create a Task Type breakdown, follow these steps. 

 

Create Breakdown Source (1)

  • Name:  Task Type
  • Facts Table:  [sys_choice]
  • Field:  SysID
  • Conditions:
    • element is sys_class_name
    • language is en
    • inactive is false

Create Breakdown (2)

  • Type:  Automated
  • Name: Task Type
  • Breakdown Source:  Task Type

Breakdown Mapping (3)

  • Facts Table:  [task]
  • Field:  Task Type

Add entries to the sys_choice_ table  (4)

  • Create one sys_choice record for each Task Type that needs to appear in the breakdown list.
  • Each record will look like this:
    • Table:  Incident
    • Element:  sys_class_name
    • Language:  en
    • Label:  Incident
      • notice the capital letter at the beginning
    • Value:  incident
      • this is the table name again
    • Sequence:  (this determines the location of this table in the list of breakdown options)
  • Your sys_choice table should look something like (5) when finished

Associate this breakdown with Indicators

  • The Indicator Source must be looking at the [task] table

Finished, working breakdown will look like (6)

 

Task Type breakdown setup.png

David Hepburn, III (he / him) | Paramedic
CSA, Senior Enterprise Application Analyst
ServiceNow DevOps
Children’s Health System of Texas
Dallas, Texas, USA

View solution in original post

2 REPLIES 2

David Hepburn
Tera Guru

Since Task Type is not a standard reference field in the [task] table, determining the setup for a Task Type breakdown can prove difficult. There was a post a few years ago here; however, we discovered an easier way to do it.

 

To create a Task Type breakdown, follow these steps. 

 

Create Breakdown Source (1)

  • Name:  Task Type
  • Facts Table:  [sys_choice]
  • Field:  SysID
  • Conditions:
    • element is sys_class_name
    • language is en
    • inactive is false

Create Breakdown (2)

  • Type:  Automated
  • Name: Task Type
  • Breakdown Source:  Task Type

Breakdown Mapping (3)

  • Facts Table:  [task]
  • Field:  Task Type

Add entries to the sys_choice_ table  (4)

  • Create one sys_choice record for each Task Type that needs to appear in the breakdown list.
  • Each record will look like this:
    • Table:  Incident
    • Element:  sys_class_name
    • Language:  en
    • Label:  Incident
      • notice the capital letter at the beginning
    • Value:  incident
      • this is the table name again
    • Sequence:  (this determines the location of this table in the list of breakdown options)
  • Your sys_choice table should look something like (5) when finished

Associate this breakdown with Indicators

  • The Indicator Source must be looking at the [task] table

Finished, working breakdown will look like (6)

 

Task Type breakdown setup.png

David Hepburn, III (he / him) | Paramedic
CSA, Senior Enterprise Application Analyst
ServiceNow DevOps
Children’s Health System of Texas
Dallas, Texas, USA

Thanks @David Hepburn , this was extremely helpful!