Records that use Augmented Attributes
Special attention should be given to these records. In our app we have one augmented attribute for the SUPPLIER_EV record.
The Action in Celonis field should track the actions performed in Celonis, through the use of our skills.
Action: Configure this attribute in the skills and make it visible in the table in the Action View.
In the standard version of the KM, we have a record SUPPLIERS_EV:
- id: SUPPLIERS_EV displayName: SUPPLIERS_EV identifier: id: SUPPLIERS_EV displayName: SUPPLIERS_EV pql: '"LFA1"."LIFNR"'
In this case, the identifier of the record is the LFA1.LIFNR field. However this might not be true for all customer implementations. For example, if your customer uses different LFA1.SYSTEM fields for the same LFA1.LIFNR (meaning the SYSTEM field is part of the key that uniquely identifies a supplier), then you need to add the SYSTEM as part of the key that identifies the record in the KM:
- id: SUPPLIERS_EV displayName: SUPPLIERS_EV identifier: id: SUPPLIERS_EV displayName: SUPPLIERS_EV pql: '"LFA1"."LIFNR" || "LFA1"."SYSTEM"'
Action: Make sure that the PQL field of the SUPPLIERS_EV record is unique.
If you had to change the PQL, any Skills that write to this record should also use the updated record ID in the Record Identifier field inside the Skill: