Support Article

Obj-Open & lookup ignores mili-seconds value in object key



The user has a use case where they need to copy the attachments from one case to another. All the attachments are committed with pxAttachKey varying only in a few miliseconds. If the user uses Obj-Open in an activity as source on a Data Page, wrong attachment is opened which is seems to be because Pega is not considering milliseconds in Obj-Open.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a case and add two attachments such that the pxAttachKey varies only in terms of milliseconds
  2. Create an activity with Obj-Open to open the attachment.
  3. Add this activity as a source of a data page with pxRefObj and pxAttachKey as the parameters to the activity and run the data page to test.

Root Cause

Support for Timestamp column for oracle is introduced in Pega 7.1.8 version but all existing Out Of The Box datetime properties are mapped to DATE columns in their corresponding tables. This is the reason why pxAttachKey column is mapped to Date column in table pc_data_workattach which inturn causes the issue.


Run the alter scripts to change the column type of pxAttachKey to TimeStamp.
alter table <schema name>.pc_data_workattach MODIFY PXATTACHKEY TIMESTAMP

For example:
alter table pegadata.pc_data_workattach MODIFY PXATTACHKEY TIMESTAMP;

Published February 21, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.