Custom fields on Additional Parties |
What happened previously | What has changed |
Custom fields were not possible on Additional Parties | - Custom fields and groups can now be created for Additional Parties similarly to what can currently be done for Clients, Projects and Project Services.
- Visibility of the fields and whether or not they are mandatory are mappable to either the Party Type or the Person Type, which cannot be changed once the field is created.
- These fields will be visible as mapped on the Additional Party when you open it and are also available on the Additional Parties list view; Service Printout templates can be customised to include them.
- Unfortunately, it is not possible to add the custom fields to step 2 of Intake but in the next release they will be reportable in the DIY Service Additional Parties report.
|
PMT: PMT-971 |
Custom fields on Actions |
What happened previously | What has changed |
Custom fields were not possible on Actions | - Custom fields and groups can now be created for Actions, similar to what can currently be done for Clients, Projects, and Project Services.
- Visibility of the fields and whether or not they are mandatory are mappable to Action Type (standard types only), which cannot be changed once the field is created.
- These fields will be visible as mapped on the Action when you open it and are also available on the Action list view; Printout templates for Actions, Services, and Project Services can be customised to include them.
- In the next release they will be reportable in the DIY Service Actions report.
|
PMT: PMT-971 |
Information, Referral and Triage workflow changes |
What happened previously | What has changed |
It was previously not possible to do the following: - Assign multiple Information/Referral services to one non-client
- Assign an Information, Referral, or Triage service to an existing client at step 3 of intake
- Assign a Triage service to an existing client when converting it to an Information or Referral
- Record client or service keywords during Intake Step 1
- Merge a Non-Client (Non-Clients had to be converted to a Full Client first before they could be merged).
| - Non-Clients can now have more than one Information or Referral service – they can be assigned these services either via Intake or from the Client Services tab of the non-client.
- At Step 3 of Intake, you can choose to Save (creating a new Non-Client) or to select an existing client (including both Full Clients and Non-Clients) when creating an Information or Referral service. Non-Clients will not be selectable for Triage services at Step 3 but Full Clients will.
- Conflict Check will now be available on Triage when you select Information or Referral as the Service Type – you can select an existing client to assign the service to. This feature will be subject to the same merge process that happens currently with other service types (ie there is no option to keep the Triage Client or Full Client at this step and simply move the service to a new client).
- Client and Service Keywords fields will now be visible on Step 1 of Intake
- Non-clients are now selectable in the Client Merge feature; however Full Clients cannot be merged into Non-Clients or Triage Clients. Please note that this process remains irreversible.
|
PMT: PMT-1094 |
Accountability Report Notification workflow |
What happened previously | What has changed |
Accountability reports did not have a clear workflow and not all relevant recipients could be added. | - Reporting bodies can be assigned as many email recipients as there are users in the Admin portal assigned to that reporting body
- The template to confirm submission of an Accountability report now includes all SPM addressees in the ‘To’ field of the email and the Reporting Administrator of the centre in the ‘Cc’ field
- The templates to notify of report Approved and Not Approved now include the Reporting Administrator of the centre in the ‘To’ field of the email and all SPM addressees in the ‘Cc’ field
- Centres are encouraged to open their centre profile in CLASS and review the user set as the Reporting Administrator and update this as required if they use the Accountability module of CLASS
|
