#Pega

[@rkjaya]

Thanks Harsha very easy to understand

[@HarshaTrainingsacademy]

Thank you for your comment... We will try our best to share better knowledge to students... Hope you are enjoying the content.. Thanks Harsha Trainings

[@SuneelKumar-kf1wg]

Very good video!! Easy to understand!! Great trainer!!

[@HarshaTrainingsacademy]

Thank you for your comment... We will try our best to share better knowledge to students... Hope you are enjoying the conetent.. Thanks Harsha Trainings

[@taniagupta5192]

Best tutorial Harsha!!!

[@HarshaTrainingsacademy]

You're very welcome!

[@monikasusan2734]

Hi , Please explain on how to handle exception when email listener fails to create case / when email service is down, an email should be sent to the receipts

[@HarshaTrainingsacademy]

Handling exceptions when an email listener fails to create a case or when the email service is down in Pega, and you want to send an email to recipients, typically involves a combination of error handling and notification mechanisms. Here's a step-by-step guide on how to handle such exceptions and send emails to recipients when work object creation fails: 1.Identify Exception Scenarios: Determine the specific scenarios that can lead to email listener failures or when the email service is down, causing work object creation to fail. These scenarios could include email format issues, connectivity problems, or other technical issues. 2.Create an Exception Handling Process: Define a clear process for handling exceptions when work object creation fails. This process should outline what actions to take when an exception occurs, who should be notified, and how the issue should be resolved. 3.Error Handling Flow: Create a dedicated flow or subprocess within your Pega application to handle exceptions. This flow will be triggered when an exception occurs during email processing or work object creation. 4.Exception Logging: Inside the error handling flow, include steps to log details of the exception. Use Pega's logging and tracing features to capture information about the error, including error codes, timestamps, and error descriptions. 5.Notification: Configure Pega to send email notifications to the relevant recipients when an exception occurs. You can use the Email Smart Shape or the Send Email utility in Pega to send these notifications. Ensure that the notification includes details of the error and any relevant information for troubleshooting. 6.Retry Mechanism: Implement a retry mechanism within the error handling flow. Depending on the nature of the error, you may want to automatically retry the email processing or work object creation after a certain interval. Configure a wait time and the number of retry attempts. 7.Escalation: Define escalation paths for unresolved errors. If the error persists after several retry attempts, you may want to escalate the issue to higher-level support or administrators. 8.Work Object Creation or Update: Depending on the nature of the error and your business requirements, you may need to create a new work object or update an existing one to track the resolution process. Assign this case or task to the responsible support team or individuals. 9.Logging and Auditing: Ensure that all error-handling actions and decisions are logged and audited for future reference and analysis. This will help in identifying recurring issues and improving the system's reliability. 10.Monitoring: Implement continuous monitoring of your email listener and associated processes. Set up alerts and monitoring dashboards to proactively identify issues and address them before they impact your operations. 11.Testing and Validation: Thoroughly test your error handling mechanisms in a controlled environment to ensure they work as expected. Simulate various error scenarios to validate the response and notifications. 12.Documentation: Document your error handling processes and mechanisms, including who to contact in case of escalations and how to resolve common issues. 13.Regular Maintenance: Periodically review and update your error handling strategy and mechanisms as your application evolves. New error scenarios may emerge, and improvements can be made based on the lessons learned.

[@monikasusan2734]

Thank You So Much

[@shubhamchoubey3284]

Please provide a video on FILE LISTENER

[@naveenkumarb2094]

we need to create all the rules manually like email account service package and email licenser like that

[@HarshaTrainingsacademy]

To manually create rules for email account service packages and email licenser in an Email Listener, you would typically follow these steps: 1. **Email Account Service Package Rule**: - Determine the features and configurations you want to include in the email account service package, such as storage limits, forwarding options, spam filtering settings, etc. - Access the Email Listener configuration or administration interface. - Look for options related to defining email account service packages. - Create a new package by specifying its name and configuring the desired features and settings. - Save the changes to activate the new email account service package. 2. **Email Licenser Rule**: - Determine the allocation model for email licenses (e.g., per user, per device). - Define the criteria for assigning licenses, such as user roles, departments, or other relevant factors. - Access the Email Listener configuration or administration interface. - Look for options related to email licenser rules or license management. - Create a new licenser rule by specifying the allocation model, assignment criteria, and any renewal or expiration rules. - Save the changes to activate the new email licenser rule. By manually creating these rules within the Email Listener configuration, you can effectively manage email account service packages and license allocations according to your organization's requirements. Additionally, this allows for flexibility and customization to meet specific needs.

[@naveenkumarb2094]

Hi Harsha in 8.7V we don't have Email Wizard then how can we create all the rules

[@HarshaTrainingsacademy]

In Pega Platform 8.7V or any version where the Email Wizard is not available, you would typically create email-related rules manually by following these steps: 1. **Email Account Service Package Rule**: - Navigate to the App Studio or Dev Studio in your Pega application. - Go to the relevant rule category where email-related rules are managed, such as Data Model or Integration. - Create a new Email Account Service Package rule manually. - Define the properties and settings for the email account service package, including storage limits, forwarding options, spam filtering settings, etc. - Save the rule to activate the new email account service package. 2. **Email Licenser Rule**: - Similarly, navigate to the appropriate rule category in App Studio or Dev Studio. - Create a new Email Licenser rule manually. - Specify the allocation model (e.g., per user, per device) and define the criteria for assigning licenses, such as user roles, departments, or other relevant factors. - Configure any renewal or expiration rules as needed. - Save the rule to activate the new email licenser rule. Although the Email Wizard provides a guided interface for creating email-related rules, you can still accomplish these tasks manually by directly accessing the rule creation screens in Pega Platform. Ensure that you have the necessary access permissions and follow best practices for rule management while creating and configuring these rules.