This document details the redesign of the Report Builder - requests view app included in our latest Data Discovery release.
For the next few months, you will have access to both the old version and new version of the app so you have time to familiarise yourself with the new version before the old version is removed. The new version has a red banner with “new” written in it in the icon for the app:
Our aim with this document is to enable you to:
Familiarise yourself with how to use the new version
Update your Data Discovery report mapping spreadsheets to reflect the new version
Update any bookmarks you have saved
Update any saved views (created using “Monitor in activity center”)
We highly recommend you set aside time to complete these steps over the next 3 months. We are available to provide further support with this, contact us at: support@noted.com
Key Changes Overview
This release focuses on enabling the Report builder - Requests View to support Whanaunga āwhina, a planned Noted feature which will replace the Whānau feature. Improvements to user experience have also been incorporated based on your feedback.
Feature Area | Previous Version | New Version |
Whanaunga āwhina | Not supported | Supported |
User Interface | Cluttered, less intuitive navigation | Streamlined, cleaner design improved navigation |
Line report builder | Large number of columns included by default in report | More flexibility - less columns included by default, more options of what to add |
Look up sheets | Separate sheets for each set of tables | Simplification to one sheet with all look up tables |
Detailed comparison for report mapping
The following tables are designed to assist you in updating your report mapping spreadsheets to the new version. Most of the terminology is similar but dropdowns have been reorganised. Rather than reading through these tables end to end, we suggest that you use them for searching for anything you can’t find in the new version or where you aren’t sure if you’ve found the equivalent to your previous mapping. You may want to use ctrl + F to search for a term from your report mapping to find its equivalent in the new version.
Note: terminology used here is the generic Noted terms, your organisation may have custom words in place of some of these e.g. “Client” may be displayed as “Tangata” or “Whaiora” for your organisation.
Aggregate report builder sheet
Mapping | Old Version | New Version |
Select/define counts: Requests with specific date in period | Get counts of requests sent, followed-up, with decisions, closed = select a button | Define count:
1. Do you wish to count or sum = Count
2. What do you wish to count = Unique Requests 3. What should the counts be based on? = Specific date being in reporting period 4. Which date should be in period? = select an option that matches the button from the old version |
Select/define counts: Requests w. Request date in period | Get counts of requests sent, followed-up, with decisions, closed = select Requests w. Request date in period | Define count:
1. Do you wish to count or sum = Count
2. What do you wish to count = Unique Requests 3. What should the counts be based on? = Specific date being in reporting period 4. Which date should be in period? = Request date |
Select/define counts: Requests w. Request decision date in period | Get counts of requests sent, followed-up, with decisions, closed = select Requests w. Request decision date in period | Define count:
1. Do you wish to count or sum = Count
2. What do you wish to count = Unique Requests 3. What should the counts be based on? = Specific date being in reporting period 4. Which date should be in period? = Request decision date |
Select/define counts: Requests w. Request outcome date in period | Get counts of requests sent, followed-up, with decisions, closed = select Requests w. Request outcome date in period | Define count:
1. Do you wish to count or sum = Count
2. What do you wish to count = Unique Requests 3. What should the counts be based on? = Specific date being in reporting period 4. Which date should be in period? = Request outcome date |
Select/define counts: Requests w. Request followup date in period | Get counts of requests sent, followed-up, with decisions, closed = select Requests w. Request followup date in period | Define count:
1. Do you wish to count or sum = Count
2. What do you wish to count = Unique Requests 3. What should the counts be based on? = Specific date being in reporting period 4. Which date should be in period? = Request followup date |
Select/define counts: Follow-ups in period | Get counts of requests sent, followed-up, with decisions, closed = Follow-ups in period | Define count:
1. Do you wish to count or sum = Count
2. What do you wish to count = Unique Request follow-ups 3. What should the counts be based on? = Specific date being in reporting period 4. Which date should be in period? = Request followup date |
Select/define counts: Unique Tangata Requests with specific date in period | Get counts of requests sent, followed-up, with decisions, closed = select a button | Define count:
1. Do you wish to count or sum = Count
2. What do you wish to count = Unique Tangata 3. What should the counts be based on? = Specific date being in reporting period 4. Which Tangata should be counted? = select an option that matches the button from the old version |
Select/define counts: Unique Tangata w. Requests w. Request date in period | Get counts of requests sent, followed-up, with decisions, closed = select Unique Tangata w. Requests w. Request date in period | Define count:
1. Do you wish to count or sum = Count
2. What do you wish to count = Unique Tangata 3. What should the counts be based on? = Specific date being in reporting period 4. Which Tangata should be counted? = Tangata at Request date 5. Which date should be in period? = Request date |
Select/define counts: Unique Tangata w. Requests w. Request Decision date in period | Get counts of requests sent, followed-up, with decisions, closed = select Unique Tangata w. Requests w. Request Decision date in period | Define count:
1. Do you wish to count or sum = Count
2. What do you wish to count = Unique Tangata 3. What should the counts be based on? = Specific date being in reporting period 4. Which Tangata should be counted? = Tangata at Request date 5. Which date should be in period? = Request decision date |
Select/define counts: Unique Tangata w. Requests w. Request Outcome date in period | Get counts of requests sent, followed-up, with decisions, closed = select Unique Tangata w. Requests w. Request Outcome date in period | Define count:
1. Do you wish to count or sum = Count
2. What do you wish to count = Unique Tangata 3. What should the counts be based on? = Specific date being in reporting period 4. Which Tangata should be counted? = Tangata at Request date 5. Which date should be in period? = Request outcome date |
Select/define counts: Unique Tangata w. Requests w. Request followup date in period | Get counts of requests sent, followed-up, with decisions, closed = select Unique Tangata w. Requests w. Request followup date in period | Define count:
1. Do you wish to count or sum = Count
2. What do you wish to count = Unique Tangata 3. What should the counts be based on? = Specific date being in reporting period 4. Which Tangata should be counted? = Tangata at Request date 5. Which date should be in period? = Request followup date |
Select/define counts: Requested amounts, received amounts with specific date in period | Get Requested amount and Received of request amount counts and sums = select a button | Define count:
1. Do you wish to count or sum = Sum up numbers
2. Which numbers would you like to sum up? = select an option that matches the button from the old version |
Select/define counts: Requested amount w. Request date in period | Get Requested amount and Received of request amount counts and sums = Sum Requested amount w. Request date in period | Define count:
1. Do you wish to count or sum = Sum up numbers
2. Which numbers would you like to sum up? = Requested amount w. Request date in period |
Select/define counts: Received of requested amount w. Request outcome date in period | Get Requested amount and Received of request amount counts and sums = Sum Received of requested amount w. Request outcome date in period | Define count:
1. Do you wish to count or sum = Sum up numbers
2. Which numbers would you like to sum up? = Requested amount w. Request outcome date in period |
Select/define counts: Requests w. Requested amount=Received of requested amount w. Request outcome date in period | Get Requested amount and Received of request amount counts and sums = Requests w. Requested amount=Received of requested amount w. Request outcome date in period | Define count:
1. Do you wish to count or sum = Sum up numbers
2. Which numbers would you like to sum up? = Received of requested amount - Requested amount w. Request outcome date in period |
Select/define counts: Requested amount w. Request outcome date in period | Get Requested amount and Received of request amount counts and sums = Sum Requested amount w. Request outcome date in period | Define count:
1. Do you wish to count or sum = Sum up numbers
2. Which numbers would you like to sum up? = Received of requested amount w. Request outcome date in period |
Breakdown options | Reporting period breakdown options - report date breakdown | Reporting period breakdown options - report date breakdown. Dropdowns have the same options |
Breakdown options | Static demographic options - gender, age, ancestral root/whakapapa | Tangata info options: 1. Select which Tangata the breakdown info should be for. If counting unique Tangata, make sure your count options match. = select an option from the dropdown that is appropriate for your needs 2. Select Tangata information - you can now select gender, age, ancestral root/whakapapa |
Breakdown options | Interval type options - Responsible Kaimahi | Responsibility info options true on Request date - Breakdown by Responsible Kaimahi at time of Request date |
Breakdown options | Interval type options - Tangata role lvl1 | Tangata info options: 1. Select which Tangata the breakdown info should be for. If counting unique Tangata, make sure your count options match. = select an option from the dropdown that is appropriate for your needs 2. Select Tangata information - Tangata role lvl1 |
Breakdown options | Interval type options - Tangata role lvl2 | Tangata info options: 1. Select which Tangata the breakdown info should be for. If counting unique Tangata, make sure your count options match. = select an option from the dropdown that is appropriate for your needs 2. Select Tangata information - Tangata role lvl2 |
Breakdown options | Interval type options - Tangata’s tag name | Tangata info options: 1. Select which Tangata the breakdown info should be for. If counting unique Tangata, make sure your count options match. = select an option from the dropdown that is appropriate for your needs 2. Select Tangata information - Tangata’s tag name |
Breakdown options | Interval type options - Client role lvl1, Client role lvl2, Client’s tag name | Client specific info options 1. Select which Client info should be used for breakdown = Client at Request date (can always use this unless your report has Whanaunga āwhina) |
Breakdown options | Request related data options - Request related info | Request info options - Breakdown by Request info |
Breakdown options | Team pathway/Wellbeing pathway related data options - Team pathway name | Pathway info options - Breakdown by Team pathway info - Team pathway name |
Breakdown options | Team pathway/Wellbeing pathway related data options - Wellbeing pathway goal Wellbeing aspect | Pathway info options - Breakdown by Wellbeing pathway info - Wellbeing pathway goal Wellbeing aspect |
Breakdown options | Team pathway/Wellbeing pathway related data options - Wellbeing pathway action name | Pathway info options - Breakdown by Wellbeing pathway info - Wellbeing pathway action name |
Line report builder sheet
Mapping | Old Version | New Version |
Select Requests, Waitlistings and/or Team pathways: Request date in period | How to relate reporting period to Requests = Request date in period | How should Requests relate to the reporting period 1. How should Requests, Waitlistings, and/or Team pathways relate to the reporting period? = Specific date being in reporting period 2. Which date should be in period = Request date |
Select Requests, Waitlistings and/or Team pathways: Request decision date in period | How to relate reporting period to Requests = Request decision date in period | How should Requests relate to the reporting period 1. How should Requests, Waitlistings, and/or Team pathways relate to the reporting period? = Specific date being in reporting period 2. Which date should be in period = Request decision date |
Select Requests, Waitlistings and/or Team pathways: Request followup date in period | How to relate reporting period to Requests = Request followup date in period | How should Requests relate to the reporting period 1. How should Requests, Waitlistings, and/or Team pathways relate to the reporting period? = Specific date being in reporting period 2. Which date should be in period = Request followup date |
Select Requests, Waitlistings and/or Team pathways: Request outcome date in period | How to relate reporting period to Requests = Request outcome date in period | How should Requests relate to the reporting period 1. How should Requests, Waitlistings, and/or Team pathways relate to the reporting period? = Specific date being in reporting period 2. Which date should be in period = Request outcome date |
Select Requests, Waitlistings and/or Team pathways: Request awaiting decision at start of period | How to relate reporting period to Requests = Request awaiting decision at start of period | How should Requests relate to the reporting period 1. How should Requests, Waitlistings, and/or Team pathways relate to the reporting period? = Active at start, end or any time during reporting period 2. How should the Request be active? = Requests without Request decision date 3. When should the Requests be active? = At start reporting period |
Select Requests, Waitlistings and/or Team pathways: Request awaiting decision at any time in period | How to relate reporting period to Requests = Request awaiting decision at any time in period | How should Requests relate to the reporting period 1. How should Requests, Waitlistings, and/or Team pathways relate to the reporting period? = Active at start, end or any time during reporting period 2. How should the Request be active? = Requests without Request decision date 3. When should the Requests be active? = Any time during period |
Select Requests, Waitlistings and/or Team pathways: Request awaiting decision at end period | How to relate reporting period to Requests = Request awaiting decision at end period | How should Requests relate to the reporting period 1. How should Requests, Waitlistings, and/or Team pathways relate to the reporting period? = Active at start, end or any time during reporting period 2. How should the Request be active? = Requests without Request decision date 3. When should the Requests be active? = At end reporting period |
Add static Tangata demographic information and Location | Select Tangata static demographics = select appropriate item from dropdown | Tangata information 1. Select which tangata should be added = Select the most appropriate option 2. Select Tangata information = select the most appropriate option - age, ethnicity, gender, iwi/hapu |
Add information to report | Select Tangata location info (only residential) - city, address, suburb | Tangata information 1. Select which tangata should be added = Select the most appropriate option 2. Select Tangata Location info (only residential) = select the most appropriate option - city, address, suburb |
Add information to report | Add interval type information - Add Tangata’s tag name = Yes | ? |
Add information to report | Add interval type information - Add Responsible Kaimahi = Yes | Responsibility at Request date information - Add Responsible Kaimahi at time of Request date = Yes |
Add information to report | Add Request information - Add Request info | Request information - Add Request info: Dropdowns appear with the same options as the old version plus additional ones. |
Add information to report | Add Team pathway information - Add Team pathway info | Pathway at Request date information - Add Team pathway info: Dropdowns appear with the same options as the old version |
Add information to report | Add Wellbeing pathway information - Add Wellbeing pathway info | Pathway at Request date information - Add Wellbeing info: Dropdowns appear with the same options as the old version |
Look up sheets
Mapping | Old Version | New Version |
How to relate reporting period… | Same mapping as line report builder - | See rows for “Select Requests, Waitlistings and/or Team pathways” |
Sheets to tables | Request related information sheet | 1. Look up sheet 2. Request information |
Sheets to tables | Client information sheet | 1. Look up sheet 2. Whanaunga āwhina and Tangata information |
Sheets to tables | Interval type information sheet | 1. Look up sheet 2. Responsibility and Contingency plan information, Whanaunga āwhina and Tangata information tables 2. Responsibility and Contingency plan information tables OR Whanaunga āwhina and Client information tables (Note that tabs from the Interval type information sheet have been split out across these two tables) |
Sheets to tables | Team and Wellbeing pathways sheet | 1. Look up sheet 2. Team pathway, Financial pathway and Wellbeing pathway information table |