envoy-hooks 0.9.2 → 0.9.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 823a05c8d454becc1b2cb7921832436a790c3d99b0a7b370ab98fe4335ead22a
-  data.tar.gz: 16eb2a0e6f82a4915c66ca5a0f59c9335bb004738f78510bfeaa923e13f8618e
+  metadata.gz: 22909d2d61ea631aa5c416510ccb95440a7265f5c793bf0794221c2f2dd50b18
+  data.tar.gz: 3706f19b970c11c6d67a679edf2464e804af878f1209746e59e12b78a5930c81
 SHA512:
-  metadata.gz: b83df03d0fbc601589785e4a96972ec0aa4cc48ea7a41d724494b35dbb408112f3b6b1eda0bc9ebb5cd00b1046c2fb11aade9978685a59ae8a16c148f5afc750
-  data.tar.gz: 4bfa3ce0f3616690a4ed80efae2f2fc1809bc47accb9518c574202808c648d3089a447b285ec5e136ab828992fde42ae416187c514053a588cc64adaad7ed5bf
+  metadata.gz: 1c665b82b32b50af42d6363aacff26326ed4ae47cde23a044ef5a0dee3f17152153b928a7641d3a0ed564f1a95f8f2e0674bd5fb42a60b6835bbcab4d4e60118
+  data.tar.gz: '09ad5daf753fd75807c3cfad4ccf21bd3624cd5e00f66e3a11e34b0f1e3e8c07995a2312184a0f3761d2e690d25094b655b4ada9e8f6154cbe4da6c4ecec791b'

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    envoy-hooks (0.9.2)
+    envoy-hooks (0.9.3)
       faraday (~> 0.15.4)
       faraday-net_http (~> 1.0)
       faraday_middleware (~> 0.12.2)

data/README.md

@@ -10,6 +10,7 @@ It has the following three API methods regarding UI Hooks and their subscription
 
 * `upsertSubscription`
 * `triggerUIHooks`
+* `triggerZoneUIHooks`
 * `subscribedUIHooks`
 
 These are the methods listed in [the Jira ticket](https://envoycom.atlassian.net/jira/software/c/projects/DEVP/boards/131?modal=detail&selectedIssue=DEVP-829) describing what's required for the email customization screen and the dynamic email sender.
@@ -171,6 +172,32 @@ hooksService.triggerUIHooks(
 )
 ```
 
+The return value will be an array of objects.  Each object will contain a lot of information, but the most important part is `response` - that will contain the HTML or JSON from the UI Hooks, which will then be used to create the UI.
+### **`triggerZoneUIHooks`**
+
+This is how we fetch custom UI at a Connect zone.  The name "trigger Zone UI Hooks" comes from the fact that we are getting the custom UI from potentially multiple UI Hooks, and we "trigger" them in order to fetch the data.
+
+This will act to fetch the custom UI, which we will receive in the response.
+
+```rb
+hooksService.triggerZoneUIHooks(
+  # REQUIRED
+  zoneIds: [3],
+  triggerName: "welcome_email", # The UI Hook name to invoke (deprecated)
+  triggerNames: ["welcome_email"], # The list of UI Hook extension names to invoke (triggerName or triggerNames required)
+  responseType: "JSON", # only other option is HTML.  Determines whether you get Component JSON or prerendered HTML.
+
+  # XOR REQUIRED
+  resourceId: 341153, # the ID of the invite we are working with
+  resourceIds: [341153, 341153] # array of IDs of the invites we are working with
+
+  # OPTIONAL
+  previewMode: false, # Whether or not to run in preview mode.  Preview mode makes it so you do not need to send in a resourceId
+  accentColor: "#123DEF", # Override the default Envoy accent color on applicable UI components.  Currently only in emails, but that could change.
+  uiHookIds: [2954, 8271], # The specific UI hooks to invoke. If you don't include it, _all_ UI Hook subscriptions that match the locationId and triggerName will trigger.
+)
+```
+
 The return value will be an array of objects.  Each object will contain a lot of information, but the most important part is `response` - that will contain the HTML or JSON from the UI Hooks, which will then be used to create the UI.
 ## Client Config
 

data/lib/envoy/hooks/version.rb

@@ -2,6 +2,6 @@
 
 module Envoy
   class Hooks
-    VERSION = '0.9.2'
+    VERSION = '0.9.3'
   end
 end

data/lib/envoy/hooks.rb

@@ -72,18 +72,19 @@ module Envoy
                    })
     end
 
-    def triggerZoneUIHooks(responseType:, zoneIds: [], triggerNames: [], resourceId: nil,
+    def triggerZoneUIHooks(responseType:, zoneIds:, triggerNames: [], resourceId: nil, resourceIds: [],
                            resourceType: nil, accentColor: nil, previewMode: false, uiHookIds: [])
 
       validateEnum('responseType', responseType, %w[HTML JSON])
 
       validateEnum('resourceType', resourceType, %w[INVITE ENTRY]) unless resourceType.nil?
 
+      resource_ids = Array(resourceId || resourceIds)
       faraday.post('/rest/v1/zones/hooks/ui/trigger', {
                      zoneIds: zoneIds,
                      triggerNames: triggerNames,
                      responseType: responseType,
-                     resourceId: resourceId,
+                     resourceIds: resource_ids,
                      resourceType: resourceType,
                      accentColor: accentColor,
                      previewMode: previewMode,

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: envoy-hooks
 version: !ruby/object:Gem::Version
-  version: 0.9.2
+  version: 0.9.3
 platform: ruby
 authors:
 - Jeffrey-Biles-Envoy
@@ -9,7 +9,7 @@ authors:
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2023-03-07 00:00:00.000000000 Z
+date: 2023-03-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: faraday