Skip to main content
All CollectionsRelease NotesSoftware Release Notes
IINSIGHT 6.3.4 Release Notes - May 2021
IINSIGHT 6.3.4 Release Notes - May 2021
Updated over 8 months ago

IINSIGHT release 6.3.4 (May 2021), brings you the following new features:

Setting Multiple Concurrent Plans

Previously on a case file on IINSIGHT it was only possible to have 1 active plan at a time. With the additional function included in release 6.3.4 it is now possible to run Multiple Concurrent Plans on a case at the same time.

If you have an existing plan on a case that is set as a Scheduled or Current bill to plan in section f):

mceclip1.png

When you create and save a new plan as Scheduled or Current bill to plan, you will now see a new popup box asking you if you want the new plan being created to be Current or Concurrent:

mceclip2.png

If you select Current, the plan(s) will work much in the same way as they do already on IINSIGHT with the new plan replacing the old / previous plan(s) on the case:

mceclip4.png

Where as if you select Concurrent then the new plan will run at the same time as any existing plans on the case already:

mceclip3.png

The same current plan window offering you the option to select if you want the plan to run as Current or Concurrent, is offered when changing a "Draft" or "Closed/not in use" plan to one of the above outlined status also.

This can be performed either via the "Details" in the Plan Edit window, or by using the Current button with a plan selected (highlighted in blue) in the plan table:

mceclip5.png

If this Plan is the first plan to be created on the case, or it is being created as "Draft" or "Closed/not in use", then this popup window with the current/concurrent options will not be provided as they are not required.

Billing against Concurrent Plans

When Employees select their Billable actions on a case and Multiple Concurrent Plans are running, the billing drop down options will remain very familiar to them, however now they will be able to select costs from any of the active plans on the case.

These options will be shown in the Billing Window:

mceclip8.png

...the Group Billing Window:

mceclip15.png

..when accessing the Billing Window from the Timesheets and Finance areas:

mceclip9.png

...and when linking a billing via an Appointment:

mceclip10.png

All user level Permissions and Role Settings will be applied to all these areas as normal.

Further information on these different billing options, and the impact of Roles, can be found in our following articles on Grouped Billings, Timesheets, Appointments and Roles.

Ability to manually "Close" a Plan

Previously on IINSIGHT it was only possible for a plan to be closed automatically when reaching completion, or being replaced by a Scheduled Plan.

This wasn't always ideal as circumstances throughout a cases life change and it is often required to change plan requirements, or remove them all together, on a more ad-hoc basis.

To allow this a new plan state has been added called "Closed/not in use", and this can be found under section f) of the plan details when both creating a new plan in the Plan New window, or modifying an existing plan via the Plan Edit window:

mceclip11.png

When this plan state is selected the status icon on the plan will show as Closed:

mceclip13.png

And the plan will have no impact on the billable options on the case any further.

New Case List Filter "My Team Cases"

There is a new default Case List Filter called "My Team Cases" available in the Case List area:

mceclip12.png

Employees that have the permission "Can Access all Cases assigned to this Employee's Team" enabled on their user account, will be able to quickly filter to see these cases in their Case List table using this drop down option.

This permission can be found in the Admin > Manage Users > User Access tab or the Admin > Manage Profiles area, and further information on User permissions in general can be found in our articles on User Accounts, and further information on the Case List and views can be found in our article on the Case List Overview.

Did this answer your question?