Difference between revisions of "Object"

Revision as of 22:53, 20 February 2008

Mainly, an Object in ServiceDesk is an object oriented representation of a single database record.

An Object belongs to a so called Factory, which is somehow a mapping to one (or two) database table(s).

Normaly, each field in a table is mapped to an attribute in its object representation.

Changes to attributes of an object are always done in a three step process: First you have to checkout the object. That means, you tell the system, that you want to change this specific object. If nobody else is actualy changeing this object, you get a writable version of this object. Then you are able to change the values of the attributes of the object. At the end, you have to do a checkin to this object. The checkin will write the changed attributes to the database and makes the changes persistent.

In addtion to the data representation, objects can also implement application behavior in form of tirggers an methods. There are two different kind of triggeres:

1) Attribute trigger: These triggers are fired, when an attribute is written or initiated (while the object is checked out).

2) Object trigger: These triggers are fired, when the whole object is checked in(saved).

Both kink of triggers are executing so called Spell code. Spell code is a proproitary script language, which can interact with each process of ServiceDesk and is able to do addtional changes to other objects or call other object methods

Addtionaly, an object may have addtional runtime attributes, like QREL, BREL, LREL and so called LOCAL attributes.

QREL, BREL and LREL Attributes can hold a list of other objects, while a LOCAL attribute is like a normal value (tablefield) attribute, but is not persistent, which means, it will not be stored in the db.