- Diary View.Auto generated
Logical – This field is set to True for all auto-generated transactions during diary processing. It is always False for manually entered transactions.
- Diary View.Date
Date – Transaction date that is required when you manually enter transactions.
- Diary View.Date time modified
DateTime – Time when the transaction was generated or last edited. Automatically populated when the transaction is generated or saved.
- Diary View.Description
Description that goes with the entity code. For example, if the entity code were Employees, then the description would be each employee’s full name.
- Diary View.Diary code
Diary – Diary code that the transaction is associated with. Required when you are entering transactions manually (must be completed before you save).
- Diary View.Diary rule code
DiaryRule – Diary rule code that auto-generated the transaction. Always populated for auto-generated transactions. Not available when you manually enter transactions.
- Diary View.EntityTypeDesc
Describes the type of entity that you are using. For example, the descriptions for OSH/OHS meetings or employees would be used.
- Diary View.Priority
A priority of 1 is highest.
Shows the priority this transaction should be given by the system and the operator. A default priority is set on all auto-generated transactions. You must add a priority when you manually enter transactions.
- Diary View.Status
Optional. Field contents are user-defined. Used only when you manually enter transactions.
- Diary View.Text
Text description of the transaction that is displayed in Diary View Drill Down. Automatically populated during diary processing. Mandatory for manually entered transactions.
- Diary View.User profile code
UserProfile – User who started diary processing or who last edited the transaction. Automatically populated when the transaction is generated or saved.
