Sunset Programming, Inc.

In the case where a user starts a call, and saves it without a stop time, then completes the call at a later time, the Contact record was left locked in error. This patch corrects. Note that in normal operation, had that user moved through menu choices in HRP, the lock would have been cleared – usually escaping notice. This fix is recommended for ALL CRM USERS.

When you receive a 134 error message in the Imaging application, it usually occurs when you update the Image Type Collection Maintenance screen to look for a new DocType or Image Type but the new DocType was not built.
If this is the case and you need to build the new Image Type, refer to the Blog entry on setting up a new Image Type on this blog.

If you receive a 130 database error while processing images, there are 3 likely reasons.
1. All Database seats are currently occupied.
2. RedBack is offline.
3. The DocType listed does not support all the indexed fields sent to the server.

To resolve the error check to make sure there are database seats available and RedBack is online and running. This will be the case 99% of the time.

There are times, after 1mage is installed and working at your site, when you will want to add a new Image Type. There are three steps to the process.
1. Make sure you have a Doc Type set up in 1mage.
2. In the Imaging Control Menu, Select Image > File > Image Type Code Maintenance.
Use the image below to setup the new Image Type Code. The line on "Process To Run" looks a little confusing. It is: EXEC “EE.HIRE.ACT.MNT” ; EXEC “SYS,IMG”