Backing up pages before updating them during a package deployment is an advisable practice. You can always use the backup to restore your pages if anything goes wrong (you never know).
But the list of paths for package creation is usually long, and manual package creation with such a list becomes tedious and time-consuming for content authors.
Create an AEM package from paths (filters) present in an Excel file.
Argil DX presents a tool with a user-friendly console to help users create AEM packages in a simpler and quicker manner through the following input fields:
Name – name of the package
Version – version of the package
Group – group of the package
Access Control Handling – permissions to handle the nodes
Excel file – file containing fields such as Path, Include child node, Include Image Renditions
All of the fields have default values except the Excel file.
A sample Excel file can be downloaded using the ‘Sample’ button present after the description of the file field.
The Excel file contains 3 fields:
Path – the absolute path of the node
Include Child Node (Yes/No) – asking for tree activation on the specified path
Include DAM Renditions (if applicable) (Yes/No) – AEM workflows automatically create DAM renditions on every server (unless altered), but users can opt not to include them by entering ‘No’ in this field.
The tool also has a history page with a record of all the packages created using it. We can see the logs of operations as well as download the old package.
The history icon is present on the top right corner of the tool.
Advantages of the tool:
Easy-to-use console for package creation
Packages and their respective logs are accessible from remote locations
Create space-saver packages by eliminating renditions of assets
Easy searching and sorting in logs
History page for package creation
The video demonstration of the tool can be viewed below: