Merge branch 'main' into PLAT-234038/add-use-case-in-data-mgmt-guide

Author: Carlo Javier

.github/exl-admin.yml

@@ -0,0 +1,3 @@
+version: 1
+type: article
+metadata:

.github/workflows/validate-articles.yml

@@ -0,0 +1,25 @@
+name: validate article
+on:
+  pull_request:
+    branches:
+      - main
+  push:
+    branches:
+      - main
+  issue_comment:
+    types: [created]
+  workflow_dispatch:
+
+jobs:
+  validate-articles:
+    # Only run if it's not a comment trigger, or if it's a retest comment on a PR
+    if: |
+      github.event_name != 'issue_comment' ||
+      (github.event.issue.pull_request && contains(github.event.comment.body, 'retest'))
+    uses: Adobe-Enterprise-Docs/workflows/.github/workflows/validate-articles.yml@main
+    with:
+      debug: true
+    secrets:
+      SCCM_GITHUB_APP_ID: ${{ secrets.SCCM_GITHUB_APP_ID }}
+      SCCM_GITHUB_APP_PRIVATE_KEY: ${{ secrets.SCCM_GITHUB_APP_PRIVATE_KEY }}
+      SCCM_SLACK_TOKEN: ${{ secrets.SCCM_SLACK_TOKEN }}

help/access-control/abac/apply-access-labels-destinations.md

@@ -67,11 +67,12 @@ You can add standard and custom labels to destination dataflows. After you add a
 
 ## Important callouts and items to know {#important-callouts}
 
-Currently, access labels can only be applied to existing dataflows. This means that you need to create a dataflow to a destination before you can apply access labels.
+* Currently, access labels can only be applied to existing dataflows. This means that you need to create a dataflow to a destination before you can apply access labels.
+* You cannot apply an access label to a destination dataflow if you do not have access to that label.
+* When adding multiple labels to a destination dataflow, users who should be able to view and edit the dataflow must be added to a role with at least the same combination of labels. For example, if you apply the labels C1, I2, and another custom label to a destination dataflow, only users added to roles with access to the combination of these three labels are able to view and edit this specific destination dataflow.
+* Destination dataflows that a user does not have access to due to access label configurations may appear in the UI in a greyed-out state; users cannot perform any actions on those dataflows.
 
-You cannot apply an access label to a destination dataflow if you do not have access to that label.
-
-When adding multiple labels to a destination dataflow, users who should be able to view and edit the dataflow must be added to a role with at least the same combination of labels. For example, if you apply the labels C1, I2, and another custom label to a destination dataflow, only users added to roles with access to the combination of these three labels are able to view and edit this specific destination dataflow.
+![The destinations browse catalog with the actions window greyed out.](../images/olac/destinations-greyed-edit.png)
 
 >[!NOTE]
 >

help/access-control/images/olac/destinations-greyed-edit.png

@@ -15,6 +15,7 @@ role: Admin,User,Developer,Leader
 * [AI Assistant UI guide](ui-guide.md)
 * [Privacy, Security, and Governance](privacy.md)
 * [FAQ](faq.md)
