Merge pull request #5676 from segmentio/develop

stayseesong · web-flow · commit 8951604577b4 · 2023-11-14T10:31:48.000-08:00
Release 23.46.1
diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2023-11-09 
+# destination categories last updated 2023-11-14 
 items:
 - display_name: A/B Testing
   slug: a-b-testing
diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-11-09 
+# destination data last updated 2023-11-14 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -15383,7 +15383,7 @@ items:
   display_name: CDP Resolution
   name: CDP Resolution
   slug: cdp-resolution
-  hidden: false
+  hidden: true
   endpoints:
   - US
   regions:
@@ -22609,8 +22609,6 @@ items:
   categories:
   - Customer Success
   - Email Marketing
-  - Marketing Automation
-  - Personalization
   logo:
     url: https://cdn-devcenter.segment.com/7c81d326-9e4f-403a-ad3c-d906e6e50507.svg
   mark:
@@ -22648,13 +22646,13 @@ items:
       Your public API key is available in Settings -> Account on your Engage
       dashboard
     required: true
-    label: API Key
+    label: Public API Key
   - name: listId
     type: array
     defaultValue: []
     description: >-
-      List ID you want to subscribe the user to. Opt-in confirmations are not
-      sent for these even if enabled for the lists
+      ID of the List you want to subscribe the user to. Opt-in confirmations are
+      not sent for this even if enabled for the List.
     required: true
     label: List ID
   actions: []
@@ -42114,7 +42112,7 @@ items:
   display_name: Insider Audiences
   name: Insider Audiences
   slug: insider-audiences
-  hidden: false
+  hidden: true
   endpoints:
   - US
   regions:
@@ -42402,7 +42400,7 @@ items:
   display_name: Insider Cloud Mode (Actions)
   name: Insider Cloud Mode (Actions)
   slug: insider-cloud-mode-actions
-  hidden: false
+  hidden: true
   endpoints:
   - US
   regions:
@@ -49130,7 +49128,7 @@ items:
   display_name: LaunchDarkly Audiences
   name: LaunchDarkly Audiences
   slug: launchdarkly-audiences
-  hidden: false
+  hidden: true
   endpoints:
   - US
   regions:
@@ -57005,7 +57003,7 @@ items:
   display_name: Optimizely Advanced Audience Targeting
   name: Optimizely Advanced Audience Targeting
   slug: optimizely-advanced-audience-targeting
-  hidden: false
+  hidden: true
   endpoints:
   - US
   regions:
diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-11-09 
+# destination data last updated 2023-11-14 
 items:
   - id: 54521fd725e721e32a72eec6
     display_name: Intercom
diff --git a/src/_data/catalog/regional-supported.yml b/src/_data/catalog/regional-supported.yml
@@ -38,6 +38,15 @@ sources:
       - eu
     endpoints:
       - us
+  - id: DY0B0Q2Gce
+    display_name: Alloy Flow
+    hidden: false
+    slug: alloy-flow
+    url: connections/sources/catalog/cloud-apps/alloy-flow
+    regions:
+      - us
+    endpoints:
+      - us
   - id: GNLT5OQ45P
     display_name: Amazon S3
     hidden: false
diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source categories last updated 2023-11-09 
+# source categories last updated 2023-11-14 
 items:
   - display_name: A/B Testing
     slug: a-b-testing
diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2023-11-09 
+# sources last updated 2023-11-14 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
@@ -81,6 +81,24 @@ items:
     categories:
       - Marketing Automation
       - SMS & Push Notifications
+  - id: DY0B0Q2Gce
+    display_name: Alloy Flow
+    isCloudEventSource: true
+    slug: alloy-flow
+    url: connections/sources/catalog/cloud-apps/alloy-flow
+    hidden: false
+    regions:
+      - us
+    endpoints:
+      - us
+    source_type: cloud-app
+    description: No Code Automation Platform
+    logo:
+      url: >-
+        https://cdn-devcenter.segment.com/a3e9338b-b769-432f-88fd-3908e6827e06.png
+    categories:
+      - Enrichment
+      - Raw Data
   - id: GNLT5OQ45P
     display_name: Amazon S3
     isCloudEventSource: true
diff --git a/src/connections/functions/environment.md b/src/connections/functions/environment.md
@@ -35,6 +35,19 @@ If you're editing an existing function, you can **Save** changes without changin
 
 You can also choose to **Save & Deploy** to push changes to all, or specific functions in your workspace that are already deployed. You might need additional permissions to deploy these changes.
 
+## Testing a function
+You have the option to test your functions code with either a sample event or by loading a default event that you can customize yourself.
+* **Sample event**: When you click **Test with custom event** you can select a sample event from any of your workspace sources to test this function.
+* **Customize the event yourself**: When you click **customize the event yourself** a default event payload loads which you can modify with the desired data. You have the option to paste in a JSON event or click **Manual Mode** and type in the fields manually. If you'd like to locate a recent event from a source that's not available by following the sample event instruction: 
+     1. Navigate to the source debugger.
+     2. Click the event you want to test and copy the raw JSON payload.
+     3. Paste the raw JSON payload into your Function Editor.
+
+Once the payload you want to test is ready, click **Run**.
+
+> info ""
+> If you create settings in your function, then you need to fill in the setting values before clicking **Run**.
+
 ## Deploying source functions
 
 > note ""
