Routing weather cases to facility coordinators
If the probability of rain is greater than or equal to 40 percent for an event day, a process to make other arrangements begins. A facility coordinator with the least amount of urgent work that is specialized in weather preparation receives the following tasks:
- Set up tents
- Provide disposable raincoats
- Cover seating area
The following table provides the credentials you need to complete the challenge.
The sample facility coordinator users are specialized as shown in the following table.
|FacilityCoordinator3@Booking||Weather and Parking|
1 Identify design options
If the forecast service indicates that rain is probable for a specified event day, then the case needs to be routed to the weather-specialized facility coordinator to make arrangements. Once the arrangements are made, the facility coordinator submits the case and then waits for the next forecast.
If the forecast service indicates no rain probability for a specified event, the case proceeds and awaits the next forecast.
The process repeats for all the event days. If the forecast is happening for the last event day (one day before the previous event day), post forecast, the case needs to wait for the event closure. When the event ends, it gets routed to the weather-specialized facility coordinator for the teardown.
If the forecast indicates that there is no rain probability rain, but in reality, it rains, the facility coordinator needs an option to manually invoke the arrangements while the case is waiting for the next forecast.
The case gets resolved when the facility coordinator completes the teardown.
The routing solution can be implemented with one of the following options.
Option 1: Assign task to worklist
Two standard routers can be leveraged when using skilled-based routing: ToLeveledGroup and ToSkilledGroup. Both of these routing rules route to a user in a specified work group with the designated skill.
ToLeveledGroup is a valid option because it takes the user's current workload into consideration. ToSkilledGroup is not a valid option in this scenario because this router does not take workload into consideration.
Option 2: Assign task to work queue
The standard router activity ToSkilledWorkbasket can be leveraged when using skilled-based routing. Facility coordinators can pull the cases from the queue by using the Get Next Work functionality. However, this option is not applicable in this scenario because the router does not take workload into consideration.
Option 3: Leverage custom router activity
Creating a custom routing activity is a valid option if a standard router does not cover the routing requirements. Because ToLeveledGroup takes both skills and workload into account, a custom router is unnecessary.
2 Evaluate design options
|Assign task to worklist||
|Assign task to work queue||
|Leverage custom router activity||
3 Recommend the best design option
It is recommended to route the weather case assignment to the user worklist by leveraging the OOTB ToLeveledGroup activity, which suffices the requirement and does not require customization.
4 Review solution details
The solution is part of the following case life cycle and workflow, which is part of WForecast ruleset. The solution is based on a skill-based routing.
5 Perform the following tasks
To complete the assignment, complete the following tasks.
- Create the specialized skills in respective application rulesets.
- Associate the facility coordinator operator records with Weather skills.
- Update the track preparation and teardown assignment to be routed to the facility coordinators by using ToLeveledGroup router activity that is associated with the weather skill.
- Verify the work by creating cases weather and see that cases are routed to facility coordinators based on the amount of work and skills.