Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.

For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.

This is the technical short name used to identify a user within an installation. This user ID might be different to the user ID used to login to the application server, depending on the login mechanism used and the environment.

This is the long name of a user. This name is used throughout the application where a detailed name of a user is required to make a selection.

Setting this field to a non-empty value disables the login. If default TradeDesign rights are used to handlethe master file, maintenance routines would automatically delete the TradeDesign rights entry for this user, making it impossible for the user to login.

Timestamp of the last login to the system.

Unique ID of the session used for the last login.

This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.

The Priority flag can be used to identify the initial record in a multi-entity environment, where the User table has not been declared global. If multiple entries are available for a single user ID, the entry with a non-empty value in the Priority field is used for the initial login.

This field defines the initial entity of a user after login.

User group the user is associated to.

The date the personal diary entries were last displayed. This date is used to remind users to take a look into the diary.

This field contains the currency for the amount to be released.

This field contains the maximum amount the user is allowed to release transactions (see also the Release field)

This field contains the maxium amount users are allowed to release for their own transactions. (See also field “Release”)

This field contains the release rights. “Officer” = allowed to release, “Clerk” = not authorized to release

This field controls whether this user is allowed to print request created for local printing (remote client printing).

The field application profile defines, which type of queue entries are assigned to a user. If no application profile is defined, any types of queue entries are assigned to a user.

In order to exclude certain queue types, it is possible to define an application profile with the ending *.tda in the ini-folder. In section [Balance CLA] for each value of the embedded codetable QUECLA (e.g. INC or RIM or REL) the assignment of entries can be excluded.

Example:

clerk.tda, [Balance CLA] REL=X excludes that Release queue entries (type REL) are assigned to users that have no authorization rights.

In the MyModelbank, these application profiles are available: Clerk.tda: Any type of queue entries, except release Officer.tda: Any type of queue entries Releaser.tda: Only queue entries of type = Release (REL) Admin/Manager.tda: No queue entries are assigned

This field contains the user's telephone number which can then be used during correspondence.

This field holds the fax number of the user used for correspondence.

This field contains the Email address of the user used for correspondence.

This field describes the user's availability for queue processing. This can be the user's daytime availability, for example.

This value and its relation to the total for all users or all users of a user group is used to estimate static and dynamic capacities for automatic load balancing.

This field contains the name of the organisational unit (department) of the user and is printed in the header of the outgoing correspondence.

This field controls the color in which the entries assigned to the user are displayed in the Dashboard charts.

This field contains the time the work has to beginn on Sunday. The format is hh.mm.

This field contains the time the work has to beginn on Monday. The format is hh.mm.

This field contains the time the work has to beginn on Tuesday. The format is hh.mm.

This field contains the time the work has to beginn on Wednesday. The format is hh.mm.

This field contains the time the work has to beginn on Thursday. The format is hh.mm.

This field contains the time the work has to beginn on Friday. The format is hh.mm.

This field contains the time the work has to beginn on Saturday. The format is hh.mm.

This field contains the time the work should end on Sunday. The format is hh.mm.

This field contains the time the work should end on Monday. The format is hh.mm.

This field contains the time the work should end on Tuesday. The format is hh.mm.

This field contains the time the work should end on Wednesday. The format is hh.mm.

This field contains the time the work should end on Thursday. The format is hh.mm.

This field contains the time the work should end on Friday. The format is hh.mm.

This field contains the time the work should end on Saturday. The format is hh.mm.

This field contains the time that should be worked on Sunday. The format is hh.mm.

This field contains the time that should be worked on Monday. The format is hh.mm.

This field contains the time that should be worked on Tuesday. The format is hh.mm.

This field contains the time that should be worked on Wednesday. The format is hh.mm.

This field contains the time that should be worked on Thursday. The format is hh.mm.

This field contains the time that should be worked on Friday. The format is hh.mm.

This field contains the time that should be worked on Saturday. The format is hh.mm.

This field specifies the part of the working time which should be planned with SLA.

This field holds the external key of the owning entity to identify the logical owner of this entry.

This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity are visible to the user.

This field holds the organizational unit to which the user is associated.

This field contains the entity address as defined in 'Displaying an Entity Address'.

Field holding the concatenated and normalized sum of all search fields used by quick search. This is one of the fields set in a SdbSetNRMFields method defined in the table definition module.

This field contains the Group Email address the user is associated with

User Profile

If checked the user has system administration rights that include user administration right.

Indicates, if a user is allowed to switch to the designer mode of this application. This enables the user to define helptexts, rules and XML templates etc.

For developer only.

In case TradeDesign is configured to run in restricted mode this field defines the minimum security level on which this user can change sources.

This field contains the user status and indicates whether the user status is normal, expired, blocked, reset or a new password was defined.

If this flag is set the relevant user is allowed to edit XML templates via document editor.

Only if in addition also the designer flag is set, document rules can be edited.

Indicates if the current user is a user of a TFaaS solution of this application. On TFaaS systems all application users have to be defined as TFaaS user, except those of the vendor.