The post Chris21 Upgrade 8.19 – Tips for Your Upgrade appeared first on System Logic.

As you will be aware, each year you are required to upgrade your version of Chris21 and other modules, in particular HR21. This time around, the Chris21 version 8-10 upgrade is due. These annual upgrades are especially relevant for legislation and taxation changes, but will also include new features, enhancements and other improvements in the software.

The Chris21 and HR21 upgrades must be performed before the end of financial year 2017. Ideally you will already have the software and are planning the upgrade to fit in with your resourcing.

It’s always best to try to get the upgrade under way as early as possible so that you have time to address any issues from testing and so that you have a stable system prior to your end of year processing.

Chris21 version 8-10 upgrade information

The latest Chris21 upgrade is version 8-10-1 and has been available since late last year. This is the version that is released on CD and is referred to as the base release. Subsequent updates are released to address issues that are found in the base release. These are known as engine updates. At the time of writing, the latest engine update is version 8-10-08.

As you can see, the engine updates come thick and fast. It’s a good idea to install the most recent engine update because with the latest update you will have the most stable version of the software. Furthermore, if you find an issue from your testing, you can be sure that there are no new releases available that may address your issue.

HR21 version 3.14.1 upgrade information

Similar to Chris21, HR21 is regularly updated from the base version. The base version is 3.14.1.0 and is included on the Chris21 version 8-10 upgrade CD.

The latest HR21 update is version 3.14.4.0 (at the time of writing). As mentioned, HR21 is updated on a regular basis so it’s a good idea to keep on top of this and install the latest version as soon as possible.

Database option users – SQL or Oracle

This Chris21 version 8-10 upgrade is quite significant, especially if you use the database option. There are some major changes to the database that may impact interfaces or reports from your Chris21 SQL or Oracle database. I am currently helping clients with their upgrades and can say that the release notes make for some quite heavy reading, there’s a lot to get through!

Some things to note:

• It’s always a good idea to upgrade your test environment first and run test scripts. Make sure your test system has a recent copy of your Production DAT directory before upgrading.
• Consider archiving before you start. This will reduce the size of your database which in turn will speed up the upgrade process. See my blog Chris21 Archiving – the Pros and Cons for more information.
• If you are using the database option, I always recommend moving your database to the native Vision format before beginning the upgrade. You can then back up your DAT directory and you have more control over the upgrade process. Move the database back to SQL or Oracle once the upgrade has been completed without errors.
• If you are using the database option, make sure you read the “New Upgrade Process – Read Me First” document. You will find this in the documents section of the upgrade CD.
• Make sure you run the Data Dictionary Changes Impact (DDI) and Data Functions (DBF) functions after upgrading.
• After running DDI and DBF you should carefully check your customisations. Sometimes things will go wrong and this can mean overlapping data or customised fields disappearing. The way to do this properly is by visually checking the upgraded version against your Production environment, form by form. If you do find a lot of problems with your customisations, it could be that they were not not done properly. Have a read of my blog Chris21 Customisations – Do it Right! for help with this.
• Thorough testing by Payroll is vital. As a bare minimum you should run a payrun in the upgraded version and check the results.
• HR21 is updated as a fresh install each time. Therefore, you will need to copy back in any customisations, such as images and changes to stylesheets.

The release notes have further information regarding pre and post upgrade checklists.

Let us know if you have found any issues with your Chris21 version 8-10 upgrade or indeed if you have solutions to problems you have encountered. This could be very useful for your fellow Chris21 users who are reading this blog.

Please feel free to contact us at System Logic if you would like to take advantage of our consulting services to help with your Chris21 upgrade. Or if you simply have a question, you can post a comment below and I will do my best to find you an answer.

The post Chris21 Version 8-10 Upgrade – Some Helpful Information appeared first on System Logic.

The Chris21 payroll upgrade seems to have gone well and after logging in everything looks ok. Testing is underway when you receive an email from the Payroll department. Something doesn’t look right…

Having been involved in the Chris21 payroll upgrade process for many years, and given that we are at that time of year when upgrades should be underway, if not completed, I thought I would share some of my experiences on what is an ‘interesting’ time of year for many clients.

Interesting might be an understatement, as some clients will find themselves perilously close to end of year processing responsibilities, while still finalising upgrades.

While the vendor will usually endeavour to release software upgrades half way through the financial year, it will not always be possible for clients to consider upgrading at this time due to other priorities. As the end of financial year approaches and clients begin their testing in earnest, then the issues in the software are discovered.

