The ValueRule object belonging to.....

This frustrated me for about 20 minutes today before I discovered the cause...

Owner : The ValueRule object belonging to the TextFieldDef
'Change.Owner' does not have a name.

Every time I went to commit I got this error. I had made some changes
to the field but no end of changing Validation settings, Autofill
Rules, Calculations would solve the issue.

Here is an explanation of how to solve this issue if you come across.
The change I had made to the field was as follows:-
1. The field had a default value from a function "Current Login ID"
2. I selected Simple Value and left the value blank.

The issue is the field still references a function in the background.
(hence the "ValueRule object" Not having a value)

When removing a function from a Default there is an option in the
function drop down list of "None".

This will remove this error.

Urgent Technical Notification for all iHEAT and iGoldMine customers

Urgent Technical Notification for all iHEAT and iGoldMine customers

Valued HEAT and GoldMine Partners,

Please be advised that Windows Update SP2 for Windows 2003, released on 15 March 2007, is incompatible with iHEAT and/or iGoldMine for Windows on Windows 2003. This incompatibility only affects the iHEAT and/or iGoldMine Server and does not impact the Client machines.

FrontRange Solutions will release a compatibility update as soon as possible and we will send a second notification when the update is available.

How to add Colour Coding to the Grid view in Dashbords (ITSM 506 and higher)

Below are the steps outlining how to change ITSM 506 to add colour coding to the Dashboard. These settings based on a Expression and will allow the records in Grids to be displayed by color in the Dashboard. Making the change will only affect newly added records moving forward (ie it won't be reflected in all existing records in the system).

Changes Needed for Color Coding
1. Open AdminLoader.exe.
2. Open a new Definition Set.
3. Select the Incident object.
4. Right-click on Fields and select New Field.
NOTE: Field should be a text field with the Name of Colour.
5. Step though the field wizard and click Finish.
6. Right-click on the newly created Colour field and select Edit Field. Page 4
7. Select the Annotations tab.
8. Type in GRIDROWCOLOR.
9. Click Apply.
10. Click on the Advanced tab.
11. Click the check box for The value in the field is calculated.
12. Select drop down for Calculation.
13. Select New Expression.
14. Build the Conditional List Properties based on Urgency values.
NOTE: Expressions should be as follows:
Urgency equals High for Left Value, Right Value defined by colour. Example: RED.
Urgency equals Medium for Left Value. Right Value defined by colour. Example: Blue.
Urgency equals Low for Left Value. Right Value defined by colour. Example: Green.
Default Value is needed so set to Low.
15. Click Ok.
16. Click Apply.
17. Click Close.
18. Select the Incident Grid from Forms.
NOTE: Depending on which grid is used for the Dashboard Part displayed on the Dashboard; adding the color field will need to be added to each grid for the Incident object if more then one grid is used for each individual part.
Example: Incident Multiview is tied to the following grid defined in the Dashboard Parts section of ITSM.
19. Drag the Colour field to the Grid.
20. Commit the definition set.

Bug Fixes and Enhancements included in HEAT 8.4.1

RM 6281 - (ITS 34632) Removing an action from a follow-up within a BPAM rule does not remove the follow-up action.

RM 6282 - (ITS 35480) BPAM will not send an attachment or write a file using a mapped drive when running on Windows XP

RM 6594 - (ITS 38092) An Auto Task that changes the CustType and CustID will error when executed through BPAM.

RM 8462 - (ITS 38314) An Auto Task that is set to close the record does not stamp the ClosedDate, ClosedBy, or ClosedTime fields.

RM 15776 - When using screen reading software, the screen reading software must be able to announce the Menu Item when executed from a keyboard short-cut.

RM 16230 - @Sum AutoTask function will not work on its own.

RM 21211 - Adding a 16x16 bmp when using MSSQL will cause a “String data right truncation” error.

RM 28187 - Auto Tasks are populating date fields with a year of 1970 when executed from BPAM.

RM 28690 - Duration calculation in reports calculates values differently when the report is run via HEAT versus when run through Crystal.

RM 31812 - User receives ODBC error when trying to create HEAT Asset Tracker tables through the HEAT Administrator.

RM 42295 - Agent Dashboard used with IPCC is reset after upgrade to HEAT 8.4.

RM 42378 - @Team function within an Auto Task will crash Call Logging, if using long team names.

RM 42893 - Alert Monitor Grid Settings do not save the size settings after saving the Alert Definition.

RM 43054 - Alert Monitor will not save the Sort Option upon exit.

RM 43654 - Call Logging crashes after deleting an item from Table Maintenance when using Access.

RM 44075 - BPAM Service produces a 1067 Error when starting service against Microsoft Access Database when the database is located on a shared location or mapped drive.

RM 44260 - ATG Service does not run on Windows Server 2004 when it queries an Access database located on a network drive.

RM 44527 - User receives 37000 SQL error when the user selects a Call Type with an apostrophe.

RM 44781 - Utilizing multiple print queues under a HEAT Print Information Auto Task Action will not print to the correct print tray that was configured in the Auto Task.

RM 44920 - Jump to Control action can not place cursor into Subset form.

RM 45391 - Call Record Browse is causing Call Logging to lock up when utilizing with a large set of Call Records.

RM 45683 - BPAM is unable to use SQL Express 2005 as the local database.

RM 45769 - Call Record Browse does not open desired record when executed.

RM 46425 - ATG processes only one e-mail per poll.

RM 46496 - Call Logging causes SQL Locking when viewing Assignments or Journals.

RM 48333 - Call Record Browse will return all values when executed from a custom Call Group that does not contain reference to a CallLog field.