Jump to content

CRITICAL: Capita has released the Summer upgrade to all our schools! SOLUS3


Recommended Posts

Posted

If you're an Authorising LA and release the upgrads to your schools and are using SOLUS3, you may well find Capita have released the upgrade directly to them!!! :mad:

 

Check your SOLUS3 LA DS. In some instances Capita have ONLY released the database upgrade! We have auto deploy enabled accross the board!!!

Posted
If schools have their SLG hosted at County and get the SIMS Summer upgrade before the SLG has been upgraded, it will break. Also, it seems a large amount of schools have ONLY had the SIMS Summer database release authorised meaning the database could potentally upgraded to Summer 2015 and everything else will be left on spring breaking it completely.
Posted

Full release and database for us, which to be honest is fine.

 

I'd prefer for it to be released now so that the Exams team can use it for a week before the summer break, rather than us having to wait til after results day to apply it "just in case something broke"

Posted (edited)
Full release and database for us, which to be honest is fine.

 

I'd prefer for it to be released now so that the Exams team can use it for a week before the summer break, rather than us having to wait til after results day to apply it "just in case something broke"

 

The Results day survival kit seemed to imply you needed Summer 2015 to process results if you're using Exams Organiser.

 

edit: From the mini guide released 16-06-15.

Procedures to Complete Before Results Day

  • Upgrade to the SIMS 2015 Summer Release to install the latest version of SIMS and Examinations Organiser.

 

am I reading that right @PhilNeal?

Edited by pete
Posted
You will need the summer release to get the correct analysis. However, the release should not have been issued by-passing support units. There was a change in our manager software that wasn't clearly communicated to our release manager - hence the mistake.
Posted
There was a change in our manager software that wasn't clearly communicated to our release manager - hence the mistake.

 

Guess he didn't read the release notes first :p

  • Thanks 2

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...