6.x tip for the day : URL and HTML Support

In 6.x the text fields now support both URLs and HTML code. The following describes how to set them up.

 

Activating URL Support

You can enable URLs (hyperlinks) to be rendered properly in text box controls, so that users may click on live hyperlinks to access a particular resource.

The following types of URL schemes are supported:

• HTTP ( http://example.com/ or https://example.com )

• FTP ( ftp://example.com )

• mailto: ( mailto:admin@example.com )

• Local Files ( file:///C:/notes.txt )

• Windows network path, or UNC ( \\ QA-Server1\Backups )

 

Note: It is important to note that URL Support is activated at the control level

(within the Description text box, for example), and not at the field level. A field

must be associated with a control to enable URL support for that field.

In the following example, URL support is activated for the

Incident.Symptom field (in this case, “Description”) on the Incident form.

 

To activate URL Support:

1. Launch the Administrator. Navigate to a Business Object for which you will activate URL support. For example “Incident”.

2. Right-click on the text box for which you will add URL support (in this case, “Description”). In the context menu, choose Properties. The Control Properties screen appears.

3. Select the Behavior tab and activate the URL Support check box. Click the Close button to apply this change.

4. If there are other perspectives, for which URL support should be activated, repeat steps 2 and 3 for the text box "Description" in all other perspectives.

5. Commit the changes in the Administrator.

 

Activating HTML Support

To enable display and editing of HTML stored in a business object, use the property settings for the text field containing the HTML. This option is available in the Properties panel for the control.

 

1. Launch the Administrator and open the definition set containing the desired business object.

2. Navigate to a business object for which you will activate an HTML control, for example: “Email.”

3. Right-click on the text box for which you will add HTML support.

4. In the context menu, choose Properties. The Control Properties dialog appears

5. Select the Behavior tab and click the Html Support check box.

6. Click Close to apply this change.

Merry Xmas!

Merry Xmas to all who read this blog! Hope you have a great 2009!

P.S. I'm aiming to update this a little more regularly in 2009!

Yes mick, it's my blog

Heat Self Service Now Compatible with IIS 6

Previously all versions of HSS 8.x (including HSS 8.4) would only run on Windows 2003 Server in IIS 5.0 isolation mode.

This issue has been certified as resolved by the release of HAT Self Service 8.4.4 which has been certified gold. The download is available in the Drivers and Downloads section on our Support Site at http://Support.Frontrange.com. This version does not contain a schema change, although support strongly recommends that HEAT 8.4.4 Call Logging be updated on all client machines.

Below are the specific bug numbers with reference to this

• RM 15150 – HEAT Self Service now operates with ISS 6.0 without having to set to IIS 5.0 isolation mode.
• RM 32563 – First Level Support and HEAT Self Service Integration now works when using Windows 2003 Server.
• RM 40899 – Typical Installation now creates Virtual Directories when installing on Windows 2003 Server.
• RM 51309 – HEAT Self Service has removed the limitation to the number of Call Types supported.

ITSM 6.1 Release

ITSM 6.1 is available for new customers at this time. The version for existing customers 6.1.1 will be available around the June-August 2008 time frame.

An effort to update

Hi All, It's been a while since I've been updating this site but with ITSM 6.1 and GMEE both just around the corner there is likely to be a whole lot more content.

Also Frontrange have started their own community page at http://frsconnect.frontrange.com which will be worth checking out for information from other people with Frontrange product experience

A couple of ITSM Tricks/Bugs

Tip Number 1: Frontrange ITSM License Timeouts in 5.0.7.4

The following piece of code is in the Web.Config file in the ServiceManagement folder:
<fusionserverconfiguration instanceid="A210F41B9C0B4492AC54EE90566D51B6" connectionname="">
<usersessionmanagement sessionexpiration="20"/>
<licenseframeworksettings/>
</fusionserverconfiguration>

The line <licenseframeworksettings> seems to be redundant for the license timeouts. Removing that line of code (after making a backup) and reset the IIS.

After this the license server should release license sessions after the timeout specified in the (in minutes)

Tip Number 2: Field Validation Errors in Frontrange ITSM 5.0.7.4

When you select Validation on a field there is another field created in the background called {Fieldname}_Valid. If the field name is longer than 20 characters the field is created with the first 20 characters of the field name then “_Valid”. The issue occurs if you have 2 fields where the first 20 characters of the name are the same and both fields have validation (of any type). When you Commit you receive and error saying that the fields share the same validation but have different validation rules.

The solution is to remove validation from one field. Change the name of this field apply this change then re-add the validation.