Hi all,

I have a table layout that each line has a button to execute an activity and after it executes it refreshes the current section to present the updated information.

When this table is paginated and the user is on another page but the first (eg 7 of 10) when the users clicks this button and the page is refreshed, the list is reloaded with the 1st page active as per PEGA standard.

User is requesting that when this section is refreshed the active page that is shown on the table is the same one that he was at when he clicked the button.

Can we use the pega credentials which are stored in DB for only authentication. After authentication it should not create any requestor in pega and it should route to some other application. What are the best ways to implement this solution?

***Edited by Moderator: Pallavi to update platform capability tags, move from Pega Academy to Product***

Hi,

Does anyone have experience how to put Pega Mashup gadget into another Pega portal on the different Pega instance? I have found an article and it says we should put some specific code into the <div> element:

https://community.pega.com/knowledgebase/articles/pega-web-mashup/troubleshooting-pega-web-mashup-issues#scenario-4

This is very strange code, I couldn't include it into section rule as I got errors from Pega.

Hi all,

last week we mistakenly installed a product rule in our pre-production environment which had an application that was built on an other one that was not present in that environment. Due to this, the following exception appeared in the log "Unable to construct authorization core due to authorization failure" and we were not able to reach Pega Login page.

The only way we found to solve the issue was a complete restore of both the PEGARULES and PEGADATA database schema to a backup we created before installing the product rule.

Is there a mechanism or logger for the async declare pool service package? We want to monitor max/active/idle requestors in that pool. We utilize it for several features - async data pages, strategies, etc - and if it fills up we end up tipping over. Thoughts? We don't want to have to log into sma all of the time. We'd like it at the logger level.

Hello!

I need to generate classes with pattern inheritance from XSD file.

For example I have a base class for generate: TmpClass. I want to generate TmpClass-FirstClass and TmpClass-FirstClass-SecondClass. Can I do this? And if yes, Can you send me example of XSD file?

All the best

Igor!

Hi All,

I am getting below error while configuring local source in data type.

**Optimization cannot be performed for classes in this hierachy because of one or more of the following reasons : they are abstract or in a Pega shipped ruleset or mapped to either pr_other or an external table

I am using FW class for datatype and also getting error while testing class connection. Table is not getting created automatically for connection.

Please suggest resolution if you have any idea for such type of scenario.

Due to business requiment, we want to include 6 new columns to optimize the search on pc_assign_workbasket table. Actually we use a join with pc_work table to filter this columns on the assignment report definition, but the performance is very poor, due to amout of records and custom columns on pc_work table.

Is there any restriction to update the pc_assign_worklist data model?

***Edited by Moderator: Pallavi to change content type from Discussion to Question***

Hi,

In Pega 7.3.0 Production system (High attachment volumes system) we are facing high JVM memory consumption for the times when uploading and downloading of attachments use cases are performed. Exponential increase of memory spikes around attachment transactions. 

Would like to know if any of the application had similar experience and if so what resolution steps were taken to improve the all performance of attachment upload and download.

***Edited by Moderator Marissa to update Platform Capability tags****

Hi, 

About a specific google chrome version Chrome Version 83.0.4103.116 in Pega 7.3.