This page (revision-21) was last changed on 26-Nov-2021 10:22 by JEscott

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
21 26-Nov-2021 10:22 11 KB JEscott to previous

Page References

Incoming links Outgoing links
ILGV
ILGV

Version management

Difference between version and

At line 27 changed one line
;[Grievance]: This field is a user-defined code that uniquely identifies the grievance being defined. While you may define the grievance code, there is also the option of setting this field to automatically assign a sequential number to each new complaint entered. You may set up this option through the [IMCS] screen. Full details on this function are available through the User Interface manual. Grievance_Code is a mandatory 16-character alphanumeric field.
;[Grievance|GRIEVANCE_CODE]: This field is a user-defined code that uniquely identifies the grievance being defined. While you may define the grievance code, there is also the option of setting this field to automatically assign a sequential number to each new grievance entered. You may set up this option through the [IMCS] screen. Full details on this function are available through the User Interface manual. Grievance_Code is a mandatory 16-character alphanumeric field.
At line 31 changed 2 lines
;[Severity]: This field defines the severity of the grievance. Grievance_Serverity is an optional field you may fill with the fixed lexicon [X_GRIEVANCE_SERVERITY].
;[Issue Date]: This field will define the issue date of the grievance. Grievance_Issue_Date is a mandatory field you may fill manually or by using the calendar icon (F9).
;[Severity|GRIEVANCE_SEVERITY]: This field defines the severity of the grievance. Grievance_Serverity is an optional field you may fill with the fixed lexicon [X_GRIEVANCE_SERVERITY].
;[Issue Date|GRIEVANCE_ISSUED_DATE]: This field will define the issue date of the grievance. Grievance_Issue_Date is a mandatory field you may fill manually or by using the calendar icon (F9).
At line 34 changed 2 lines
;[Approved]: If this toggle has been checked, the grievance has been approved.
Approved is an optional toggle you may select.
;[Approved]: If this toggle has been checked, the grievance has been approved. Approved is an optional toggle you may select.
At line 55 changed 2 lines
;[Decision]: This field displays the decision made in for this grievance. Grievance_Decision is an optional field you may fill using the lexicon [X_COMPLAINT_DECISION].
;[Date]: This field will display the date of the settlement. Grievance_Closed_Date is an optional field you may fill manually or with the calendar icon (F9) provided.
;[Decision|GRIEVANCE_DECISION]: This field displays the decision made in for this grievance. Grievance_Decision is an optional field you may fill using the lexicon [X_GRIEVANCE_DECISION].
;[Date|GRIEVANCE_CLOSED_DATE]: This field will display the date of the settlement. Grievance_Closed_Date is an optional field you may fill manually or with the calendar icon (F9) provided.
At line 85 changed one line
;[Date!REPLY_TIMESTAMP]: This field identifies the date a reply was actually received. Reply_Timestamp is an optional field you may fill manually or with the calendar icon available.
;[Date|REPLY_TIMESTAMP]: This field identifies the date a reply was actually received. Reply_Timestamp is an optional field you may fill manually or with the calendar icon available.
This page (revision-21) was last changed on 26-Nov-2021 10:22 by JEscottTop