Unfortunately, it’s very difficult for users to find out what the current issues are. I know that a lot of clients are frustrated to discover they are testing and uncovering issues that are already known to the vendor.

The problem is, effective planning goes out the window as clients become dependent on the vendor to fix issues and release updates. And of course, updates mean even more testing. Add to this the fact that an upgrade is usually mandatory and the pressure is on the client to get the upgrade completed prior to the end of the financial year.

To overcome this, some customers will request that they be exempted from the upgrade until bugs are fixed and they are provided with a stable version of the software. The vendor will resist this – all clients on the same version of the software is the ideal from the vendor’s point of view. The customer, of course will see this differently. They want to be confident that the payroll system is doing what it is supposed to without manual workarounds.

So what’s the answer to a successful, stress free upgrade? I’m not sure that there is such a thing but here are some ideas:

• Try to start your testing as early as possible. You might not like the idea of being the guinea pig but the truth is you will get an early feel for what this particular upgrade will be like and can report issues early.

• Talk with other organisations that use Chris21. Some may have started their upgrades, and if not, they will be keen to hear about your experiences. The chairperson of your state’s user group is also a good contact point.

• Use Google. There’s more relevant information about Chris21 on the internet than you might think! Search for Chris21 forums or blogs, like this one.

Is there anything you could add to this list? Have you experienced problems with your upgrades? I would be interested to know your thoughts.

I’ll be putting more information in future blogs that will help Chris21 users. If you need help please don’t hesitate to contact me, tony.danher@systemlogic.com.au or call 0421 817 265. Good luck with your upgrade!

The post Chris21 Payroll Upgrade and the Customer appeared first on System Logic.

To help out I have created a new forum specifically for the Chris21 version 8 upgrade. If you are already a registered forum user you can log in and will notice the new forum under the Chris21 Upgrades category. If you are not yet a member register now to gain access to all of the information available on the Chris21 support forum.

I encourage you to share your experiences as you move through the upgrade process. If you find an issue it will be very useful for other Chris21 users if you can take the time to create a topic. Others will no doubt find the same issue and may come to the forum looking for answers. Likewise, if you post a question it’s also likely that someone else will already have the answer

The more users contributing to the forum the more successful it will be. I will of course update the forum with any useful information I come across as I work with clients on their upgrades.

I am available if you need help with your upgrade. It’s a big job to undertake, especially considering that significant testing should be undertaken to identify any issues. I can help you work through the process with less stress! Email me at tony.danher@systemlogic.com.au or phone me on 0421 817 265.

The post New Forum to Help With Your Chris21 Version 8 Upgrade appeared first on System Logic.

It’s always best to try to get the Chris21 upgrade under way as early as possible so that you have time to address any issues from testing and so that you have a stable system prior to your end of year processing.

This upgrade is quite big – by big I mean there are quite a few enhancements and fixes from previous versions. I am currently helping clients with their upgrades and can say that the release notes make for some quite heavy reading, there’s a lot to get through!

Some things to note:

• It should go without saying that you must upgrade your test environment and run test scripts. Make sure your test system has a recent copy of your Production DAT directory before upgrading;

• Consider archiving before you start. This will reduce the size of your database which in turn will speed up the upgrade process. See my blog “Chris21 Archiving – the Pros and Cons” for more information;

• If you use the database option I always recommend moving your database to the native Vision format before beginning the upgrade. You can back up your DAT directory and you have more control over the upgrade process. Move the database back to SQL or Oracle when the upgrade has been completed without errors;

• Make sure you run the Data Dictionary Changes Impact (DDI) and Data Functions (DBF) functions after upgrading;

• Even after running DDI and DBF you should still carefully check your customisations. Sometimes things will go wrong and this can mean overlapping data or customised fields disappearing. The way to do this properly is by visually checking the upgraded version against your Production environment, form by form;

• For Payroll, testing is vital. You should have test scripts but as a bare minimum you will want to run a payrun in the upgraded version and check the results.

• Don’t forget HR21. This will also need to be upgraded. Usually this is done as a fresh install so you will need to copy in any customisations, such as images and changes to stylesheets.

The release notes have further information regarding pre and post upgrade checklists.

Please feel free to contact me at tony.danher@systemlogic.com.au if you need help with your Chris21 upgrade. Or if you have a quick question, post a comment below.

The post Chris21 Upgrade Help appeared first on System Logic.