nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Cannot Remove Versionable Aspect

blc

Hi

My objectives is to default add versionable aspect to every content and explicitly remove the versionable aspect under some folder using ruling - remove versionable aspect.

Senario:
Folder Sturcture: Root Folder –> Version –> Version Testing
Folder Rule:
1. "Version" Folder - (inbound rule) all items add versionable aspect (turned on "apply to sub-spaces" option)
2. "Version Testing" Folder - (inbound rule) all item remove versionable aspect

Therefore, I can see two rules under "Version Testing" folder and the sequence is:
1. all items add versionable aspect (inbound and inherited)
2. all item remove versionable aspect (inbound and local)

Testing:
I add a new document say "abc.doc" to "Version Testing" folder.

Result:
abc.doc versionable aspect was not removed without any error.

Question:
Why versionable aspect was not removed even I applied the rule to remove versionable aspect ???? Please Help

Find more posts tagged with

Comments

jayjayecl

discard the "herit rule" that you don't want in your "Version Testing" folder

jpfi

Hi,
at least in further alfresco version the rule execution order was not reliable, so your apporach may have some side effects.
Removing inherit rules as mentioned before should sove your prob.
cheers, jan

blc

thanks JayJayECL and jpfi, Yes, I knew it should work if I chose not to inherit rule from parent option, however, what I really want is to only make "Version Testing" folder removing versionable aspect but not for folders under "Version Testing" folders. Because we assumed only few folders would take out versionable aspect.

And now I am trying to use a work around that create new aspect with a field "folderVersionable" (boolean value) for every folder, and implement an actionExecutor in java (rule action in java) to add versionable aspect whenever the folder properties "folderVersionable" value is true. Whenever the user wanna bypass the "add versionable aspect" action, they only have to update the properties "folderVersionable" value to false.

Final thing is, I am also thinking how to prevent that rule (or system default rules, not user rules) from being deleted by the folder coordinator ???!!!!!!