Skip to main content

wait shape configuration not working because of Report Definition pzGetChildCases

Hi,

We have a flow where Parent Case should get Resolved  when all child cases were resolved ,  until all child cases were resolved  Parent Case will be in wait shape , with wait type as Case Dependency 

In our scenario the number child cases were 69 and parent Case got resolved immediately after 50 th child case resolved , We have analyzed and found that the Report Definition pzGetChildCases is pulling only 50 cases , so all the 50 child cases were resolved and parent cases is got resolved .

Create a new case in the same harness when old case gets assigned to other workbasket

We created an initialization screen where we can enter all case data needed. After duplicate case check, the temporary case is being persisted and moved to another workbasket where it will be picked up by an agent to do some background calculations/checks. Afterwards, it will be reassigned to the end-users workbasket.

In order to speed up the work, we would like a new case to be created using the existing harness so the user can continue with encoding the next case.

Any ideas on how to accomplish this? Thnx!

 

Implementation of Specialized Data Pages per entity

Submitted by on

Hi, 

  I have a design clarification question : I work in an application which cuts across more than one country/entity (let us call the countries X and Y). Now, there is a strict regulatory requirement to have a segregation of data between the entities : users of Country X would NOT be able to view the data of country Y.

 

Production ruleset rule changes/checkin are not reflecting on all nodes in prodction

We delegated decision tables to production users and we noticed couple of times by now that when they check in changes did not reflect on all nodes, only on few nodes changes are synced.

 

We have 24 nodes in production

 

  • Pega pulse is running on all nodes, then why this issue is happening and how to minimize this?

 

Client is asking why this is happening and is concerning business.

 

 

***Edited by Moderator Marissa to update Content Type from Discussion to Question***

Call pega function in control rule to format IBAN number for output.

The end result I want to obtain is the next:

An IBAN number is stored on the clipboard in internal format (uppercase, no spaces), where as on the screen, it is displayed as a formatted IBAN (uppercase in groups of four).

 

I created a function that takes "I" or "O" and the number to format the given IBAN to input/output format.

I use this function in an edit input rule to format the entered number for internal storage.

Delete PR_LOG and PR_HISTORY tables using DDL scripts

We had an issue on one flow of our application, that generated a lot of records on pr_history and pr_log tables, due to a loop in a wait shape (more than 15.000 records per case).

We need to purge these records, since they are not useful, and they are occupying more than 60% of Pega's tablespace.

Is it safe to delete them manually, using a DDL script?

Thanks in advance,

Fabio A.

Subscribe to 7.3

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