This page describes how to use the Policy Importer tool. The tool can be found via the AEM Tools primary navigation, and selecting the AEM Modernize Tools menu item.
Job Listing
Selecting the Policy Conversion tool displays a list of all the previously scheduled jobs. From here the user can view the details of a specific job, or create a new one.
Job Detail View
When a job has been scheduled and is running or completed, it can be viewed via the Job Detail view. This will show the paths selected for processing and their current state.
If the job has been scheduled but not executed, or is mid-execution, you can refresh the page to check the status/state.
Job (Buckets) List
If a given scheduling request has over 500 paths that need to be processed, then multiple jobs will be scheduled. The job detail view will allow users to select which job to view the details, using the left panel.
Job Creation
The following configuration options are available when scheduling a Policy Import Job.
Job Title
As with all the tools, the Policy import tool requires a name for the Job to be created. This helps with identifying the job once it is scheduled and completed.
Configuration Target
A Policy job also requires a target location into which the new policies will be created. This will make them available to any Editable templates. The user scheduling the job must have *write* access to this location in the repository, or the job will not be scheduled.
The user scheduling the job must have *write* access to this location in the repository, or the job will not be scheduled.
SuperTypes
Components using a design are not necessarily using a direct reference. Legacy designs are inheritable through the *page's supertypes*. Thus, it is possible when searching for a design the direct reference does not contain the information used to render a component.
Checking this property will task the job to search the page's hierarchy to find the specific Style node that a component references. Unchecked, if the Style is not a direct reference, it will be ignored for import.
Overwrite
Since Designs and Policies are not stored in the same location in the repository, it's possible to reprocess a Policy import. This tool marks already imported designs with the created Policy location.
Checking this option import all found designs as Policies, regardless of whether they have already been imported. This can result in duplicate policies, if selected.
Page Selection
Importing is done by selecting the source pages from which Designs are referenced. The page list will show how many designs are found, and how many rules will apply to those create the associated policies.
The user may select as many pages as they want; depending on the number more than one job may be scheduled.