[sims] CR #1403-1295841 - Populate communicatee field on comms log with linked contacts

[pete]

Short version - the communicatee field in the communications log for a given student should automatically populate with linked contacts in a dropdown and then offer to search for someone else.

 

Currently you have to manually search for the communicatee by name and hope they're not called Smith.

 

Given SIMS already knows which student you're referring to if you use the Student Details > Communications Log route, I shouldn't have to search unless I want to add someone who isn't a linked contact.

 

The change request I found on Supportnet is CR #1403-1295841. Mind supporting it?

 

cheers

[vikpaw]

+2 for you sir.

[mercer77]

Any idea if this is being considered two years on? Our school is just starting to use the communication log and this makes a simple task often difficult, particularly if you've typed your log, then realise that the parent has a different name to the child and you don't know what it is as you have to go back out of the window to find out what it is, then start again. Alternatively, the communicatee could just be non-required field. As long as the record is linked to the student it often doesn't particularly matter who you've spoken to.

[Esteban_Child_of_the_Sun]

It's only got 24 votes in the last 2 years so is unlikely to be high on Capita's priority list. Generally Change Requests with 50+ votes get the attention.

[SouthCoastSaint]

It shouldn't need a change request - it's flawed functionality. What if you have 3 John Smiths at school, all parents. No way of knowing if you are picking the correct one!

[pete]

^ There's a lot of flawed functionality in SIMS (off the top of my head - 1) lack of audit trails and 2) including personal data (DOB) in class lists by default, with no option to change that default school-wide).

 

Experience shows that unless enough people moan about it, it doesn't get fixed. And even then it might not.

[SouthCoastSaint]

I must say, I had a moan on here (and supportnet) about the use of UPNs which we do as the Admission Number was not matching properly when importing from CSV... and it was picked up by Capita. I have now received a patch which does seem to have solved the problem and is being included in the next release.

 

It's not often this happens, so it's worth mentioning I think

[tech-man]

+1 - makes good sense to me