Expand my Community achievements bar.

SOLVED

Editable Template Policy not getting updated with mode=merge in filter.xml

Avatar

Level 2

Hi

I am currently working on AEM 6.4. I have created my own project specific editable template

/conf/project-xyz/settings/wcm/template-types

/conf/project-xyz/settings/wcm/template

/conf/project-xyz/settings/wcm/policies

I have created a default policy for title component as below

/conf/project-xyz/settings/wcm/policies

          project-xyz

               components

                    content

                         title

                              policy_1433655

In my filter.xml file i have allowed as below:

<filter root="/conf/project-xyz/settings/wcm/policies" mode="merge" />

When I am trying to deploy this policy, it is not getting updated in CRx/de.

If i remove mode=merge from filter.xml, This newly created policy for title gets deployed in Crx/de

<filter root="/conf/project-xyz/settings/wcm/policies" />

With mode=merge, the policy is not getting updated in Crx/de.

Any help will be really appreciated

Thanks

Hina

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

filter elements

The filter elements are independent of each other and define include and exclude patters for subtrees. The root of a subtree is defined by the root attribute, which must be an absolute path.

The filter element can have an optional mode attribute which specified the import mode used when importing content. the following values are possible:

“replace”
This is the normal behavior. Existing content is replaced completely by the imported content, i.e. is overridden or deleted accordingly.
“merge”
Existing content is not modified, i.e. only new content is added and none is deleted or modified.
“update”
Existing content is updated, new content is added and none is deleted.


Arun Patidar

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

filter elements

The filter elements are independent of each other and define include and exclude patters for subtrees. The root of a subtree is defined by the root attribute, which must be an absolute path.

The filter element can have an optional mode attribute which specified the import mode used when importing content. the following values are possible:

“replace”
This is the normal behavior. Existing content is replaced completely by the imported content, i.e. is overridden or deleted accordingly.
“merge”
Existing content is not modified, i.e. only new content is added and none is deleted or modified.
“update”
Existing content is updated, new content is added and none is deleted.


Arun Patidar