Errata

RT Essentials

Errata for RT Essentials

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Printed
Page 3
Project Management, 2nd paragraph, line 2

You are particularly interested are particularly interested in the...
should be:
You are particularly interested in the...

 Anonymous   
Printed
Page 5
Multiuser paragraph, 3rd line

"Any number of people in an organization must be able to enter data of people
in an organization to enter data and open tickets at the same time."
should be:
"Any number of people in an organization must be able to enter data and open
tickets at the same time."

 Anonymous   
Printed
Page 6
Penultimate paragraph

pp 6: Penultimate paragraph, last line contains the type "unitl".

Note from the Author or Editor:
Report is correct, this is a typo. unitl should be until.

 Anonymous  Aug 20, 2008 
Printed
Page 10
4th paragraph

The word "effieciently" should appear as "efficiently."

 Andrew Yaksic  Oct 29, 2009 
Printed
Page 11
1st paragraph

"use the new tool to it's best advantage" ? should be "its"

 Andrew Yaksic  Oct 29, 2009 
Printed
Page 23
Site Details: last paragraph

For configuration as virtual host the suggested $WebPath:
Set($WebPath, "/");
should be:
Set($WebPath, "");

 Anonymous   
Printed
Page 34
Last sentence

This sentence appears to be incomplete.

 Anonymous   
Printed
Page 42
Associating Related Tickets: paragraph 1, line 5

reference to Figure 3-8 should be Figure 3-9.

 Anonymous   
Printed
Page 42
Last paragraph

The description of Parent/Child vs DependsOn/DependedOnBy is reversed.
Dependency relationships prevent the user from resolving tickets when
there are outstanding dependencies. Parent/Child have no such requirement.

Note from the Author or Editor:
Replace paragraph with:

The Parent/Child relationships are similar to the Depends On/Depended On By relationships. The practical difference is that RT doesn't enforce ordering constrants -- the parent ticket can be resolved before the children.

 Anonymous   
Printed
Page 57
bottom command line listing

$ rt edit ticket/42

A backslash () is missing at the end of this line.

Anonymous   
Printed
Page 65
2nd paragraph

The word "primarly" should be "primarily".

 Andrew Yaksic  Nov 04, 2009 
Printed
Page 73
3rd paragraph

The word "catastropic" should be "catastrophic".

 Andrew Yaksic  Nov 11, 2009 
Printed
Page 78
towards the bottom

$self->TicketObj->status

should have the first 's' of status capitalised, otherwise it fails.

It should read:
$self->TicketObj->Status

 Anonymous   
Printed
Page 94
Both sample templates

The 'Depended-On-By: TOP' line is in the Content: section which does not work
correctly (at least in 3.4.5). Moving the lines above the Content: section solved the
problem.

Note from the Author or Editor:
In the first code sample, move the
Depended-On-By: TOP
line above the Content: ... line

 Anonymous   
Printed
Page 120
figure 8-2, the RT Logical Model image.

The image references several objects as CustomerField instead of CustomField. My
copy of the book has 6 references of the form:

CustomerField -> id
CustomerField -> id
CustomerFields (in grey box)
CustomerFieldValues (in grey box)
ObjectCustomerFieldValues (in grey box)
ObjectCustomerField (in grey box)

Also, in the lower part of the image, Scrip is misprinted as Script in various
places. I see:

ScriptActions (in grey box)
ScriptConditions (in grey box)
ScriptAction -> id
ScriptCondition->id
Scripts (in grey box)

 Anonymous   
Printed
Page 186
3rd line

$LogToScree should be $LogToScreen

 Anonymous   
Printed
Page 196
last entry in left column

memebership
should be
membership

 Anonymous   
Printed
Page 199
Under T

There is no index entry for TicketSQL, which is an important subject mentioned in
several places in the book.

 Anonymous