Skip to main content
Question

Parallel Appointment request in IFS PSO

  • Oct 20, 2026 9:36 AM UTC
  • 2 replies
  • 42 views

Forum|alt.badge.img+6

We have requirement from a customer that they would need around 3 months of appointment slots to be shown.

While we know almost 600 slots will break the system in one go, there was a question if system can handle parallel requests.

Which means about 10 parallel calls with different start dates associated to the same activity each giving like 50 slots (lets just assume 50 slots work for now).

 

Can someone please help if this works properly?

 

We just ran the test via postman, but the results are not consistent. Sometimes it give results, sometimes there are errors. Not sure what is the reason for that.

Also, even though the SlotRowNo is same in all the request responses, we are allowed to confirm the slot from first request (which is not the latest) which for me is very strange. Is it how we are expecting the system to work?

We are currently on IFS Cloud 25R1.

 

Awaiting the response at the earliest based on your experience.

2 replies

  • Superhero (Employee)
  • Oct 20, 2026 9:41 AM UTC

I'm very curious to understand why you would need three months worth of offers? Who are you going to display that to/how are you displaying that? 
 


Forum|alt.badge.img+6
  • Author
  • Do Gooder (Customer)
  • Oct 20, 2026 10:05 AM UTC

​@anmise - Customer’s front end portal is designed in such a way that they show almost 3 months of slot in a go. A list is shown with all the slots (not available ones greyed out). User is expected to just click on the slot which they would like to confirm.

 

Customer is not very keen in changing their front end, definitely not bringing it down to 20 slots (which is IFS best practice) that results in 2.5 days of slot.

 

Just to add, their current legacy system is capable of sending 80-100 slots in one request and also permits parallel calls (so 6 parallel calls are being made currently)