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

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
14 26-Nov-2021 10:22 3 KB jmyers to previous
13 26-Nov-2021 10:22 4 KB jmyers to previous | to last
12 26-Nov-2021 10:22 4 KB JEscott to previous | to last
11 26-Nov-2021 10:22 4 KB RForbes to previous | to last
10 26-Nov-2021 10:22 4 KB Administrator to previous | to last
9 26-Nov-2021 10:22 4 KB Administrator to previous | to last
8 26-Nov-2021 10:22 4 KB Administrator to previous | to last
7 26-Nov-2021 10:22 4 KB Administrator to previous | to last
6 26-Nov-2021 10:22 4 KB Administrator to previous | to last
5 26-Nov-2021 10:22 4 KB Administrator to previous | to last
4 26-Nov-2021 10:22 4 KB RForbes to previous | to last
3 26-Nov-2021 10:22 4 KB Administrator to previous | to last
2 26-Nov-2021 10:22 4 KB Administrator to previous | to last
1 26-Nov-2021 10:22 4 KB Administrator to last

Page References

Incoming links Outgoing links
ILGR
ILGR

Version management

Difference between version and

At line 1 changed one line
!!!GRIEVANCE RULES
!!!FUNCTION TITLE
[{Image src='ILGR.JPG' width='360' align='right' link='attach/ILGR/ILGR.JPG'}]
At line 12 changed 9 lines
;[Grievance Rule|GRIEVANCE_RULE_CODE]:This field is a user-defined code that uniquely identifies the grievance rule being defined.
;[Description]:This field allows you to provide a short description of the grievance rule.
;[Grievance Rule Text|GRIEVANCE_RULE_TEXT]: This text box provides a space for you to add further information about the grievance rule.
;[Grievance Step|GRIEVANCE_STEP_CODE]: This field is a user-defined code that uniquely identifies the grievance step being defined.
;[Seq #|GRIEVANCE_STEP_SEQUENCE]: This field identifies the sequential order of the grievance steps within the grievance rule. It is advised that the sequence numbers be listed in tens (10,20,30,40,....). This will accommodate later step entries, which may need to be entered in between existing steps. For example, an initial submission from the employee should come before a panel review by the union representative.
;[Participant Type|PARTICIPANT_TYPE]:this field identifies the type of participation for this individual.
;[Status|GRIEVANCE_STATUS]: This field indicates the status of the grievance at this particular step.
;[Stage|GRIEVANCE_STAGE]:This field is displays the stage of the grievance at this particular step.
;[Description]:This field allows you to provided a short description of the step.
;[Grievance Rule]:This field is a user-defined code that uniquely identifies the grievance rule being defined. Grievance_Rule is a mandatory 16-character alphanumeric field you must fill manually.
;[Description]:This field allows you to provide a short description of the grievance rule. Description is an optional 50-character alphanumeric field you may fill manually.
;[Grievance Rule Text]: This text box provides a space for you to add further information about the grievance rule. Grievance_Rule_Text is an optional 4000-character alphanumeric field you may fill manually.
;[Grievance Step]: This field is a user-defined code that uniquely identifies the grievance step being defined. Grievance_Step_Code is a mandatory 16-character alphanumeric field you may fill manually.
;[Seq #]: This field identifies the sequential order of the grievance steps within the grievance rule. It is advised that the sequence numbers be listed in tens (10,20,30,40,etc). This will accommodate later step entries, which may need to be entered in between existing steps. For example, an initial submission from the employee should come before a panel review by the union representative. Grievance_Step_Code is a mandatory 5-character numeric field you may fill manually.
;[Participant Type]:This field identifies the type of participation for this individual. Participant_Type is a mandatory fixed lexicon you must fill with the fixed lexicon [X_PARTICIPANT_TYPE] provided.
;[Status]: This field indicates the status of the grievance at this particular step.
Complaint_Status is a mandatory field you may select from the fixed lexicon
[X_COMPLAINT_STATUS].
;[Stage]:This field is displays the stage of the grievance at this particular step.
Complaint_Stage is an optional field you may fill with the user-defined lexicon
[X_COMPLAINT_STAGE].
;[Description]:This field allows you to provided a short description of the step.
Description is an optional 50-character alphanumeric field you may fill manually.
At line 24 changed 3 lines
;[Time Window Value|TIME_WINDOW_VALUE]:This field defines the value of the time interval.
;[Time Window Basis|TIME_WINDOW_BASIS]:This field defines the basis of the time interval.
;[Time Window Method|TIME_WINDOW_METHOD]: This field further defines the time basis. For example, the ‘Basis’ field may identify days, however, this field will identify if the time interval is in work days or calendar days.
;[Time Window Value]:This field defines the value of the time interval. Time_Window_Value is an optional 9-character numeric field you may manually enter.
;[Time Window Basis]:This field defines the basis of the time interval. Time_Window_Basis is an optional field you may fill using the fixed lexicon [X_TIME_WINDOW_BASIS].
;[Time Window Method]: This field further defines the time basis. For example, the ‘Basis’ field may identify days, however, this field will identify if the time interval is in work days or calendar days. Time_Window_Method is an optional field you may fill using the fixed lexicon [X_TIME_WINDOW_METHOD].
At line 29 changed one line
;[Text|GRIEVANCE_STEP_TEXT]:This field allows you to provide more detailed information about the grievance step.
;[Text]:This field allows you to provide more detailed information about the grievance step. Step_Step_Text is an optional 4000-character alphanumeric field you may fill manually.
At line 33 changed 10 lines
This screen is for viewing only; descriptions cannot be added or edited directly on this screen. Once the rule has been defined and ILGR saved, you may associate the rule to a unit through [IDUN]. This will allow you to define agreement end and start dates. Once [IDUN] is saved, the rule will then automatically appear in this area of the ILGR form.
;[Description|DESCRIPTION]:This field identifies the grievance unit rule being described.
;[Unit|UNIT_CODE]:This field identifies the unit associated to this rule.
;[Agreement_Start_Date|AGREEMENT_START_DATE]:This field displays the start date of the union agreement associated with this rule.
;[Agreement_End_Date|AGREEMENT_END_DATE]:This field displays the end date of the union agreement associated with this rule.
----
![Notes|Edit:Internal.ILGR]
[{InsertPage page='Internal.ILGR' default='Click to create a new notes page'}]
This screen is for viewing only; descriptions cannot be added or edited directly on this screen. Once the rule has been defined and the ILGR screen saved, you may associate
the rule to a unit through the IDUN screen. This will allow you to define agreement end and start dates. Once the IDUN screen is saved, the rule will then automatically appear in this area of the ILGR form.
;[Description]:This field identifies the grievance unit rule being described.
;[Unit]:This field identifies the unit associated to this rule.
;[Agreement_Start_Date]:This field displays the start date of the union agreement associated with this rule.
;[Agreement_End_Date]:This field displays the end date of the union agreement associated with this rule.
This page (revision-14) was last changed on 26-Nov-2021 10:22 by jmyersTop