Skip to main content
Solved

Appointment Booking Outside the Scheduling Window


Forum|alt.badge.img+9

Hi Experts,

We have a specific requirements from customer. Does anyone faces such situation, your guidance is highly appreciated.

  1. Customer has an Appointment Window for 6 months in current legacy system. So they want the from IFS too. But as per IFS that long window is not allowed. Do you have any best practices for the Appointment Scheduling window. I have experience of having 42 days Scheduling window (3 days Dynamic Work Days + 39 Appointment Work Days) but not working with 6 months window.
  2. If IFS doesn’t handle such long window any workaround to handle 6 months appointment booking window.

Your timely suggestion will help me a lot.

 

Regards,

RR

Best answer by Sajith Anushan

Thanks Sajith for the update.

Just to confirm, we have a dataset with

Process type : Appointment

Scheduling Work Days : 3

Appointment Work Days: 177

No of Slots : 20

So while requesting appointment for the tasks we should limit the Period Start and Period End so that 20 slots will be retrieved between the Period Start and Period End days.

Also the number of activities in the scheduling window of 6 months will still remain 15000 (Scheduling Work Days) + 25000 (Appointment Work Days) per dataset?

 

Am I correct in saying so? 

Regards,

RR

This is correct

View original

7 replies

Forum|alt.badge.img+22

Hi -

6 months Appointments window is fine, assuming that you are not requesting tons of slots within that 6 month for one appointment request. Best practice is to limit slots per request to 20. 


Forum|alt.badge.img+9
  • Author
  • Sidekick (Partner)
  • June 17, 2026

Thanks Sajith for the update.

Just to confirm, we have a dataset with

Process type : Appointment

Scheduling Work Days : 3

Appointment Work Days: 177

No of Slots : 20

So while requesting appointment for the tasks we should limit the Period Start and Period End so that 20 slots will be retrieved between the Period Start and Period End days.

Also the number of activities in the scheduling window of 6 months will still remain 15000 (Scheduling Work Days) + 25000 (Appointment Work Days) per dataset?

 

Am I correct in saying so? 

Regards,

RR


Forum|alt.badge.img+2
  • Do Gooder (Partner)
  • June 17, 2026

Hi ​@RRPATNAIK 

According to the PSO documentation also, having an appointment window of 6 months should be feasible. 

 


Forum|alt.badge.img+6
  • Do Gooder (Partner)
  • June 17, 2026

​@Sajith Anushan  Could please attached the document or the name of the Document to get more details on this?


Forum|alt.badge.img+22

​@Ashish Check Appointment Booking Concept guide here.

 


Forum|alt.badge.img+22

Thanks Sajith for the update.

Just to confirm, we have a dataset with

Process type : Appointment

Scheduling Work Days : 3

Appointment Work Days: 177

No of Slots : 20

So while requesting appointment for the tasks we should limit the Period Start and Period End so that 20 slots will be retrieved between the Period Start and Period End days.

Also the number of activities in the scheduling window of 6 months will still remain 15000 (Scheduling Work Days) + 25000 (Appointment Work Days) per dataset?

 

Am I correct in saying so? 

Regards,

RR

This is correct


Forum|alt.badge.img+6
  • Do Gooder (Partner)
  • October 16, 2026

​@Sajith Anushan There is a requirement from customer  that in they show upto 2months of Slots[400 Slots] on there portal for customer to choose from which means the best practice of 20 slots is not going to fulfill the requirement hence we need to understand to what maximum extent this value can be increased without impacting the PSO.