You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -93,7 +97,7 @@ The following is an example of how to specify the configuration in code:
93
97
classResourceController < ApplicationController
94
98
defindex
95
99
begin
96
-
100
+
97
101
customerId =""# Your Queue-it customer ID
98
102
secretKey =""# Your 72 char secret key as specified in Go Queue-it self-service platform
99
103
eventConfig =QueueIt::QueueEventConfig.new
@@ -104,41 +108,46 @@ class ResourceController < ApplicationController
104
108
eventConfig.extendCookieValidity =true# Should the Queue-it session cookie validity time be extended each time the validation runs?
105
109
# eventConfig.culture = "da-DK" # Optional - Culture of the queue layout in the format specified here: https:#msdn.microsoft.com/en-us/library/ee825488(v=cs.20).aspx. If unspecified then settings from Event will be used.
106
110
# eventConfig.layoutName = "NameOfYourCustomLayout" # Optional - Name of the queue layout. If unspecified then settings from Event will be used.
@@ -148,3 +157,32 @@ class ResourceController < ApplicationController
148
157
end
149
158
end
150
159
```
160
+
161
+
## Advanced Features
162
+
### Request body trigger
163
+
164
+
The connector supports triggering on request body content. An example could be a POST call with specific item ID where you want end-users to queue up for.
165
+
For this to work, you will need to contact Queue-it support or enable request body triggers in your integration settings in your GO Queue-it platform account.
166
+
Once enabled you will need to update your integration so request body is available for the connector.
167
+
You need to create a custom RailsHttpContext similar to this one (make sure to inherit from `QueueIt::RailsHttpContext`):
Then, on each request, before calling the any of the SDK methods, you should initialize the SDK with your custom RailsHttpContext implementation, instead of the RailsHttpContext:
0 commit comments