Hosted Scheduling Query Params

Question and Answers
1

I have a couple questions regarding the hosted scheduling page that are unanswered and I thought it best to consolidate them here and bump them.

  1. On the hosted scheduling page why are we not permitted to use read_only on query params like we were able to in v2? Is this going to be fixed?
  2. Why can we not use query params at all for the hosted re-scheduling page at https://book.nylas.com/us/reschedule/:booking_ref?name=BillyBob
  3. Why does every single query param need to have its own custom field entry? It’d be nice if there was a way to hide these if possible, above having just a read_only

Thanks

2

All good question @sboynton Will come back with some answers as soon as I can :wink:

3

@Blag Any update here? I’ve had these questions up for about a week in their respective places with no answer, and they’re incredibly important to our flow.

4

Hello @sboynton sorry about that…

1.- The current implementation of pre-filling from 
query parameters did not originally include the 
read_only use case, as it wasn’t part of the initial 
requirements.

2.- 1. This was an oversight on our part. 
We have a PR to fix this. It will be available soon.

3.- I believe this functions similarly to v2, where 
custom fields need to be configured in the 
scheduler config (editor / API). It sounds like 
they're asking for a feature where custom fields 
can be passed via query parameters 
(without being set up in the config) and remain 
hidden on the form, but are still included in the 
booking request. This would be a new feature. 
Not sure it will be supported.
1 Like