Skip to content

Commit 9c84eb9

Browse files
authored
Merge branch 'v1.0' into W-11826600-EOL-Consolidate-and-deprecate-PM-latest-hn
2 parents 7518764 + 84bca55 commit 9c84eb9

5 files changed

Lines changed: 3 additions & 8 deletions

File tree

modules/ROOT/pages/_partials/promotion-scenarios.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Checkbox
2525
.2+.^|*P1~E1~* has previously been promoted to *P1~E2~*
2626
|Selected
2727
|Either selected or not selected
28-
|If *P1~E1~* contains any new cerfificates, they will be copied to *P1~E2~*
28+
|If *P1~E1~* contains any new certificates, they will be copied to *P1~E2~*
2929

3030
|Not Selected
3131
|Either selected or not selected

modules/ROOT/pages/apm-tutorial-td.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -431,7 +431,7 @@ In order to identify your APM environment and its API Key to Anypoint Studio:
431431

432432
=== Identify or Create an API Key
433433

434-
In order to create a Mule project, you must enter an xref:glossary.adoc#secta[API Key] and an .
434+
In order to create a Mule project, you must enter an xref:glossary.adoc#secta[API Key].
435435

436436
If you have an existing API Key, use it. If you do not know the API Key, consult your organization's MuleSoft administrator.
437437

modules/ROOT/pages/examples.adoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,6 @@ Go to the B2B Transmissions area of APM to view tracked events and messages.
3939
// Promotion Scenarios
4040
include::{partialsdir}/promotion-scenarios.adoc[leveloffset=+1]
4141

42-
////
4342
=== Rough draft graphic for certs promo
4443

4544
removed image PromoteIDsOffCertsOn kris 7/1/2017

modules/ROOT/pages/transaction-tracking-walkthrough.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ image::transmission-tracking-walk-5.png[]
9090
|===
9191
|*Field* |*Value*
9292
|From-party identifier|`#[xpath3(''/PurchaseOrder/Address/Name'')`]
93-
|To-party identifier|`My Organisation`
93+
|To-party identifier|`My Organization`
9494
|Content Reference (Set only if you have configured the File Storage type on the Partner Manager Connector config)|`#[payload]`
9595
|Filename|`#[flowVars.originalFilename]`
9696
|Format Type|`XML`

modules/ROOT/pages/working-with-environments.adoc

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,6 @@ include::partial$promotion-scenarios.adoc[leveloffset=+1]
1313

1414
image::promoteidsoffcertson.png["rough draft graphic,cert promotion scenario"]
1515

16-
////
17-
</New Text
18-
1916

2017

2118

@@ -56,7 +53,6 @@ Only users with the appropriate role or permissions will be able to promote part
5653
. Select the "target environment", this is the environment into which the partners will be promoted. Hit "Next" to go to the next step. Alternatively, you can hit "Back" to change the selected target environment, if needed.
5754
. Select whether the partners being promoted will keep their identifiers when matching existing or previously imported partners on the target environment.
5855
. Select whether the partners being imported will keep their AS2 certificates or use the certificates from the matching existing, or previously promoted partners on the target environment. Hit import to start the process.
59-
////
6056
6157
== Promotion Scenarios
6258
Promotion of partners is a more complex procedure than import.

0 commit comments

Comments
 (0)