Hi,My customer is using non-blocking appointment templates. They are not performing the check on the slot before acceptance to ensure it is still available as they are happy to deal with it manually if it is not allocated. I have two questions:Is it necessary to respond to the offers (either accept or reject) given that the customer is not concerned about checking the slot validity? Does it matter what the offer_expiry_datetime on the appointment template it is non-blocking, can this be set to 0 ?Thanks,Tom
Hopefully an easy one,When making an appointment request via FSM does the response code on the time commit always default to APPOINTMENT? I can’t see a related scheduling app param so I assume this is hardcoded?Thanks,Tom
Hi,What does the ‘Is proportional’ field mean on the rule ‘Limits how soon a membership period of a given category can start after the previous period’. Can someone explain and provide an example please?Thanks,Tom
Hi,Hopefully a straightforward question:Does the automatic rota generation process consider existing shifts when trying to meet requirements and rules or only the period the rota generation is taking place over?Thanks,Tom
Hi,I’m getting the below error when accepting an appointment offer from PSO in FSM:I think the problem may be when FSM tries to create a time_commit record for the task. I’ve set the PRIMARY response code (as I believe this is the one used when creating a time_commit in FSM after accepting an appointment offer) to have a calendar id: Note that this customer has renamed response code to SLA Profile. I suspect it is down to missing config or a business rule but it’s hard to pin down exactly what. Understanding how the baseline works might help.Thanks,Tom
Hi, We have noticed that when sending a COMPLETE DSE broadcast back to FSM from PSO, the dse_allocation table only contains the details for the latest visit of an activity. For example we have a split activity which is split into 7 visits, only the allocation data for the 7th visit is stored in the dse_allocation table. We have checked the incoming broadcast XML from PSO and it contains the allocation records for all the visits so the issue is definitely in FSM. We are using FSM 6 UPD 14.We noticed a fix in UPD13 (G2279817) which might be related ?@Aaron.Sleight are you able to help with this at all please? Thanks,Tom
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
