The Bulk Editor allows for very efficient editing when the visual page context is not needed as it lets you:
You can also import content into the repository, but by default this is disabled for the Bulk Editor as available in the Tools console.
This section describes how to work with the bulk editor in the Tools console. Typically, administrators use the bulk editor to search and edit multiple items. This is done by populating the table using a GQL query and then by selecting the content items to work on. Authors generally use the bulk editor as part of a customized bulk editor application accessible through the product listing component.
With the deprecation of the Classic UI in AEM 6.4, the Bulk Editor has also been deprecated and thus Adobe does not plan to further enhance the Bulk Editor.
For example, if you need all the names and email addresses of users who filled out a particular survey, the Bulk Editor can provide that information and you can export it into a spreadsheet.
An example to illustrate such a use case is included in the Geometrixx web site:
Navigate to the Support page and then to the Customer Service Satisfaction survey.
Edit the Start of Form paragraph. In the dialog click the Advanced tab, expand the Action Configuration, then click View Data….
The Bulk Editor is fully customizable., though in this example the bulk editor does not allow users to edit the content, but only lets them export the information to a spreadsheet.
The bulk editor allows you to:
To use the bulk editor to edit multiple items simultaneously:
|Root Path||Indicates the root path the bulk editor searches.
|Query Parameters||Using GQL parameters, enter the search string you want the bulk editor to look for in the repository; for example,
|Content Mode check box||Select this check box to read properties within the
|Properties/Columns||Select the check boxes for the properties that you want the bulk editor to return. The properties you select are the column heads in the results pane. By default, the node path is displayed in the results.|
|Custom Properties/Columns||Enter any other properties that are not listed in the Properties/Columns field. These custom properties appear in the results pane. You can add multiple properties by using a comma to separate properties. Note: If you add a custom property that does not yet exist, AEM WCM displays an empty cell. When you modify the empty cell and save it, the property is added to the node. The newly created property must respect node type constraints and property namespaces.|
Click Search. The Bulk Editor displays the results.
For the example above, all the pages that meet your search criteria are returned and displayed with the requested columns.
Make any changes you need by double-clicking in a cell.
Click Save to save your changes (the Save button will be activated once you have edited a cell).
The changes you make here are written to the repository content; for example, the page referenced in Path.
You may need to export content and make changes to it in an Excel spreadsheet. For example, you may want to export a mailing list and change the area code of all the listed phone numbers directly in Excel, add additional lines, and so on.
To export content:
Search for content as described in Searching and Editing Content.
Click Export to export the changes into a tab-separated Excel spreadsheet. AEM WCM asks you where you want to download the file.
By default, changes are encoded in Windows-1252 (also known as CP-1252). You can check UTF-8 to export the changes in UTF-8.
Select the location and confirm that you want to download the file.
After you download the file, you can open it from your spreadsheet program, for example, Microsoft Excel. The spreadsheet program imports the file and converts it to a spreadsheet format.
By default the import functionality is hidden when you open the Bulk Editor. Simply adding the parameter
hib=false to the URL will display the Import button on the Bulk Editor page. You can import content from any tab-separated (
.tsv) file. In order for importing to work properly, the column headings (first row of cells) must match the column headings of the table you are importing to.
When you re-import content, you erase any previous content for those nodes. Be careful not to overwrite important information.
To import content:
?hib=falseto the URL, e.g.:
.tsvfile. The data are imported into the repository.