Question
UMKC
US
Last activity: 29 May 2024 1:23 EDT
Difference between pxinsname and pyID column
I just observed that work object ID is stored in both pxinsname and pyID column in the worktable.
Is there a reason storing the case ID in two different columns ?
Updated: 23 May 2024 17:38 EDT
Infosys Limited
IN
pxInsName:
Structure: [Class Name] [Key Values]
Example: Work-W-12345
Purpose: Internal system identifier.
Details: Ensures unique identification across the system, used for system operations.
pyID:
Purpose: User-friendly case ID.
Details: Simplifies user interaction, easier to reference in reports and interfaces.
Reasons for Storing Case ID in Both Columns:
Distinction: Separates system operations (pxInsName) from user interactions (pyID).
Redundancy: Provides backup for data integrity.
Flexibility: Offers developers multiple identifiers based on need.
UMKC
US
In my work table the structure of pxInsName is not [Class Name] [Key Values] or Work-W-12345.
The structure of pxInsName in my worktable is exactly the same as pyID.
For example in worktable if the data in the column of pyID is W-128, then in then the data in pxInsName is also W-128
Pegasystems Inc.
IN
@KevinR17115962 - Generally pyID is used as a primary key for the table. pxInsName property rule is defined in @baseclass and can be accessible in any class to get the data.
Infosys Limited
IN
Pyid is specific to the workobjects that gets set automatically when a case is created in pega.
Pxinsname is avaible across the system (rule instances, work object instances, data etc.,). Except the work object instances, if you open any ruleform, you could see the pxinsname not the pyid.
For rule instances, the format for pxinsname is (<AppliesToClass> <id>). For work objects the format is <id>.
Eclatprime Digital Private Limited
IN
@KevinR17115962 The visible key of an instance is the text value of a reserved property @baseclass.pxInsName. This property is defined in the ultimate base class and so is available in every class. The value of this property is sometimes called the instance name or informally "insname".
The system forms the visible key for an object by concatenating values of the properties identified on the Keys tab of the Class form. On most rule and data forms, you supply these values as key parts as you complete the New instance form and the Save As form. Two rules with identical visible keys that are both available to you are known as siblings. PYID key is primary key for the particular table.