apn-app-manager 0.2.6 → 0.2.7
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/README.md +4 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -8,11 +8,11 @@ When app building you may want to do things in bulk that are easiest to do via a
|
|
|
8
8
|
|
|
9
9
|
## Disclaimer
|
|
10
10
|
|
|
11
|
-
The functionality provided by this tool is not supported nor endorsed by Appian. It is merely a tool to manipulate XML files following strict rules. The structure of these XML files
|
|
11
|
+
The functionality provided by this tool is not supported, nor endorsed by Appian. It is merely a community tool to manipulate XML files following strict rules. The structure of these XML files may change between Appian platform releases, and those changes may break this tool.
|
|
12
12
|
|
|
13
13
|
Importing an application export modified by this tool should be done at your own discretion.
|
|
14
14
|
|
|
15
|
-
Latest compatible Appian platform version
|
|
15
|
+
Latest compatible Appian platform version tested against: **22.3**.
|
|
16
16
|
|
|
17
17
|
## Installation
|
|
18
18
|
|
|
@@ -49,10 +49,10 @@ Used to duplicate all objects of an application, which replaces the namespace of
|
|
|
49
49
|
1. Always inspect your cloned zip before importing to verify that what will be imported matches what you'd expect.
|
|
50
50
|
1. The cloning tool is idempotent meaning it will always return the same output zip run against the same input. This also means you can develop an application, clone it, then enhance the original application, re-clone it, and that second clone will deploy over the first clone with objects being recognized as "Changed" as if you had just modified the clone directly.
|
|
51
51
|
1. It is highly recommended that all objects in your application have the same prefix (including objects that generally aren't prefixed such as applications, groups, process models, etc). Otherwise, the cloning tool will not be able to generate a unique name for these objects, and certain objects are required to have unique names.
|
|
52
|
-
1. Import properties files and SQL files for your application are not supported at this time. These will have to be adjusted manually to align with the cloned objects.
|
|
52
|
+
1. Import properties files and SQL files for your application are not supported for cloning at this time. These artifacts will have to be adjusted manually to align with the cloned objects (i.e. swapping UUID or name references).
|
|
53
53
|
1. There are two other document generated in the `/out/` folder after cloning:
|
|
54
54
|
- `objects.json` - This contains every attribute of collected metadata from every object in the package, including its current value and new value.
|
|
55
|
-
- `not-cloned-uuids.json` - Warnings may appear during cloning about UUIDs in the package that the tool didn't know how to handle, which will be listed in this file. If no warnings appeared, this file will be empty. Generally these can be ignored if your inspection looks good, however these may be actual issues that come up due to XML structure changes in future releases. Please reach out to the authors of this tool if you have any questions about this.
|
|
55
|
+
- `not-cloned-uuids.json` - Warnings may appear during cloning about UUIDs in the package that the tool didn't know how to handle, which will be listed in this file. If no warnings appeared, this file will be empty. Generally these can be ignored if your inspection looks good, however these may be actual issues that come up due to XML structure changes in future Appian platform releases. Please reach out to the authors of this tool if you have any questions about this.
|
|
56
56
|
|
|
57
57
|
## License
|
|
58
58
|
|