@adobe/acc-js-sdk 1.1.26 → 1.1.27
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/changeLog.html +12 -1
- package/docs/xtkSchema.html +17 -1
- package/package-lock.json +2974 -3
- package/package.json +1 -1
- package/src/application.js +2 -1
- package/src/client.js +48 -9
- package/test/application.test.js +60 -0
- package/test/client.test.js +126 -1
package/docs/changeLog.html
CHANGED
|
@@ -2,7 +2,18 @@
|
|
|
2
2
|
layout: page
|
|
3
3
|
title: Change Log
|
|
4
4
|
---
|
|
5
|
-
|
|
5
|
+
|
|
6
|
+
<section class="changelog"><h1>Version 1.1.27</h1>
|
|
7
|
+
<h2>2023/05/10</h2>
|
|
8
|
+
<li>
|
|
9
|
+
Fixed a unit test which was failing in Node 16 but succeeding on node 14. The reason is that the error message thrown by Node when accessing a property of a null object changed between the 2 versions.
|
|
10
|
+
</li>
|
|
11
|
+
<li>
|
|
12
|
+
The `client.getSchema` and `application.getSchema` functions are now able to return group schemas
|
|
13
|
+
(using the temp:group:{id} format for the schema id). See <a href="https://opensource.adobe.com/acc-js-sdk/xtkSchema.html"></a> for more information.
|
|
14
|
+
</li>
|
|
15
|
+
</section>
|
|
16
|
+
|
|
6
17
|
<section class="changelog"><h1>Version 1.1.26</h1>
|
|
7
18
|
<h2>2023/04/17</h2>
|
|
8
19
|
|
package/docs/xtkSchema.html
CHANGED
|
@@ -36,4 +36,20 @@ var srcSchema = await NLWS.xtkPersist.getEntityIfMoreRecent("xtk:srcSchema|nms:r
|
|
|
36
36
|
console.log(JSON.stringify(srcSchema));
|
|
37
37
|
</pre>
|
|
38
38
|
|
|
39
|
-
|
|
39
|
+
<h1>Group schemas</h1>
|
|
40
|
+
|
|
41
|
+
<p>
|
|
42
|
+
Campaign groups represent marketing lists or audiences. Each group can have it's own specific schema,
|
|
43
|
+
stored in the `extension` XML element of the group entity. This schema can be generated in a workflow by
|
|
44
|
+
using the List Update activity.
|
|
45
|
+
</p>
|
|
46
|
+
<p>
|
|
47
|
+
The schema of a group can be retrieved using the `getSchema` method of the client or application objects.
|
|
48
|
+
</p>
|
|
49
|
+
<p>
|
|
50
|
+
The schema id is build as followed: prefix `temp:group:` + id of the group in mms:group (example `temp:group:1234` )
|
|
51
|
+
</p>
|
|
52
|
+
|
|
53
|
+
<p>Note: group schemas are not cached. The rationale is that they are not accessed as frequently as other,
|
|
54
|
+
regular schemas, but more importantly that they can change more often that regular schemas.
|
|
55
|
+
</p>
|