Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize setup docs #103

Closed
wants to merge 529 commits into from
Closed

Optimize setup docs #103

wants to merge 529 commits into from

Conversation

dsoffiantini
Copy link
Contributor

Description

Adds documentation about the assurance optimize setup view

@dsoffiantini dsoffiantini changed the base branch from main to staging October 25, 2022 21:49
Copy link
Contributor

@calebk1 calebk1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some small fixes!

Comment on lines 11 to 12
1. [Set up Assurance](../set-up-project-griffon.md)
2. [Create](./README.md#creating-sessions) and [connect](./README.md#connecting-to-a-session) to a Assurance session
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment here - we need to update these links to the proper links within this repo.

So I think it's set-up.md for Set up Assurance, and index.md instead of README.md.


## Datastream Setup Validation

At the top of the Optimize Setup Validation view, Assurance inspects your current app's datastream, and looks to see if Target or Offer Decisioning has been enabled. In order to use optimize, at least one of extensions needs to be enabled inside your datastream.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is a first mention, this should be "... Platform Assurance inspects your current app's..."


## SDK Setup Validation

Below the datastream validation section, the SDK Setup Validation section offers feedback on two major issues you could face in your application. First it offers validation that you have installed all the required SDKs Optimize requires in order to work correctly. Second, it validates that request and response events are flowing from your application in the way the platform expects them to. Errors may arise if your schemas have been improperly implemented, or your app may be sending requests that do not receive an appropriate response. In these cases, this section will give feedback about what is going wrong, and identify the events in error so that you can diagnose what went wrong.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Firstly, it offers validation that you have..."
"Secondly, it validates that the request and response events are..."

@dsoffiantini dsoffiantini force-pushed the optimize-setup-docs branch 2 times, most recently from 50d859a to 5f3c6ef Compare October 26, 2022 17:31
Copy link
Contributor

@calebk1 calebk1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few more minor comments!

gatsby-config.js Outdated
@@ -698,6 +698,10 @@ module.exports = {
title: "Custom validation",
path: "/documentation/platform-assurance/tutorials/custom-validation.md"
},
{
title: "Optimize Setup",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To match with the other ones, this should be "Optimize setup".

(I believe it's sentence-casing, rather than title-casing for documentation, unfortunately.)

To use this view, complete the following steps:

1. [Set up Adobe Experience Platform Assurance](../set-up.md)
2. [Create](./index.md#creating-sessions) and [connect](./index.md#connecting-to-a-session) to a Assurance session
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"... to an Assurance session".

@@ -0,0 +1,35 @@
# Optimize Setup Validation View
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lowercase v for view, because of sentence casing.

@emdobrin
Copy link
Contributor

@hbhandal80 @sbenedicadb can you help with a review on this PR?

Copy link
Collaborator

@hbhandal80 hbhandal80 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comments left, please make updates.


## Overview

You may use the Optimize Setup Validation view in order to quickly see if your app has been successfully set up to use AEP Optimize. The view validates all pre-requisites have been met, and offers feedback on how to fix your setup in cases where requirements have been missed.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would reword the first sentence: "You can use the Optimize Setup Validation view to check if your application has been set up successfully to use Adobe Experience Platform Optimize."


## Getting Started

To use this view, complete the following steps:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest amending this to - "To use this view, follow the steps outlined below:"


## Datastream Setup Validation

At the top of the Optimize Setup Validation view, Platform Assurance inspects your current app's datastream, and looks to see if Target or Offer Decisioning has been enabled. In order to use optimize, at least one of extensions needs to be enabled inside your datastream.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest amending the first sentence slightly: "....your current application's datastream to see if Target or Offer Decisioning has been enabled.


![Validate Datastream Section](./assets/optimize-configuration/datastream-validation.png)

To enable Target in your datastream, go to the datastream view for your app inside the Data Collection UI, and ensure that Adobe Target has been added and enabled.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

change "app" to "application".


![Enable Target Datastream](./assets/optimize-configuration/enable-target-datastream.png)

To enable Offer Decisioning in your datastream, go to the datastream view for your app inside the Data Collection UI, and then select Edit inside the actions menu for Adobe Experience Platform. Inside, you will see a checkbox that shows whether Offer Decisioning has been enabled.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest rewording this section: "To enable Offer Decisioning in your datastream, go to datastream view for your application in the Data Collection UI, and select Edit in the actions menu for Adobe Experience Platform. The toggle shows if Offer Decisioning is enabled."


## SDK Setup Validation

Below the datastream validation section, the SDK Setup Validation section offers feedback on two major issues you could face in your application. Firstly, it offers validation that you have installed all the required SDKs Optimize requires in order to work correctly. Secondly, it validates that the request and response events are are flowing from your application in the way the platform expects them to. Errors may arise if your schemas have been improperly implemented, or your app may be sending requests that do not receive an appropriate response. In these cases, this section will give feedback about what is going wrong, and identify the events in error so that you can diagnose what went wrong.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest rewording: "Firstly, it offers validation that all SDKs have been installed that are required by Optimize to work correctly."

Remove "are" appears twice: "....events are flowing from...."

Suggest updating to - "Errors may arise if your schemas have been improperly implemented, or your application is sending requests that do not receive an appropriate response. This section will provide feedback and identify the events in error, so you can diagnose what went wrong."

@dsoffiantini
Copy link
Contributor Author

@hbhandal80 sorry I missed your comments earlier and forgot about this one, should be updated with your feedback!

calebk1 and others added 12 commits August 25, 2023 10:41
…gatsby-theme-aio-4.10.5

Bump @adobe/gatsby-theme-aio from 4.10.4 to 4.10.5
* Create release-pr.yml

* no message

* Update update-release-notes.js

* Update release-pr.yml

* no message

* Update release-pr.yml

* Update release-pr.yml

* clean up BOM scripts

* add the license header

* cleanup

* Update update-release-notes.js

* address review comments

* address review comments

* merge BOM release notes to the existing section when the release date exists
* places ios 4.1.0 and android 2.1.0 release notes

* Places release doc updates

* fix link

---------

Co-authored-by: Pravin Prakash Kumar <pprakash@Pravins-MBP.attlocal.net>
Co-authored-by: Pravin Prakash Kumar <pprakash@Pravins-MacBook-Pro.local>
Co-authored-by: Emilia Dobrin <33132425+emdobrin@users.noreply.github.com>
* Update release notes for Core 4.1.0 and 2.4.0

* minor fix

* Fix style
calebk1 and others added 27 commits January 22, 2024 13:10
MOB-20134 - Command overrides: migrate from datastreams docs to mobile SDK docs
…gatsby-theme-aio-4.11.0

Bump @adobe/gatsby-theme-aio from 4.10.7 to 4.11.0
MOB-20239 - Small typo and 404 link: streaming media for edge - READY
* Updating release notes

* remove beta version from the release notes

---------

Co-authored-by: yangyansong-adbe <yangyansong-adbe@users.noreply.github.com>
Co-authored-by: yansong <yanyang@adobe.com>
Bumps [@adobe/gatsby-theme-aio](https://github.com/adobe/aio-theme) from 4.11.0 to 4.11.2.
- [Release notes](https://github.com/adobe/aio-theme/releases)
- [Commits](https://github.com/adobe/aio-theme/compare/@adobe/gatsby-theme-aio@4.11.0...@adobe/gatsby-theme-aio@4.11.2)

---
updated-dependencies:
- dependency-name: "@adobe/gatsby-theme-aio"
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…gatsby-theme-aio-4.11.2

Bump @adobe/gatsby-theme-aio from 4.11.0 to 4.11.2
Bumps [@adobe/gatsby-theme-aio](https://github.com/adobe/aio-theme) from 4.11.2 to 4.11.3.
- [Release notes](https://github.com/adobe/aio-theme/releases)
- [Commits](https://github.com/adobe/aio-theme/compare/@adobe/gatsby-theme-aio@4.11.2...@adobe/gatsby-theme-aio@4.11.3)

---
updated-dependencies:
- dependency-name: "@adobe/gatsby-theme-aio"
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…gatsby-theme-aio-4.11.3

Bump @adobe/gatsby-theme-aio from 4.11.2 to 4.11.3
* Updating release notes

* rename the release name for React Native wrappers

---------

Co-authored-by: yangyansong-adbe <yangyansong-adbe@users.noreply.github.com>
Co-authored-by: yansong <yanyang@adobe.com>
* Updated release notes for Target iOS and Android releases

* Fixed lint issues

* Incorporated feedback
Co-authored-by: yangyansong-adbe <yangyansong-adbe@users.noreply.github.com>
Co-authored-by: yangyansong-adbe <yangyansong-adbe@users.noreply.github.com>
Co-authored-by: yangyansong-adbe <yangyansong-adbe@users.noreply.github.com>
Co-authored-by: praveek <praveek@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.