Recent blog posts
How do I set up a new Image Type in 1mage
There are times, after 1mage is installed and working at your site, when you will want to add a new Image Type. Here are steps to the process.
1. Log in to 1mage via PuTTY, add a Document Type: Maintenance > Image Type Codes (look at a Type that has the same data elements you will want to use -- I'd suggest the W4 - remember to '(F)orward to get all the key pieces. Use 'screen print' to get the exact setup 'captured')
HRPyramid 11.1 - CRM Passive Tracking Updates
HRPyramid 11.1 Linkage Update for Adapt/CRM for HRPyramid.
As HRPyramid 11.1 (and every release!) loads new menu items or rearranges menus, we have built a method to assure your Passive Tracking works everywhere with those new/changed menus without the need to manually maintain it.
Please log in to find the link for file for PRJ1-305.zip. UnZip this file into your local C:\TEMP then it's a routine Patch Load from there: PCLOAD the project C:\TEMP\PRJ1-305 to your REVISIONS file, and then FLOAD.REVISIONS.
Fix for Locking Issue of Contacts on Completion of some “Interaction” (Phone Call) records.
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.
Error 134 Message in 1mage
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.
Error 130 Message in 1mage
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.
