PEGA PRPC | Queue Processor In PEGA [ Detailed explanation ] - PEGA Training

แชร์
ฝัง
  • เผยแพร่เมื่อ 18 ธ.ค. 2024

ความคิดเห็น • 37

  • @vamsipatnaik9829
    @vamsipatnaik9829 2 ปีที่แล้ว +1

    Excellent Explanation...

  • @sukhapriyas4418
    @sukhapriyas4418 13 วันที่ผ่านมา +1

    very good explanation with example scenarios especially in delay factor calculation .

  • @kunalkantibera
    @kunalkantibera หลายเดือนก่อน +1

    Thankyou so much for this in depth explaining data flow .god bless u

  • @zeebo100
    @zeebo100 ปีที่แล้ว +1

    Thank you Harsha for this in depth explanation. Especially the worked example of the Queue Processor's retry/Delay factor. 👍

  • @akhilbunny6639
    @akhilbunny6639 10 หลายเดือนก่อน

    Good explanation about queue processor complete topic thanks!

  • @SharmilaThurai
    @SharmilaThurai ปีที่แล้ว

    Thank you Harsha. Your detail explanation is always helpful.🙂

  • @HeloWorld-np3jk
    @HeloWorld-np3jk 7 วันที่ผ่านมา

    Thanks to pega god harsha

  • @snehasiz9128
    @snehasiz9128 ปีที่แล้ว

    Detailed explanation! good work sir.

  • @UMAMAHESWARIR-kc4cv
    @UMAMAHESWARIR-kc4cv 6 หลายเดือนก่อน

    Good explanation. Thank you sir

  • @subhalaxmiroutray8544
    @subhalaxmiroutray8544 8 หลายเดือนก่อน +1

    Hi Harsha, What is the limitation of queue processor ? Could you please give some examples of actions which cant be achieved by a Job scheduler

    • @HarshaTrainingsacademy
      @HarshaTrainingsacademy  8 หลายเดือนก่อน

      Queue processors and job schedulers serve distinct purposes in process automation, each with its own limitations and advantages. Here are the limitations of queue processors and examples of actions that might be challenging to achieve solely with a job scheduler:
      Limitations of Queue Processors:
      1. **Single-threaded Processing**: Queue processors typically operate on a single thread, which means they process items sequentially. This can lead to performance bottlenecks if the processing load is high.
      2. **Manual Error Handling**: Queue processors might require manual error handling and recovery mechanisms if items fail to process correctly. Without proper error handling, failed items may accumulate in the queue, affecting system performance.
      3. **Scalability**: While queue processors can be effective for managing small to medium-sized workloads, they may struggle to scale efficiently with large volumes of data or high-throughput processing requirements.
      4. **Complexity**: Implementing complex business logic or workflows in a queue processor can be challenging and may require additional customization and configuration.
      Examples of Actions Challenging to Achieve Solely with a Job Scheduler:
      1. **Dependency Management**: Job schedulers may struggle to manage dependencies between tasks or jobs, especially when tasks need to execute in a specific order or rely on the completion of other tasks.
      2. **Event-Driven Processing**: Handling event-driven processing, such as reacting to real-time events or triggers, is more challenging with a job scheduler. Queue processors are better suited for event-driven architectures, where tasks need to be executed in response to specific events or conditions.
      3. **Distributed Processing**: Coordinating distributed processing across multiple nodes or systems is more complex with a job scheduler. Queue processors often provide built-in support for distributed processing and load balancing.
      4. **Dynamic Scaling**: Automatically scaling processing resources based on workload demand is difficult to achieve with a job scheduler alone. Queue processors can dynamically scale processing capacity by adjusting the number of processing nodes or workers based on workload fluctuations.
      5. **Message Processing**: Queue processors are well-suited for handling message-based processing, such as processing messages from messaging systems like Kafka or RabbitMQ. Job schedulers may lack native support for message processing and require additional integration efforts.

  • @arunavamukherjee2942
    @arunavamukherjee2942 2 ปีที่แล้ว +1

    A detailed explanation of Queue Processor. Excellent!!! Thank you for sharing this. Can we have a similar for Data Flows too?

    • @HarshaTrainingsacademy
      @HarshaTrainingsacademy  2 ปีที่แล้ว

      Yes, soon...
      Harsha Trainings is one of the leading and Placement Consultant Provided training with qualified trainers on PEGA,DEVOPS, PowerBI,JAVA,DATA SCIENCE, MULESOFT ,Spring&Microservices,OracleFinance,Appian,Core&Advance java,Django,Communication&Varbal and other various leading software technologies….
      For those who have gap after education, we have job placement assurance courses...
      Subscribe to our channel to learn best of best in technology... For training call us on 9652532753, 9885312299

    • @anilkumarreddy4053
      @anilkumarreddy4053 2 ปีที่แล้ว

      Yes

  • @anilkumarreddy4053
    @anilkumarreddy4053 2 ปีที่แล้ว +1

    Very good explanation. Do it for data flows also

  • @vikastsk
    @vikastsk 2 ปีที่แล้ว +1

    How to get instances that are using standard queue type, say i want list of all the flows/activities using standard queue processor, from admin studio i can get the scheduled/broken/ready items under the pzstandardprocessor, but not the full list.

    • @HarshaTrainingsacademy
      @HarshaTrainingsacademy  2 ปีที่แล้ว +1

      Hi Vikar, I think this is not possible to find so... Let me check if it can be... As of now, I say it cant be..
      Harsha Trainings is one of the leading and Placement Consultant Provided training with qualified trainers on PEGA,DEVOPS, PowerBI,JAVA,DATA SCIENCE, MULESOFT ,Spring&Microservices,OracleFinance,Appian,Core&Advance java,Django,Communication&Varbal and other various leading software technologies….
      For those who have gap after education, we have job placement assurance courses...
      Subscribe to our channel to learn best of best in technology... For training call us on 9652532753, 9885312299

  • @chiruglory2523
    @chiruglory2523 2 ปีที่แล้ว +1

    Hi Harsha,
    I have a case and it is differentiate with customer type(gold, dimond) and daily cases will get create with customer type either gold or dimond. Now the scenario is, system should send a notification to the case manager after some hours of creation time. Let's say for customer type gold, notification should fire after 8 hours of case creation and for customer type diamond, notification should fire after 4 hours. How we can achieve this one ?

    • @HarshaTrainingsacademy
      @HarshaTrainingsacademy  2 ปีที่แล้ว

      Hi , we can achieve this by using SLA, with goal time escalation.
      Here, goal time should be set with currentdatetime+4 hours / currentdatetime+ 8 hours
      This can be acheived by calling a pre processing DT --> Call decision table --> Retunrn values as above for the given condtions you mentioned..
      We offer pega trainings with 4 real time projects, complete hands on. If you or any one of oyur friends looking for same , please forward our number 9652532753.
      Please do not forget to subscribe our channel. Your Subscription will help us to do more better videos. Also hit the BELL icon for new video notifications.
      Harsha Trainings is one of the leading and Placement Consultant Provided training with qualified trainers on PEGA,DEVOPS, PowerBI,JAVA,DATA SCIENCE, MULESOFT ,Spring&Microservices,OracleFinance,Appian,Core&Advance java,Django,Communication&Varbal and other various leading software technologies….
      For those who have gap after education, we have job placement assurance courses...
      Subscribe to our channel to learn best of best in technology... For training call us on 9652532753, 9885312299

    • @chiruglory2523
      @chiruglory2523 2 ปีที่แล้ว

      @@HarshaTrainingsacademy thanks for the response. Can't we achieve with delayed queue processor with delayed
      time as per the requirement mentioned above ?

  • @Jayaversion
    @Jayaversion 2 ปีที่แล้ว +1

    What is the use of the pulse feed in pega

    • @HarshaTrainingsacademy
      @HarshaTrainingsacademy  2 ปีที่แล้ว

      Hi Amalapuramammi, pulse is a comment place where different parties can write comments, action items, finished items details. Also they can collaborate each other with comments... One more thing is that, they can share the attachments through pulse section....
      Harsha Trainings is one of the leading and Placement Consultant Provided training with qualified trainers on PEGA,DEVOPS, PowerBI,JAVA,DATA SCIENCE, MULESOFT ,Spring&Microservices,OracleFinance,Appian,Core&Advance java,Django,Communication&Varbal and other various leading software technologies….
      For those who have gap after education, we have job placement assurance courses...
      Subscribe to our channel to learn best of best in technology... For training call us on 9652532753, 9885312299

  • @SrinathMorrimekala
    @SrinathMorrimekala 3 หลายเดือนก่อน

    Hi Team , QP is delayed by 1 minute , even though it is processing with in seconds instead of waiting for 1 minute, How this is happening ?

  • @HMCooking
    @HMCooking 2 ปีที่แล้ว

    I have a property named Approval Status in the data class that can store the status of the particular case but I don't know how to store the case status into the database records. Please guide me how can I add the status in the records.

    • @HarshaTrainingsacademy
      @HarshaTrainingsacademy  2 ปีที่แล้ว

      Hi Prachi,
      1. u should create a temp page from the data class...
      2. Assign status value to the page of data class
      3. Do obj save of data class page
      4. Commit, done

  • @RRBANDSSC
    @RRBANDSSC ปีที่แล้ว

    Hi sir ,can you make a video on job scheduler detailed explanation