+* [Legal disclaimer](legal-disclaimer.md)
 * New features {#new-features}
   * [AI Assistant capabilities in Alpha and Beta](./new-features/alpha-beta.md)
   * [Monitor significant changes and forecast audiences](./new-features/audience-forecasting.md)

help/ai-assistant/TOC.md

@@ -0,0 +1,22 @@
+---
+title: Legal Disclaimer - Personal Data, Language Support, and Verifying Responses
+description: Learn about legal disclaimers regarding personal data, language support, and verifying responses when using AI Assistant.
+exl-id: 1a3c698e-49eb-4a3b-8e1d-4da909581d57
+---
+# Legal Disclaimer: Personal Data, Language Support, and Verifying Responses
+
+Read this document for information on legal disclaimers regarding personal data, language support, and verifying responses when using the Adobe Experience Platform AI Assistant.
+
+## Personal Data {#personal-data}
+
+AI Assistant uses an automated chatbot. Your use of this automated chatbot constitutes consent that the information you provide in the chat session will be collected, used, disclosed, and retained by Adobe and service providers acting on Adobe's behalf in accordance with the terms of the agreement between your organization and Adobe.
+
+If you need to include personal data here, only add what's necessary and only if you have the right to use it.
+
+## Language Support {#language-support}
+
+AI Assistant is currently supported in English only. Non-English inputs may produce inconsistent or erroneous results. Issues arising from non-English responses won't be addressed or improved at the present time.
+
+## Verifying Responses {#verifying-responses}
+
+It is important to check your answers, as language models can make mistakes. Always verify the sources to ensure that SQL logic is correct and that the appropriate documentation was referenced for your use case. Review the reasoning steps and explanations provided by AI Assistant to understand how it arrived at its answer. If something does not look right, please submit feedback.

help/ai-assistant/legal-disclaimer.md

@@ -22,6 +22,10 @@ You can set up retention policies on datasets created using the ExperienceEvent
 
 +++Answer
 
+>[!NOTE]
+>
+>The retention period for Profile Service can only be updated once every 30 days.
+
 Yes, you can apply different retention policies for the data lake and Profile Service.
 
 +++

help/catalog/catalog-faq.md

@@ -327,7 +327,13 @@ For example, if you apply a 30-day expiration policy on May 15th, the following
 ### Can I set different retention policies for data lake and Profile services?
 
 +++Answer
+
+>[!NOTE]
+>
+>The retention period for Profile Service can only be updated once every 30 days.
+
 Yes, you can set different retention policies for data lake and Profile services. The retention period for the Profile store can be shorter or longer than the data lake retention period, depending on your organization's needs.
+
 +++
 
 ### How can I check my current dataset usage?

help/catalog/datasets/experience-event-dataset-retention-ttl-guide.md

@@ -50,8 +50,8 @@ This user guide requires a working understanding of the following components of
 
 >[!CONTEXTUALHELP]
 >id="platform_datasets_orchestratedCampaigns_toggle"
->title="Orchestrated Campaigns"
->abstract="Enable this toggle to allow the selected dataset to be used in Adobe Journey Optimizer Orchestrated Campaigns. The dataset must use a relational schema and only one dataset can be created per schema."
+>title="Orchestrated campaigns"
+>abstract="Enable this toggle to allow the selected dataset to be used in Adobe Journey Optimizer Orchestrated campaigns. The dataset must use a relational schema and only one dataset can be created per schema."
 
 In the [!DNL Experience Platform] UI, select **[!UICONTROL Datasets]** in the left-navigation to open the **[!UICONTROL Datasets]** dashboard. The dashboard lists all available datasets for your organization. Details are displayed for each listed dataset, including its name, the schema the dataset adheres to, and the status of the most recent ingestion run.
 
@@ -102,25 +102,26 @@ More information on these available actions can be found in their respective sec
 
 ### Preview a dataset {#preview}
 
-You can preview dataset sample data from both the inline options of the [!UICONTROL Browse] tab and also the [!UICONTROL Dataset activity] view. A new dataset preview window is available with additional navigation and context enhancements.
+You can preview up to 100 rows of sample data for any dataset, either from the inline options in the [!UICONTROL Browse] tab or from the [!UICONTROL Dataset activity] view.
 
-From the [!UICONTROL Browse] tab, select the ellipsis (...) next to the dataset name you want to preview. A list of options appears. Next, select [!UICONTROL Preview dataset] from the available options. If the dataset is empty, the preview link is deactivated and indicates that the preview is not available.
+From the [!UICONTROL Browse] tab, select the ellipsis (...) next to the dataset name and choose [!UICONTROL Preview dataset]. If the dataset is empty, the preview option is deactivated. Alternatively, from the **[!UICONTROL Dataset activity]** screen, select **[!UICONTROL Preview dataset]** near the top-right corner of your screen.
 
 ![The Browse tab of the Datasets workspace with the ellipsis and Preview dataset option highlighted for the chosen dataset.](../images/datasets/user-guide/preview-dataset-option.png)
 
-This opens the preview window, where the hierarchical schema view for the dataset is shown on the left.
+This opens the preview window, where the hierarchical schema view for the dataset appears on the left.
 
 >[!NOTE]
 >
->The schema diagram on the left side of the view only displays fields that contain data. Fields without data are automatically hidden to streamline the UI and focus on relevant information.
+>The schema diagram on the left only displays fields that contain data. Fields without data are automatically hidden to streamline the UI and focus on relevant information.
 
 ![The dataset preview dialog with information about the structure, as well as sample values, for the dataset are shown.](../images/datasets/user-guide/preview-dataset.png)
 
-Alternatively, from the **[!UICONTROL Dataset activity]** screen, select **[!UICONTROL Preview dataset]** near the top-right corner of your screen to preview up to 100 rows of data.
+Alternatively, from the **[!UICONTROL Dataset activity]** screen, select **[!UICONTROL Preview dataset]** to open the preview window and review a sample of your dataset's structure and values.
 
 ![The Preview dataset button is highlighted.](../images/datasets/user-guide/select-preview.png)
 
-The dataset preview window provides a streamlined interface for exploring and validating datasets.
+The dataset preview window provides a quick way to explore and validate your dataset's structure and data.
+
 
 #### Dataset preview window {#dataset-preview-window}
 
@@ -131,34 +132,25 @@ The following animation shows the dataset preview window with its navigation and
 The dataset preview window includes:
 
 * An object browser sidebar on the left for navigating and filtering dataset fields.
-* Data type indicators displayed next to each column name for quick insight into the structure of the dataset.
+* Data type indicators next to each column name for insight into the structure of the dataset.
 * A SQL query display at the top of the window, showing the query used to generate the dataset.
-* A formatted table view of up to 100 rows in the lower right area for efficient data review.
-* Direct navigation to Query Editor for Data Distiller users, with the SQL query prepopulated for further exploration or modification.
-
-These features support fast navigation, schema understanding, and transparent dataset validation.
+* A formatted table view of up to 100 rows for efficient data review.
 
-Select **[!UICONTROL Preview dataset]** from the inline actions or from the [!UICONTROL Dataset activity] screen to open the preview window.
-
->[!NOTE]
->
->The preview window displays a sample of up to 100 rows. Fields without data are excluded from the view.
+These features help you navigate, understand schema details, and validate sample data efficiently.
 
 #### Advanced Query Editor shortcut {#query-editor-shortcut}
 
-If your organization has a Data Distiller license, you can access the Advanced Query Editor directly from the dataset preview window.
+If your organization has a Data Distiller license, you can access the [!UICONTROL Advanced Query Editor] directly from the dataset preview window. Use this shortcut to move seamlessly from previewing sample data to running and refining queries in Query Service.
 
 >[!AVAILABILITY]
 >
->Only users with the required Data Distiller license can access this functionality. If your organization does not have Data Distiller, the [!UICONTROL Advanced query editor] option is not visible.
-
-Select **[!UICONTROL Advanced query editor]** in the upper right of the preview window to open the Query Editor. The current preview query is preloaded and ready for execution or further analysis.
+>Access to the [!UICONTROL Advanced Query Editor] is limited to organizations with a Data Distiller SKU license. If your organization does not have the required license, this option does not appear in the dataset preview window.
 
-![Dataset preview window showing the Advanced query editor button in the upper right.](../images/datasets/user-guide/dataset-preview-advanced-query-editor.png)
+Select [!UICONTROL Advanced Query Editor] in the upper right of the preview window to open Query Service with your current SQL query pre-loaded and executed. You can continue analyzing or modify the SQL without re-entering the query.
 
-This shortcut enables you to move seamlessly from previewing sample data to running and refining queries in Query Service without re-entering SQL or context.
+![Dataset preview window showing the Advanced Query Editor button in the upper right.](../images/datasets/user-guide/dataset-preview-advanced-query-editor.png)
 
-For additional data access and analysis, use downstream services such as [!DNL Query Service] and [!DNL JupyterLab]. See the following documents for more information:
+For additional analysis, use downstream services such as [!DNL Query Service] and [!DNL JupyterLab]. See the following documents for more information:
 
 * [Query Service overview](../../query-service/home.md)
 * [JupyterLab user guide](../../data-science-workspace/jupyterlab/overview.md)
@@ -239,6 +231,8 @@ Configure your preferred retention period in the data retention settings dialog.
 >[!NOTE] 
 > 
 >The minimum retention period for the data lake is 30 days. The minimum retention period for Profile Service is one day.
+>
+>Additionally, you can only update the retention period for Profile Service once every 30 days.
 
 To support transparency and monitoring, timestamps are provided for the **last** and **next** data retention job executions. The timestamps help you understand when the last data cleanup occurred and when the next one is scheduled.