Should you have any questions about the latest release, don't hesitate to contact your Client Success Manager or Customer Support via our support centre.
Expected Date/s of Release
-
Phase I - Mon 01 November 2021
-
Phase II - Mon 08 November 2021
The most significant changes are:
- We've improved the Smart Fee Modifier Logic for Per Nominal Hour (PNH) Calculations.
- Validation on Smart Fees, added to an Enrolment, will now correctly enforce the set rules.
- We've added filters to the Smart Fee Override Links.
- We've modified the Outcome Type ID fields for Units, Subjects, and Elements in the Enrolment API.
- The Victorian AVETMISS NAT120 File will now contain any Smart Fees linked to the Unit.
- We've added a new API Endpoint to allow users to List and Retrieve Outcome Types.
- We've made improvements to the Batch Log output for importing Smart Fees. It's now easier than ever to identify any failed records.
- We've made improvements to the Smart Fee Export and Import process. There is now better handling for Smart Fees that have the Invoice Trigger turned off.
- We've made it possible to search for a Smart Fee by name using the Audit Trail.
New
Nothing new to see here.
Improved
-
We've improved the Smart Fee Modifier Logic for Per Nominal Hour (PNH) Calculations.
We've improved the Smart Fee Modifier Logic better to handle the Per Nominal Hour (PNH) calculations. This update will make it possible to apply Modifiers at an Individual Unit Level.
This will only occur if the Smart Fee has a Category that is not Subject or Academic Period. You must set the Smart Fee Multiplier to Per Nominal Hour (PNH).
-
Validation on Smart Fees, added to an Enrolment, will now correctly enforce the set rules.
Validation on Smart Fees, added to an Enrolment, will now correctly enforce the following three rules:
Rule #1 - The Smart Fee must have a Ledger Code.
Rule #2 - The Smart Fee can not have one of the following 'Unit' invoice triggers unless the Smart Fee has a Category of Unit: (1) Enrolment Unit Start, (2) Enrolment Unit Completion, or (3) Enrolment Unit Outcome with Trigger Invoice Flag.
Rule #3 - The Smart Fee can not have one of the following 'Units of Study' or 'Subject' invoice triggers unless the Smart Fee has a Category of Subject: (1) Enrolment Subject Start Date, or(2) Enrolment Subject Census Date.
-
We've added filters to the Smart Fee Override Links.
When Link Types are added to the Links window, the Smart Fee Override Links will only show those values that you already applied under Links. If a value is now selected, all values will apply.
For example, if a Smart Fee is only linked to Location A, we will only show Location A in the Override Rules Location Link Type dropdown.
-
We've modified the Outcome Type ID fields for Units, Subjects, and Elements in the Enrolment API.
The Outcome Type ID field will now be read-only. It will no longer be possible to write or update this value. You will be able to set the Outcome Code, Outcome Code and Name, or Outcome Name for any Unit, Subject, or Element when creating or updating an Enrolment via the API. Returns for all API Calls will remain unchanged.
-
The Victorian AVETMISS NAT120 File will now contain any Smart Fees linked to the Unit.
In addition to any Unit Fees, the Victorian AVETMISS NAT120 File will now contain any Smart Fees linked to the reported Unit. The system will report this as:
(1) An hourly rate in the Tuition Fee field when the Smart Fee has a type with the Reporting Type set to Tuition.
(2) A total rounded to the nearest dollar in the Resource Fee field when the Smart Fee has a type with the Reporting Type set to Resource.
Additional validation has been added to the Tuition Fee and Resource Fee fields for the Victorian AVETMISS NAT120 File:
(1) A validation warning will show if the Tuition Fee for a unit is greater than $999.99 per hour. If you attempt to export the NAT00120 file with a number in this field greater than $999.99, it will put "ERROR" text in that field in place of the usual five digits.
(2) A validation warning will show if the Resource Fee for a unit is greater than $99,999. If you attempt to export the NAT00120 file with a number in this field greater than $99,999, it will put "ERROR" text in that field in place of the usual five digits.
-
We've added a new API Endpoint to allow users to List and Retrieve Outcome Types.
-
We've made improvements to the Batch Log output for importing Smart Fees. It's now easier than ever to identify any failed records.
-
We've made improvements to the Smart Fee Export and Import process. There is now better handling for Smart Fees that have the Invoice Trigger turned off.
Smart Fees, where the Invoice Trigger is toggled off, will not display any data for the Trigger related fields, but the columns will still be visible. For example:
When Importing Smart Fees, the Invoice Trigger specification will be ignored if the Trigger Enabled column is set to FALSE. For example:
When Smart Fee Invoice Trigger is enabled, the export displays the following fields:
-
We've made it possible to search for a Smart Fee by name using the Audit Trail.
Fixed
- 21243 - Previously, there was an issue that prevented a user from clearing the Absent Reason when updating a Parties attendance from Absent to Present on the Edit Attendance page for a Party Record. This issue has been resolved.
- 21962 - Previously, there was an issue where, in some instances, it would cause the Client Identifier - Apprenticeships field to report the Training Contract Identifier upon generating a National AVETMISS File Extract. This issue has been resolved.
- 21955 - Previously, there was an issue when extracting the AVETMISS NAT120 File for South Australia. The issue would cause the Client Identifier - Apprenticeships in the NAT120 File to be reported with the Training Contract Identifier instead of the Client Identifier. This issue has been resolved.
- 20661 - Overall, changes have been made to improve the security of the system. More specifically, sanitising the input to ensure XSS can not be used on several pages.