...
We are introducing new functionality soon, in the form of Assessment Milestones; we have extended schemas to provide a list of the required uploads needed as part of the assessment, along with a method of creating rules around when an upload needs to be received by e.g. max 3 days after Gateway.
Structured uploads to make it easier for users to provide the correct information
The system has been enhanced to allow the configuration of assessment milestones. These milestones can be configured against assessment components, to provide a more granulated break down of the tasks required, and allows for optional rules to be configured that give guidance as to when these milestones must be met.
...
The regular “Save” button has been replaced with two new buttons:
“Save & Continue” and “Save & Exit”
Save & Continue, saves the assessment schema and returns the user to the same edit screen, to allow further changes to be made.
Save & Exit, saves the assessment schema and returns the user to the main schema listing page.
Once an assessment schema has been saved, the new “Manage Milestones” button appears against each added component in the components table. (see below image)
Clicking this manage button will show the screen used for configuring milestones and rules, which has the following functionality:
Add component drop down (not available in restricted edit mode): allows the adding of any configured milestones against this assessment component.
Added milestones can be removed via the red bin icon (not available in restricted edit mode).
The Assessment type milestone is added to all new components by default, as this must take place.
Add rule button: adds a blank rule line to allow configuration of a new rule.
Added rules can be removed via the red minus icon.
Rules are added to the system using the dropdown options and input fields, to create sentence style rules. i.e.: Finish Max 5 Days After Gateway.
Rules can be configured to rely on other milestones being completed.
If in view mode, the manage button is replaced with a view button, which can be used for display purposes only.
...
Within this sidebar, any File Upload type milestones can have files uploaded against them.
Internal users are able to select a file as the “Selected Version”, completing the milestone. This will allow you to see some form of versioning history with the documents uploaded.
...
Assessment type milestones are automatically completed by the system when a result is published.
Logging of Milestone Success/failure
With the introduction of assessment milestones (detailed above), the system will attempt to calculate a due date using the rules that have been configured against a particular schema’s milestones. These due dates are then compared against the date in which the milestone was completed, to determine whether the milestone was completed in time.
...
Note: if no rules have been set the milestones will still appear on the Assessment Profile in the checklist.
Frontend enhancements/Restrictions
The following additional enhancements have been made to the assessment profile area, related to the new assessment milestones.
External users (i.e. Providers) can no longer select a file version & complete a file upload type milestone.
The programme checklist has been enhanced to show the milestones (along with their completed status) against each one.
These are displayed as sub items under each component, in the order specified.
...
Restructure data to allow logging of milestone success/failure.
Added functionality to the new milestones development to store element milestones against each component – this is an internal change that will allow for reporting on milestone delivery success in a later ticket.
Complete assessment milestone on result publish
The milestones development has been enhanced to record an assessment milestone being completed, when a result is made available. This is triggered via both the QA being published, or the result being published (in the situation where no QA is required).
Operations Report
A new operations report has been created as part of the milestones work:
...
A pre-existing bug has also been fixed, that caused the user search to potentially look at the incorrect table when searching by email address. This ticket should now force all user information to be taken from the same table.
Entity Report
We have added two new reports;
...