Ask the Expert - Pega Express with Suman Bhowmick
Join Suman in this month's Ask the Expert session on Pega Express!
- Follow the Product Support Community's Community Rules of Engagement
- This is not a Live Chat - Suman will reply to your questions over the course of this two-week event
- Questions should be clearly and succinctly expressed
- Questions should be of interest to many others in the audience
- Have fun!
Architech Solutions LLC
US
Hello Suman,
We have a case prefix that is updated in our system from JA-1 to JA-xxxx-yy-0001. Earlier we were able to search with case id say JA-1, and pega finds the case and opens properly.
After tweaking the case prefix per new requirement, new case ID format is JA-xxxx-yy-0001. We are not able to search cases with the new case number. Looks like Pega bug to me, but want to see if anyone else faced the same issue.
Matt
Pegasystems Inc.
IN
Hi Matt,
You might try re-indexing all the work objects. You can try that from Designer Studio -> System -> Settings -> Search. If that doesn’t fix your problem, please consider creating an SR with Pega Support team to investigate.
Suman
Pegasystems Inc.
IN
Hi Venki,
I am not sure if I understood your question correctly.
I want to highlight that operators with the pxCanDelegateRules privilege, can delegate rules and data types. So with that you can always control who can delegate rules.
Here is a link to delegation related best practices you might want to look at.
Please let me know if you have any Express specific queries.
Thanks,
Suman
TD Bank Group
CA
Hi,
We have a business requirements to allow our business users to leverage PegaExpress (in a dev like environment) to modify existing case types that were initially developed in 6.2.
Are there any specific pre-requisites on those case types to make sure that they will be able to modify them in Pega Express?
Thanks,
Pegasystems Inc.
IN
Hi Patrick,
As you say the cases types were created with 6.2, I guess you won’t have stages and steps in those case types.
If it’s not a stage based case type, you may not be able to edit them in Express.
Thanks,
Suman
TD Bank Group
CA
Hi Suman,
Thanks for your reply.
Besides stages, anything else required? We can manage to introduce stages in them but I want to make sure that nothing else is required.
Cheers,
Patrick
Pegasystems Inc.
IN
Hi Patrick,
I guess it won’t be that straightforward. It will depend on how the case types are configured. You might find lot of items as locked in Express. The UI which you might have, won’t be editable in Express. You can see here how to create a section which can be edited in Express. Similarly the fields (properties) , processes won’t be available in Express unless they are marked as Relevant Records. You can learn more about Relevant Records here. In the current version all these are done automatically when we design the case types in case designer or Express.
Thanks,
Suman
Standard Chartered Bank
SG
Subject : Re-using Data Models across the enterprise
Hi Suman,
In our organization , we are planning to educate the business user to use pega express to design simple workflows. We are already having enterprise global system to manage client queries via email. If I want to use the existing components or data model which I have in enterprise layer , how can we enable that in the pega express level.
If you need more information , please let me know.
Thanks
Venkatesh Velu
Pegasystems Inc.
IN
Hi Venkat,
The items which are visible in Express managed through relevant records. Relevant records are the list of rules most likely to be reused in a case type or data type. The relevant records define the design time prompting and filtering in various places in Express. This enables Express to show the user only the most relevant items while designing the case types and data types. You can manage the relevant records from the relevant records landing page: Designer Studio -> Application -> Inventory -> Relevant Records.
As of the current release (7.3.1) you can configure the following types of rules as relevant records:
- Property: You can define relevant properties or fields for a case type or for a data type.
- Section: You can define relevant section or views for a case type or for a data type.
- Flow: You can define relevant flows or processes for a case type.
- Flow action: You can define relevant flow actions or user actions for a case type.
- Correspondence: You can define relevant correspondences for a case type.
This list will vary based on the Pega version you are using. You can learn more about relevant records here. By adding records to relevant records you can achieve what you are looking for.
Pegasystems Inc.
IN
Hello!
Thank you for the great discussion!! This sessions ends today. For any new questions, please write a new post.
A huge thank you to Suman for being our expert despite the holidays!!
Regards,