What is the Major difference between Pega v7 and v8 ?

 What is the Major difference between Pega v7 and v8 ?

 

There are new functionality and features added in PRPC 8 and one of major change is in PRPC 8 there are four different studio i.e. 

  1. Dev Studio(Designer Studio in 7), 
  2. App Studio, 
  3. Admin Studio(SMA moved under admin studio),
  4. Predictive studio(Data Scientist and AI team).
  5.  
  6.  

Pega Platform 8.6 and build resilient, low-code automation everywhere. The new Pega Platform lets you deliver breakthrough outcomes end-to-end with the power of real-time AI.

 

Click here for   more differences

Comments

Post a Comment

Popular posts from this blog

Split For Each shape in pega - Parallel processing in Pega

Image
  Split For Each shape in pega Parallel processing in Pega We can allow users to perform multiple tasks independently to complete the work, in pega we can this as parallel processing. In a stage or flow rule, we can add smart shapes to achieve this parallel processing. Smart shapes in pega Pega has defined some smart shapes like  Split Join ,  Split-For-Each,  and  Spin-Off . We have to use these smart shapes in sub-process shape. Each shape can call one or more processes to proceed in parallel. Split For Each shape in pega Split for each allows us to run a single process multiple times by looping through a Page List or Page Group. The main flow continues when processes on the PageList/PageGroup processed. I Will explain with an example:  In a Service Request case type when the user submits a request it should be going for the inspection process. Used Split Join shape to fulfill this requirement with two sub-processes. When all sub-processes are complete, t...
Read more

Queue processor FAQ

Image
  Queue processor FAQ A queue processor rule is an internal background process that you configure for queue management and asynchronous message processing. Use standard queue processor rules for simple queue management or low-throughput scenarios, or use dedicated queue processor rules for higher-scaling throughput, and customized or delayed processing of messages. Best practice is to configure queue processors instead of using standard agents to manage message queuing in Pega Platform. For details, see   Background processing best practices . Frequently Asked Questions about queue processors include the following: How do I queue a message to a queue processor? You can queue a message to a queue processor by performing either of the following actions: Use the   Queue-for-Processing   activity method. Use the   Run in Background   SmartShape when you create a case. For more information, see   Queue-For-Processing method   and   Running a backg...
Read more

Spinoff and Split join shape in pega

Image
  Explain Spinoff and Split join shape in the context of Pega. Spinoff join shape: When one flow execution starts another flow execution that runs asynchronously and independently of the first flow execution, this is known as a spinoff. The first flow does not pause or wait for the second flow's results. The second flow could work on the same or a different work item than the first flow. At the workflow level, spinoffs enable parallel processing of work. While one department or business unit performs its functions for the work item at its own pace and according to its own flow, another department works on the same work item. Increased parallelism can reduce end-to-end resolution times, allowing for more efficient staffing and better customer service. Split Join Shape: On the Diagram tab of a flow rule, a Split Join shape can be found. This shape causes work item processing to divide into two or more distinct flow executions that run asynchronously and then rejoin later at runtime. ...
Read more