Workaround for Oracle Views in ITSM 5.04-5.06

In ITSM (versions from 5.04 and 5.06) the linking of external data to Oracle views is problematic (eg. you are able to see the view but no columns are presented to add, even though they exist). Below is a work around if you need to connect an Oracle view in as an External Data source.

1. Create a new definition set.
2. Create an Object (just a Standard or Validation Business Object depending on your requirements), and define all the fields that WILL appear in your database view (i.e. Mimic the structure of the view you wish to connect in an ITSM table)
3. Make sure the view does not exist in the database – drop it if necessary,
4. Commit your definition set. The system will create a table in the database.
5. Directly in the database (i.e. connect to the database with a tool such as Toad etc. not through the ITSM administrator ), drop the table.
6. Directly in the database (i.e. connect to the database with a tool such as Toad etc. not through the ITSM administrator ), create the view with the same name and in the same table space as the table that was created through ITSM administrator in Step 2 (remembering that capitalization is important in Oracle systems).
7. The system will now use the view as if it were a table, and will operate normally.

Important points:

1. If there are any changes to the format of the object in Administrator, the commit will fail, because it will try to drop the table (which doesn't exist because it is a view)
2. You will need to 2 SQL scripts – one to run before a commit, one to run after.
1. The first will drop the View, and create a table with the same structure as the view.
2. The second will drop the table and recreate the view.
3. Adjust the security for the new object that you've created so that no user can update or add to this table to prevent errors in the tool
   
4. All fields in the table must be replicated in the view, this includes RecId, LastModDateTime, LastModBy, CreatedDateTime and CreatedBy
   

Product Update: GoldMine 6.7 Patch for IE 7.0 Compatibility

Product Update: GoldMine 6.7 Patch for IE 7.0 Compatibility

Patch ready for IE 7.0 compatibility issues!

FrontRange Solutions will release a patch next week via NetUpdate for GoldMine version 6.7 to address known Internet Explorer 7 compatibility issues. All customers who currently have 6.7 installed will have access to the patch when it becomes available. The known compatibility issues included:



· HTML toolbar buttons missing from the GM email composition window

· Email font sizes shrunk

· Warnings displayed for script errors when launching MyGoldMine

Windows Authentication in ITSM SelfService and ServiceManagementWeb

I couldn't find this change anywhere on the net so here it is...

There is a setting in the web.config file to setup Windows Authentication.

Change this Section

<authentication mode="Forms">
<forms name=".FUSIONAUTH" loginUrl="Login.aspx" timeout="2400" />
</authentication>

To

<authentication mode="Windows">
<forms name=".FUSIONAUTH" loginUrl=" Login.aspx" timeout="2400" />
</authentication>

How to identify an ITSM 5.06 System

How to identify an ITSM 506 System

The versioning in the ITSM system is not always the clearest and with the new version of ITSM (506) release the versioning hasn't been

incremented in the tool to reflect this. This is a couple of ways you can and can't find the version of the two systems :-

ITSM 5.04 SP1
Installer Version - 5.0.4003
Help-About Version - 5.0.4003

ITSM 5.06
Installer Version - 5.0.4003
Help-About Version - 5.0.4003.21

So officially (according to support) 5.0.4003.21 is the 5.06 release of ITSM.

Issue with HEAT 8.4 and Windows 2K3

Version: HEAT 8.4

Issue:
Running Heat 8.4 on WIn2k3 with no SP or hotfixes.BPAM will schedule the activity but will not fire off.Stop/Started the services but will time out.

Resolution:
Installing Windows 2003 SP1 fixed this issue. No other hot fixes were installed, which after reading the forum can actually break BRM again.