URGENT TECHNICAL NOTIFICATION FOR ALL iHEAT AND iGOLDMINE CUSTOMERS

Please be advised that Windows Update 931784, released 10 April 2007 is incompatible with all supported version of GO-Global for Windows 3.x on Windows Server 2003 (SP1 and SP2), Windows XP-SP2, and Windows 2000-SP4

The incompatibility only affects the iHEAT and/or iGoldMine Server and does not impact the Client machines.

FrontRange Solutions will release a compatibility upgrade as soon as possible.

General Availability of ITSM 5.0,7

FrontRange Solutions pleased to announce the General Availability of IT Service Management (ITSM) 5.0.7, English.

ITSM Release Version 5.0.7 includes some of the following enhancements and fixes:

· New enhanced FAD File

· New Inventory Module Features and Enhancements

· New Email Change Approval Process

· Approximately 40 Customer Escalation Issues

· Updated Documentation

Setting a Default SLA in the out of the box.

Here is a bit of Code that will allow you to set the default value of a link field. This specific example sets the default value of the SLALink field on Incident based on the priority.


import System
import Fusion
import Fusion.Api

class FusionScriptWrapper implements IScriptWrapper
{
function FusionScriptWrapper()
{
// place constructor logic here
}

function Process(currentBusinessObject : Fusion.Api.BusinessObject, currentField : Fusion.Api.Field) : Object
{
var objReturn : Object;
var defaultSLARecId: String;
var highPrioritySLARecId: String;

// first set the link to null
currentBusinessObject.GetField("DefaultEscalationLink+LinkID").SetValue(new Fusion.FusionValue(""));
currentBusinessObject.GetField("DefaultEscalationLink+LinkCategory").SetValue(new Fusion.FusionValue(""));

// Set the value of the RecID of the Default SLA
defaultSLARecId = "00000000000000000000000000000000";
// Set the value of the RecID of the High Priority SLA
highPrioritySLARecId = "00000000000000000000000000000000";

// then set the link to either the default or high priority sla
if(currentBusinessObject.GetField("Priority").NativeValue == "1")
{
currentBusinessObject.GetField("DefaultEscalationLink+LinkID").SetValue(new Fusion.FusionValue(highPrioritySLARecId));
currentBusinessObject.GetField("DefaultEscalationLink+LinkCategory").SetValue(new Fusion.FusionValue("SLA"));
}
else
{
currentBusinessObject.GetField("DefaultEscalationLink+LinkID").SetValue(new Fusion.FusionValue(defaultSLARecId));
currentBusinessObject.GetField("DefaultEscalationLink+LinkCategory").SetValue(new Fusion.FusionValue("SLA"));
}


return objReturn;

}
}


Linking closed incidents to problem records (ITSM 5.0.6.4)

There is a new feature in the Security Group Manager in Patch 4 of ITSM 5.0.6. This new feature allows you to link objects when in the final state provided they are in a ad-hoc relationships.

If this feature was selected on the Problem object it would allow Incidents to be linked once the Problem had reached final state. This would however allow any ad hoc relationship to be linked so you would have to managed which relationships you would allow by conditionally enabling the Tab linked to the relationship.

Transfering Perspectives in FUDs

There is a easily overlooked option that you need to select when trying to transfer a perspective definition via a FUD.

There is a database definition in the list of the category "PerspectiveDef". These definitions are in the association "Associated with :" and under the perspective "Perspective : (Base)".

If you're taking across a new perspective definition you need to include the PerspectiveDef entry for the perspective.