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

 Elluri Shaikh Muneer Hussain (ElluriShaikhM)
Virtusa Consulting & Services Pty Ltd
AU
ElluriShaikhM Member since 2014 2 posts
Posted: Nov 29, 2021
Last activity: Nov 30, 2021
Posted: 29 Nov 2021 18:54 EST
Last activity: 30 Nov 2021 4:40 EST
Closed

How to display the case type prefix based on the different property values selected from a dropdown?

Hi, 

I have a requirement where I need to display the prefix of a case type based on the property values that I select from a dropdown in the New harness which is configured in the pyStartCase flow.

So, if I have 5 values in the dropdown, there should be 5 different case type prefix values available for that work object and should be displayed on the case header based on the selection.

Can anyone suggest how this can be achieved?

 

Thanks in advance,

Muneer

 

 

 

 

***Edited by Moderator: Pooja Gadige to change category from General to Product, add product details tag, add capability tag***
To see attachments, please log in.
Pega Platform
Case Management

  • Muhammad Hamza
Posted: 3 years ago
Posted: 29 Nov 2021 22:59 EST
Gunasekaran Baskaran (Gunasekaran Baskaran)
Lventur
Delivery Head [PEGA]
Lventur
IN

@ElluriShaikhM

In Post action of new harness UI you could invoke data transform which could override the work object id prefix value based on input which user selecting in UI.

After new harness screen submitted by using pyWorkIDPrefix property value only pega will invoke logic to generate case id, so before case id generated you could override pyWorkIDPrefix property value and this will not have any negative impact.

Attached screen shot for reference.

Case ID Prefix

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