Get package content

RE: Get package content

Luis Ripoll Morales — Thu, 27 Apr 2023 16:35:26 GMT

Thank you all.

Once I've realized that, at this moment, ther is no way to retrieve packages content programmatically, I've done something on MS Excel based upon Export log file you can get manually when you are exporting a package. These export log files includes package content and they can be easily imported to an Excel sheet.

So, I import on the same excel sheet every package I have on going, and can compare the contents before deployment.

That wasn't my first idea, but it meets my goal.

Thanks again, I appreciate the time you get to answer me.

Regards

RE: Get package content

Rómulo — Wed, 26 Apr 2023 13:27:24 GMT

Hi Jesus,

This is a post deployment operation. It looks like the use case Luis is looking for is before that (avoid summit unnecessary objects).

However, could be interesting for Luis using the function a!toDeployment() after reviewing them.

Cheers,

Rómulo

RE: Get package content

Jesús Hormigos — Wed, 26 Apr 2023 13:10:40 GMT

This would be a way to obtain that:

1- Obtain the zip document using a!deployment(<UUID>,"objectsPackageId")

2- Go to content folder

3- Every xml file is an object contained in the package, so you can iterate using getcontentdetailsbyuuid(<NAME_DOC>)

Best

RE: Get package content

Rómulo — Tue, 25 Apr 2023 15:03:23 GMT

Hi Luis Ripoll Morales,

Assuming that your idea it is possible (which unfortunately is not at this moment, there's not native way to retrieve package contents programmatically) probably you will encounter problems comparing packages, mainly because you could have the same object in different package throughout the history (if you dont delete them). A date filter it helps likely; however, could be not accurate enough. I propose you consider these options:

Option 1 - App Read File Fuctions
Detail: Create an application that allows upload the packages exported files (patches, or content / processModel folder) and can read it using fuctions like xpathdocument(), readtextfromfile(). Then, you can compare it and decide about it.
Pros: You can compare between several packages + Easy to build + You can leverage design-guidance.json file to expand the recommendations/info that you show to the developers.
Cons: Manually upload the package.

Option 2 - Design and Integrate a Jenkins pipeline
Detail: Design a DevOps model (using Jenkins for example) where you can use the steps to evalute conditions. In your case, evaluate if the objetcs you are upgrading are already deployed.
Pros: More flexible and strong DevOps pipeline.
Cons: External technology + no basic implementation

Option 3 - Enable Government DepOps
Detail: Go to Admin Console / DevOps / Infrastructure and enable requiere review (create a group DevOps first).
Pros: Easiest implementation + User Notification
Cons: You have to compare manually the packages.

Hope it helps,

Rómulo

RE: Get package content

tushark6475 — Tue, 25 Apr 2023 11:17:19 GMT

AFAIK, there is no way to keep track of unnecessary deployed items in the upper environment. And if you are looking to create another application to keep track of ongoing packages, then this will be more complex to keep both applications synced as there is no way to easily reflect changes from one application to another.
If in case of unwanted deployed packages, just deploy the package with the right objects and the changes will be reflected on the higher environment.

RE: Get package content

vigneshkumarr — Tue, 25 Apr 2023 10:43:43 GMT

Hi Luis,

two or more of them include same interface, rule or any other kind of appian object. -> In this case you can use version history to avoid this type of issues.
This application act as a ongoing package inventory and should be able to compare contents of each packages in order to warn about objects that were part of more than one package. -> In this case you can use Inspect button at the time of package deployment before using of Import button directly.

Thanks and Regards,

Vigneshkumar Radhakrishnan