@AneeshaG Thank you. I've gone through this. It doesn't have any realtime implementation scenario for TODOList ,Data Instance first & LimitedAvailability&Concurrency . Want to understand more on the scenarios where these patterns can be chosen.
Posted: 3 months ago
Updated: 3 months ago
Posted: 5 Oct 2021 9:56 EDT Updated: 5 Oct 2021 9:57 EDT
Eg: Case types like Issue an Accreditation for Organization. There can be several checklist items to be evaluated and confirmed for Accreditation. Not all checklist items require a child case. All we need to do then is create a data instance for these checklist items. Say 5 checklist items are corresponding to a site visit, combine them and show them in one assignment. The next 5 checklist items are related to Finance, group them to another assignment. These checklist items are TO-DO items and all the user has to do is mark them complete.
Data Instance First
Eg: Consider a service request to Register a new member. If we leverage mashup with Create New Case, for every request we will end up creating a Registration case. Instead, it may be important to validate whether all information is accurate. If the user record already exists. It is good practice to create a data instance first and then process them to create a case. Also, you will have an advantage over the genuine number of requests.
Limited Availability and concurrency
Eg: Consider train reservations. The concurrent requests during holidays could be higher than usual. Capturing every request as a data instance, and keep allocating seats incrementally whilst the rest are in a waiting period solves the problem of over-booking.