Skip to content

Commit d5821bc

Browse files
bbringhuGitHub Enterprise
bbringhu
authored and
GitHub Enterprise
committed
Merge pull request #109 from AdobeDocs/v2-prep
V2 prep
2 parents 9e3a851 + f4c365e commit d5821bc

9 files changed

Lines changed: 33 additions & 28 deletions

File tree

‎.github/workflows/validate-articles.yml‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,4 +22,3 @@ jobs:
2222
secrets:
2323
SCCM_GITHUB_APP_ID: ${{ secrets.SCCM_GITHUB_APP_ID }}
2424
SCCM_GITHUB_APP_PRIVATE_KEY: ${{ secrets.SCCM_GITHUB_APP_PRIVATE_KEY }}
25-
SCCM_SLACK_TOKEN: ${{ secrets.SCCM_SLACK_TOKEN }}

‎help/campaign/api/filtering.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -260,7 +260,8 @@ Response to the request.
260260
261261
<!-- exemple à vérifier de bout en bout-->
262262
263-
<!--+category = query editor
263+
<!--
264+
+category = query editor
264265
privacy ?
265266
displayFOrmat ?
266267
pour faire un POST sur une enum, il faut lui passer le @name décrit dans le noeud values, chaque @name a une correspondance en format = au format définit par le resType

‎help/campaign/api/limitations.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -123,10 +123,12 @@ Campaign Standard Workflow GET API returns parameter names such as the workflow
123123

124124
Campaign v8 does not support advertising workflow instance variables, but expects developers to know what those are. As such, post-migration, parameters information in POST request body will need to be constructed without the availability of parameters information in GET API response.
125125

126-
<!--## Transactional messages
126+
<!--
127+
## Transactional messages
127128
128129
* With Campaign Standard, a POST request returns empty fields for elements and attributes in the request body. With Campaign v8, the response returns values that match the ones in the request body instead.
129130
130131
* When publishing an event configuration, the API preview panel displays the REST URL alongside the request body syntax.
131132
132-
Since Campaign v8 does not support event configuration fields definition (event creation is just adding a value to eventType enumeration), there is no API preview panel when adding an event type. The REST URL is displayed in the transactional message user interface once an event transactional message is published.-->
133+
Since Campaign v8 does not support event configuration fields definition (event creation is just adding a value to eventType enumeration), there is no API preview panel when adding an event type. The REST URL is displayed in the transactional message user interface once an event transactional message is published.
134+
-->

‎help/campaign/api/metadata-mechanism.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,8 +31,10 @@ The response returns the main metadata from the resource (all other fields are d
3131
* The **Filters** node returns the URL to retrieve the associated filters. For more on filters, refer to [this section](filtering.md) section.
3232

3333
<!-- créer une section au même niveau sur les liens -->
34-
<!-- dans l'exemple: birthdate, email + mettre 2 liens : un de type 1-1 , 1-N
35-
si on prend l'exemple de l'org unit, on aura un bon exemple lien -->
34+
<!--
35+
dans l'exemple: birthdate, email + mettre 2 liens : un de type 1-1 , 1-N
36+
si on prend l'exemple de l'org unit, on aura un bon exemple lien
37+
-->
3638
<!-- plus reparler du node Data -->
3739

3840
<br/>

‎help/campaign/api/troubleshooting.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,8 @@ Either your token is invalid (improper IMS call used to generate a token) or you
8787

8888
Depending on the instance configuration, the created profile needs to be associated to an **orgUnit**. To understand how to add this field in your creation, consult [this section](creating-profiles-api.md).
8989

90-
<!-- * (error duplicate key : quand tu crées un profile qui existe déjà , il faut faire un patch pour updater le profile plutôt qu'un POST)
90+
<!--
91+
* (error duplicate key : quand tu crées un profile qui existe déjà , il faut faire un patch pour updater le profile plutôt qu'un POST)
9192
9293
With Curl
9394
List all profiles

‎help/campaign/technotes/64-bit-tables.md‎

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -21,21 +21,21 @@ Here is the list of schemas changed to 64 bits and their modified attributes.
2121

2222
| Schema name | Atribute name |
2323
|--- |--- |
24-
| nms:broadLogRcp | id |
25-
| nms:trackingLogRcp | id |
26-
| nms:excludeLogRcp | id |
27-
| nms:broadLogVisitor | id |
28-
| nms:trackingLogVisitor | id |
29-
| nms:propositionRcp | interactionId |
30-
| nms:propositionVisitor | interactionId |
31-
| nms:webTrackingLog | id |
32-
| nms:tmpBroadcast | message-id |
33-
| nms:tmpMarketingPressure | message-id |
34-
| nms:tmpBroadcastExclusion | message-id |
35-
| nms:tmpBroadcastPaper | message-id |
36-
| nms:broadLogAppSubRcp | id |
37-
| nms:trackingLogAppSubRcp | id |
38-
| nms:excludeLogAppSubRcp | id |
39-
| nms:webEvent | broadLogSrc-id, broadLogRemkt-id |
40-
| nms:broadLogMid | mktBroadLogId |
24+
| nms:broadLogRcp | id |
25+
| nms:trackingLogRcp | id |
26+
| nms:excludeLogRcp | id |
27+
| nms:broadLogVisitor | id |
28+
| nms:trackingLogVisitor | id |
29+
| nms:propositionRcp | interactionId |
30+
| nms:propositionVisitor | interactionId |
31+
| nms:webTrackingLog | id |
32+
| nms:tmpBroadcast | message-id |
33+
| nms:tmpMarketingPressure | message-id |
34+
| nms:tmpBroadcastExclusion | message-id |
35+
| nms:tmpBroadcastPaper | message-id |
36+
| nms:broadLogAppSubRcp | id |
37+
| nms:trackingLogAppSubRcp | id |
38+
| nms:excludeLogAppSubRcp | id |
39+
| nms:webEvent | broadLogSrc-id, broadLogRemkt-id |
40+
| nms:broadLogMid | mktBroadLogId |
4141
| nms:mirrorPageSearch | remoteMessageId |

‎help/experience-rollouts/guides/feature-flags/request-a-release.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,12 @@ exl-id: 8eee84b2-fbd5-4713-90ac-92fd7b74c163
77

88
## Prerequisites {#prerequisites}
99

10-
* You have the **Release Manager** role — see [User roles](../teams/user-roles.md)
10+
* You have the **Release Manager** role — see <!-- broken link[User roles](../teams/user-roles.md) -->
1111
* Your application is onboarded — see [Onboard your application](../applications/onboard-your-application.md)
1212

1313
>[!TIP]
1414
>
15-
>Before requesting a release, review [Releases and cross-team feature groups](releases-and-cross-team-feature-groups.md). A cross-team feature group may meet your needs with less overhead — it is self-serve and supports richer audience targeting.
15+
>Before requesting a release, review <!--[Releases and cross-team feature groups](releases-and-cross-team-feature-groups.md)-->. A cross-team feature group may meet your needs with less overhead — it is self-serve and supports richer audience targeting.
1616
1717
## Submit a support request {#submit}
1818

‎help/software-distribution/TOC.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
user-guide-title: Experience Cloud Software Distribution
3-
index: y
3+
index: true
44
---
55

66
# Experience Cloud Software Distribution {#software-distribution}

‎metadata.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ solution: Experience Cloud
44
feature-set: Experience Cloud Services
55
type: Documentation
66
git-repo: https://github.com/AdobeDocs/experience-cloud.en
7-
index: yes
7+
index: true
88
mini-toc-levels: 2
99
product: experience cloud
1010
---

0 commit comments

Comments
 (0)