Ideas

Customer Scenario with Pay Awards. A chance to improve functionality and ease of use. Due to the Support staff pay award being settled at 3.2% from September I used this function to update all 10 properties. I then discovered that this only increa...

There should be a way of archiving past Admission Events. We have been using the product for 7 years and so have many events that are over 5 years old. They can be deleted but this deletes all the associated data. Would be good therefore if they c...

Could there be a option to put an end date on the Users On Holiday tick box? Sometimes it can be forgotten to remove the tick once they're back. If the system could automatically do it on the end date entered, this could save some time.

The Admissions Statuses used by a school can change over time. For historic reasons, we would not want to delete statuses no longer in use (since these will be attached to existing applicant records). However, we would no longer want them displaye...

Customers want to report on all different types of data for various reasons, but not all data fields are available in the report builder or in the pre built reports. Giving them the option to choose any field that they have populated with data and...

In V2 that we have just upgraded from you were able to put a full stop and tab to copy the item in the row above. This seems to have disppeared in purchasing. In purchasing you can copy the whole row above but that isnt always useful. We want to b...

The Every HR system could include pre-configured default templates for Green Book and Burgundy Book parental leave policies—similar to how it already supports default sick pay configurations. This would simplify setup for schools using these natio...

I have just been onto support to see why UPN's do not pull through from Applicants in Admissions mgr, when students are transferred across to current. Apparently this is how isams is set up but this an unnecessary duplication of work for support s...

Duplicate Invoice number across locations. Currently the warning only appears when the same number if used on the same location. If this could flag across locations that would save duplicate orders being rasied.

We find the process of creating a new user really long winded and often we miss certain elements. A user friendly function which adds the user to all the right areas of the system with the right access would be amazing.