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

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

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

Page References

Incoming links Outgoing links
ISPY
ISPY

Version management

Difference between version and

At line 1 removed 2 lines
[{TableOfContents }]
At line 11 changed one line
Through PA types, Personality enables you to make a good business association between a specific change reason/action and the particular fields that must/may be affected by that change.
Through PA types, [{$applicationname}] enables you to make a good business association between a specific change reason/action and the particular fields that must/may be affected by that change.
At line 15 added one line
!!‘Maintain Personnel Action Types’ Usage and Examples
At line 19 changed one line
;[PA Type|PA_TYPE_CODE]:This field holds the name of the Personnel Action type that is being created.
;[PA Type|PA_TYPE_CODE]:This field holds the name of the Personnel Action type that is being created. PA_Type_Code is a 16-character alphanumeric mandatory field that is manually created.
At line 21 changed one line
;[Change Reason|CHANGE_CODE]:The reason a PA of this type will be created is provided in this field. This is an optional field. A change reason may be provided on the PA definition in [ISPY] or on the actual PA when initiated.
;[Approval Level|APPROVAL_LEVEL]:Within this field, you may define the approval level required (e.g. not specified, manager, supervisor) in order to process any PA of this type. Approval_Level is a required, user-defined lexicon ([X_APPROVAL_LEVEL]), from which you may make a selection from the list of values.
At line 23 changed one line
;[Description|DESCRIPTION]:This field displays the description of the purpose and use of the PA type.
;[Change Reason|CHANGE_CODE]:The reason a PA of this type will be created is provided in this field. Change_Code is a 16-character alphanumeric mandatory field that you may either manually enter or with a select from the LOV provided. Values for the LOV are maintained in the Define Change Reasons ([IDCR]) form.
At line 25 changed 2 lines
;Update Future Records|UPDATE_FUTURE_RECORDS:If this toggle is ON, then the effective date record(s) created after the date of the PA will also be updated. If the toggle is OFF, only the effective date record that is in effect when the PA is processed will be affected.
;[Cascade Change Reason|CASCADE_CHANGE_REASON]:If this and the Update Future Records toggle are ON, then the change reason for this PA will override all future dated effective record change reasons. If the toggle is OFF and the Update Future Records toggle is ON, future effective dated records will be updated but their change reason will remain the same.
;[Description|DESCRIPTION]:This field displays the description of the purpose and use of the PA type. Description is an optional 50-character alphanumeric field you must manually enter.
At line 28 changed one line
;[Track Changes|TRACK_CHANGES]:If this toggle is ON, any changes to the PA that are made by anyone who is not the originator will be tracked. A copy of the PA will be made and given a negative PA number to distinguish it from the original PA.
;[Assignment Required|ASSIGNMENT_REQUIRED]:If this toggle is ON, then users must indicate which assignment is to be used to retrieve the information for a PA of this type. If the toggle is OFF, the no assignment information is required in order to process the PA. The toggle must be on for any PA’s that require the Assignment or Assignment Details tables. Assignment_Required is an optional toggle field.
At line 30 changed one line
;[Table|TABLE_NAME]:This field identifies all tables that will be affected by the PA, if selected.\\
;[Update Future Records|UPDATE_FUTURE_RECORDS]:If this toggle is ON, then the effective date record(s) created after the date of the PA will also be updated. If the toggle is OFF, only the effective date record that is in effect when the PA is processed will be affected. Update_Future_Records is an optional toggle field.
;[Cascade Change Reason|CASCADE_CHANGE_REASON]:If this and the Update Future Records toggle are ON, then the change reason for this PA will override all future dated effective record change reasons. If the toggle is OFF and the Update Future Records toggle is ON, future effective dated records will be updated but their change reason will remain the same. Cascade_Change_Reason is an optional toggle field.
;[Track Changes|TRACK_CHANGES]:If this toggle is ON, any changes to the PA that are made by anyone who is not the originator will be tracked. A copy of the PA will be made and given a negative PA number to distinguish it from the original PA. Track_Changes is an optional toggle field.
;[PA Type Tables|TABLE_NAMES]:This field identifies all tables that will be affected by the PA, if selected. Table_Name is a 16-character alphanumeric mandatory field that you must complete with a selection from the LOV provided. \\
At line 45 changed one line
;[Table Alias|TABLE_ALIAS]:This field shows the abbreviated alias for the table selected.
;[Table Alias|TABLE_NAMES]:This field shows the abbreviated alias for the table selected. Table_Name will automatically default in once the Table_Name has been selected.
At line 47 changed one line
;Create, Refresh All PA Columns for Table:If a new release has added new fields to a table, then by pressing this button, all the new information for those fields will be pulled into the database.
;[No Create Allowed|NO_CREATE_ALLOWED]:If this toggle is ON, you will not be able to add information for this table on the PA. No_Create_Allowed is an optional toggle field.
At line 49 changed one line
;[Seq. #|COLUMN_SEQUENCE]:This field defines the sequential order of the column or field. This sequence is supplied but you may override the order.
;[No Delete Allowed|NO_DELETE_ALLOWED]:If this toggle is ON, you will not be able to delete information for this table on the PA. No_Delete_Allowed is an optional toggle field.
At line 51 changed one line
;[PA Type Columns|]:This field holds the Personality internal name of the column (field). This field is supplied and is not updateable.
;[Seq. #|COLUMN_SEQUENCE]:This field defines the sequential order of the column or field. This sequence is supplied but you may override the order. Column_Sequence is a 5-digit numeric mandatory field.
At line 53 changed one line
;[Prompt|]:This field holds the Personality display name of the column (field). This field is supplied and is not updateable.
;[PA Type Columns]:This field holds the [{$applicationname}] internal name of the column (field). This field is supplied and is not updateable.
At line 55 changed one line
;[PA Column Access|PA_COLUMN_ACCESS]:You may use this field to define the access that user have to each column.
;[Prompt]:This field holds the [{$applicationname}] display name of the column (field). This field is supplied and is not updateable.
;[PA Column Access|PA_COLUMN_ACCESS]:You may use this field to define the access that user have to each column. PA_Column_Access is a required, fixed lexicon ([X_SECURITY_ACCESS]), which you may fill with a selection from list of values provided.
|Updateable|default
|Mandatory|column cannot be left blank
|No View|column will not be displayed on [ISPA]
|No Update|column will be displayed but the use will not be able to update it
At line 57 changed one line
;[Context|CONTEXT_COLUMN]:If the toggle is ON, any changes to that field in relevant tables made after an [ISPA] screen is created will cause [USPPA] to not update that field. If the toggle is OFF, [USPPA] will update the field regardless of any changes since the [ISPA] screen was created.
;[Context|CONTEXT_COLUMN]:If the toggle is ON, any changes to that field in relevant tables made after an [ISPA] screen is created will cause [USPPA] to not update that field. If the toggle is OFF, [USPPA] will update the field regardless of any changes since the [ISPA] screen was created. Context_Column is an optional toggle field.
At line 59 changed one line
;[User Field|USER_FIELD_NAME]:If the toggle is ON, it indicates that the field is user defined. Any user fields that are added must be given a sequence number of 99000 or higher.
;[User Field|USER_FIELD]:If the toggle is ON, it indicates that the field is user defined. User_Field is an optional toggle field. Any user fields that are added must be given a sequence number of 99000 or higher.
\\
---
!!Buttons
At line 61 changed 6 lines
----
![Notes|Edit:Internal.ISPY]
[{InsertPage page='Internal.ISPY' default='Click to create a new notes page'}]
;[Create, Refresh All PA Columns for Table]:If a new release has added new fields to a table, then by pressing this button, all the new information for those fields will be pulled into the database.
This page (revision-16) was last changed on 26-Nov-2021 10:22 by JEscottTop