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 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 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.
;[Change Reason|CHANGE_CODE]:The reason a PA of this type will be created is provided in this field.
At line 25 changed one line
;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|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.
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.
;[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.
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.
;[PA Type Columns|]:This field holds the [{$applicationname}] internal name of the column (field). This field is supplied and is not updateable.
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.
;[Prompt|]:This field holds the [{$applicationname}] display 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.
;[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_NAME]: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.
At line 62 removed 5 lines
----
![Notes|Edit:Internal.ISPY]
[{InsertPage page='Internal.ISPY' default='Click to create a new notes page'}]
This page (revision-16) was last changed on 26-Nov-2021 10:22 by JEscottTop