diff --git a/src/connections/reverse-etl/index.md b/src/connections/reverse-etl/index.md
@@ -298,3 +298,8 @@ Column count | The maximum number of columns a single sync will process. | 512 c
 Column name length | The maximum length of a record column. | 128 characters
 Record JSON size | The maximum size for a record when converted to JSON (some of this limit is used by Segment). | 512 KiB
 Column JSON size | The maximum size of any single column value. | 128 KiB
+
+## FAQs
+
+#### Why do my sync results show *No records extracted* when I select *Updated records* after I enable the mapping? 
+It's expected that when you select **Updated records** the records do not change after the first sync. During the first sync, the reverse ETL system calculates a snapshot of all the results and creates records in the `_segment_reverse_etl` schema. All the records are considered as *Added records* instead of *Updated records* at this time. The records can only meet the *Updated records* condition when the underlying values change after the first sync completes.
diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup.md
@@ -36,17 +36,22 @@ To set up Databricks as your Reverse ETL source:
 1. Log in to your Databricks account.
 2. Navigate to **Workspaces** and select the workspace you want to use. 
 3. Select **SQL** in the main navigation. 
-4. Select **SQL Warehouses** and select the warehouse you want to use. Note that Segment doesn't support the `Compute` connection parameter.
-5. Go to the **Connection details** tab.
-6. In a new tab on your browser, go to the Segment app. 
+4. Select **SQL Warehouses** and select the warehouse you want to use. Note that Segment doesn't support the `Compute` connection parameters.
+5. Go to the **Connection details** tab and **keep** this page open.
+6. Open [your Segment workspace](https://app.segment.com/workspaces){:target="_blank”}. 
 7. Navigate to **Connections > Sources > Reverse ETL**.
 8. Click **+ Add Reverse ETL source**. 
 9. Select **Databricks** and click **Add Source**. 
-10. Enter the configuration settings for your Databricks source. 
-    * Copy the Hostname, Http Path, and Port from the Databricks console from step 5.
-    * The Http Path in the above step should contain `/sql/1.0/warehouses`. Note that Segment doesn't support `/sql/protocolv1`.
-    * To generate a **Token**, follow the steps listed in the [Databricks docs](https://docs.databricks.com/dev-tools/auth.html#pat){:target="_blank"}. Segment recommends you create a token with no expiration date by leaving the lifetime field empty when creating it. If you already have a token with an expiration date, be sure to keep track of the date and renew it on time.     
+10. Enter the configuration setting for your Databricks source based on information from step 5
+    * Hostname: `adb-xxxxxxx.azuredatabricks.net`
+    * Http Path: `/sql/1.0/warehouses/xxxxxxxxx`
+    * Port: `443` (default)
+    * Token: `<your-token>`
+    * Catalog [optional]: `hive_metastore` (default)
 11. Click **Test Connection** to see if the connection works. If the connection fails, make sure you have the right permissions and credentials, then try again.
 12. Click **Create Source** if the test connection is successful. 
 
-Once you've added your Databricks source, [add a model](/docs/connections/reverse-etl/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. 
+> info ""
+> To generate a token, follow the steps listed in the [Databricks docs](https://docs.databricks.com/dev-tools/auth.html#pat){:target="_blank"}. Segment recommends you create a token with no expiration date by leaving the lifetime field empty when creating it. If you already have a token with an expiration date, be sure to keep track of the date and renew it on time.   
+
+Once you've succesfully added your Databricks source, [add a model](/docs/connections/reverse-etl/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. 
diff --git a/src/connections/sources/catalog/libraries/website/javascript/index.md b/src/connections/sources/catalog/libraries/website/javascript/index.md
@@ -673,7 +673,7 @@ Non-critical plugins run through a timeline that executes in order of insertion
 
 | Type          | Details                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `enrichment`  | Executes as the first level of event processing. These plugins modify an event. <br><br> See the example of how Analytics.js uses the [Page Enrichment plugin](https://github.com/segmentio/analytics-next/blob/master/packages/browser/src/plugins/page-enrichment/index.ts){:target="_blank"} to enrich every event with page information.                                                                                                                                                     |
+| `enrichment`  | Executes as the first level of event processing. These plugins modify an event.                                                                                                                                                      |
 | `destination` | Executes as events begin to pass off to destinations. <br><br> This doesn't modify the event outside of the specific destination, and failure doesn't halt the execution.                                                                                                                                                                                                                                                                                                                        |
 | `after`       | Executes after all event processing completes. You can use this to perform cleanup operations. <br><br>An example of this is the [Segment.io Plugin](https://github.com/segmentio/analytics-next/blob/master/packages/browser/src/plugins/segmentio/index.ts){:target="_blank"} which waits for destinations to succeed or fail so it can send it observability metrics.                                                                                                                         |
 | `utility`     | Executes once during the bootstrap, to give you an outlet to make any modifications as to how Analytics.js works internally. This allows you to augment Analytics.js functionality.                                                                                                                                                                                                                                                                                                              |
