Software Release Notes

There are a number of links to software release notes because 'times they are a changin' and we have moved through the years from static notes through to full multimedia release notes with embedded video.

For TriSys Version 10 release notes, please click here.

For TriSys Version 8 release notes, please click here.

For TriSys Version 7 release notes, please click here.

For TriSys Version 6 release notes, please click here.

For TriSys Version 5 release notes, please click here.



Infrastructure Support And Stuff

Hello Blog Readers,

I will be writing blogs based on our Infrastructure, Support Desk and the TriSys ASP Desktop.

Hopefully I can share with you an insight into what's happening within the Support Desk here at TriSys and pass on helpful hints and tips to help along the way.

We have a new corporate video filmed here in Cambridge which we like.

This will let you see some faces behind the voices.

(Be warned these are frightening images, don't let your children near them)

We also have a Support Website where you can find helpful documentation as well as Training and How-To's.


Did you know that you can autorec a CV from within the TriSys application?

You do not need to send an e-mail to yourself to be able to use the CV Autorecognition Feature!

Firstly, save the CV onto your TriSys drive. Go into the TriSys application and select "CV Autorecognition". Set the "CV Holding Folder" as the one where you put the CV on the TriSys drive. (The CV Folder should be preset (Normally G:\CVData)) You should see your CV within the CV Documents grid where you can highlight it and select "Process CV" and this will take you through the autorec process as you are used to.

Voila !! CV Autorecognition without the hassle of sending e-mails to yourself.

I have found that this is a time saver that some users are unaware of, so I hope that this helps a bit.

Well this is all from me for now, pop back later if you get a mo.

Recruitment Focus


Hello everyone, my name is Joanne Parkin and I will be writing regular posts on the TriSys blog about recruitment.


I will cover a range of topical issues and welcome any feedback readers may have about the subject matter in question.


As it is the first month of the new year, here are the top 10 predictions in recruitment for 2012:

  • 2012 Will Be “The Year of the Mobile Platform”
  • Intense hiring competition will return in selected areas
  • Retention issues will increase dramatically
  • Social media increases its impact by becoming more data-driven
  • Remote work changes everything in talent management
  • The need for speed shifts the balance between development and recruiting
  • Employee referrals are coupled with social media
  • Employer branding returns
  • The candidate experience is finally getting the attention it deserves
  • Forward-looking metrics begin to dominate


 Next week, I will write about the AWR (agency worker regulations), so please subscribe to this blog.

Welcome to January 2012 Newsletter Readers

A warm welcome to TriSys monthly newsletter readers. In future, monthly newsletters will be posted on this blog first, then announced on twitter, then sent in the usual manner by e-mail. It is easy to opt out of the e-mail newsletter by clicking the unsubscribe link.

This blog will grow over time and will contain a whole bunch of topical articles and news about numerous subjects including of course recruitment and technology.

Thank you for taking the time to visit our web site. There are some awesome product videos which give a great, and fun, overview of our products and services, and this is the best place to start if you are new to TriSys.

If you would like to speak to us, please click here at any time to start chatting via the web, or call us on 01223 393 519. We would love to hear from you.

The New Emperors Clothes - Abuse of Web Technology

The inspiration for this blog post was the following set of error messages displayed on an arrivals screen at Brighton, England railway station on Sunday 29th January 2012:

What this shows is a broken arrivals computer system which has been completely over, and badly, engineered for the purpose of displaying information about the arrivals of buses to carry train passengers.

The designers/developers have chosen to build a browser based system with client-side Javascript pulling data asynchronously from a web service. Nothing wrong with that in principal, but for a non-interactive display-only, highly available message board system? I think not, as clearly demonstrated.

The problems shown here are typical and are spreading like wild fire. People, including customers, project managers, inexperienced technical people, and transport staff, all make the same mistake. They think that the web is all about the browser.

This mistaken belief is responsible for the rise (and soon fall) of browser oriented technology, where software houses, designers and developers around the globe, have resorted to breaking all the rules of industrial strength software development in the belief that browser technologies are current 'best-practice'.

What are these current technologies that are not industrial strength?

  • Separation of concerns: Client-side script and web services

Whilst separating display logic from business logic is generally a good principle of software engineering, it is almost impossible to do using the current technologies favoured by the web software development industry today. Client-side code is being implemented in Javascript and is increasingly gaining more and more business logic because changing Javascript is easier that redesigning complex web services. This makes for very unreliable and unmaintainable software, and let us not forget that this business logic is available for all to see.

And what of the display logic? A mixture of HTML, CSS and JQuery is creating code which is utterly unmaintainable and unmanagable, Throw in the mechanism of dealing with the enormous range of web service protocols, document object models (DOM) etc.. and you have a classic spaghetti dish. This is far from the ideal and history teaches us much about what happens when this is the case.

  • Lowest common denominator web service protocols

We have gone from WSDL and ASMX to REST and WCF. XML is being replaced with JSON because it is smaller in size and gets around some browser string problems, but you have to use JSONP to get around many other limitations. So, we are now passing complex data as strings! We get no benefit from sharing classes or strongly typed objects. Another recipe for disaster.

  • Proprietary security protocols

Each browser/web server combination works differently with different security protocols, and oAuth is hard to do properly. You need some good technology on the back end and a good CRM system to manage developer API keys etc.. Web security is always evolving and requires a lot of knowledge, money and time to master. Many projects simply do not have the budget or experienced staff, so instead developers are implementing their own proprietary security mechanisms, resulting in systems which are very fragile and easily hackable.

  • Development and maintenance tool immaturity

For almost thirty years, we have had highly graphical software development tools with more recently intellisense, edit-and-continue, source code analysis tools, memory checkers, garbage collectors etc.. We get almost none of this with Javascript, DOM and JQuery. Developing in these client-side web frameworks is like stepping back in time to a prehistoric age of software development.

  • Script-kiddie mentality and inexperience

Many of the people writing this client-side javascript/jquery/HTML/CSS are young, cheap and inexperienced. They have no concept of industrial strength software design. They do not know or care about reliability or maintenance because they'll be off onto the next job or mountain long before their code catastrophically breaks leaving us with the debris. Good luck to the people who have to fix it under enormous pressure from paying customers, irrate investors and frustrated management.

  • Too much focus on web design at the expense of robustness and reliability

If it looks good, it must be good eh? Wrong! Almost all web designers know absolutely nothing about complex business processes and the provision of reliable data to service those essential business activities. Project managers and customers are easily captivated by something which looks sexy. Web designers know this and use it as a shield to hide the mess that lies beneath the surface.

There are of course many more, but this is a blog-post not a book.

In summary, the new emperors clothes do not fit, are badly designed and will be torn to shreds as more and more people will be affected by this madness. Anyone contemplating building line of business (LoB) or safety (or transport) critical web applications using these technogies should really think again, to put it mildly.