Reusing the standard queue processor
Front Stage wants its Booking application to send a specific email to each participant.
Email contents are different for different roles (for example, customers or sales coordinators)
Front Stage wants the application to send emails efficiently and immediately.
The following table provides the credentials you need to complete the challenge.
1 Identify design options
Option 1: Standard Queue Processor
By reusing the standard queue processor, your application can send notifications to all participants with custom messages as per their role asynchronously and immediately. As a result, case processing can continue without waiting for the background process to complete. You can use the standard queue processor rule to send email notifications to all participants.
Option 2: Job Scheduler
Create a job scheduler to send notifications with custom messages to all participants at a specific time.
Option 3: Advanced agents
Create an advanced agent to send custom messages to all participants. Update the agent schedule to execute and send custom emails to all participants at a specific time, which can be different from the agent rule.
2 Evaluate design options
Standard queue processor
3 Recommend the best design option
It is recommended to use a standard queue processor to send email notifications to all participants without any additional rules.
4 Review solution details
To review the implemented solution, switch the application to Booking Background Queue Processing when you are logged in as the Admin@Booking operator.
5 Perform the following tasks
To complete the assignment, accomplish the following tasks.
- Create a correspondence rule for the Customer, Sales Coordinator, and others.
- Log in as Admin@Booking.
- Create a decision table to return the correspondence name that is based on the party role.