Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Paul Aquino (Paul7342)
Paccar
Pega Software Engineer
Paccar
US
Paul7342 Member since 2018 15 posts
Paccar
Posted: Aug 20, 2018
Last activity: Aug 21, 2018
Posted: 20 Aug 2018 23:39 EDT
Last activity: 21 Aug 2018 2:08 EDT
Closed

change pyID or pzInsKey of existing case record

I have three sibling case types that are related to each other and have the same parent case type with the same pxCoverInsKey.

For Example, I have three different sibling case types/records:

pzInsKey: MyApplication-Work-PR PD-21 pyID: PD-21

pzInsKey: MyApplication-Work-PR RS-21 pyID: RS-21

pzInsKey: MyApplication-Work-PR WR-22 pyID: WR-22

The last case record was auto generated by an agent, and WR-22 was automagically generated incorrectly as it is suppose to match the sibling cases with a (dash) -21.

I have a business requirement to correct the case id and identifier of 22 to match the sibling records. is this possible?

To see attachments, please log in.
Low-Code App Development
Java and Activities

Posted: 6 years ago
Posted: 21 Aug 2018 1:58 EDT
Rajendraprasadu Potti (Prajendra)
PEGA
Senior Principal Engineer, Technical Support - 1:1 Customer Engagement
Pegasystems Inc.
IN

May be you can create the case id with the RS-22 and copy the WR-22 case content to the RS-22

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice