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.

override explorer delete?

esource

I need to override the default delete behavior in alfresco explorer. Can I do this through a behavior? How can I do this?

Find more posts tagged with

Comments

mrogers

What do you mean by "override the default delete behavior". By all means you can define a policy implementing your "onDelete" buisness rules. But you can't interferre with the deletion process itself.

esource

there is strange behavior with Alfresco explorer delete. For example, I create a document called DualParent in TestSpace1. I then go to TestSpace2 and add the node DualParent from TestSpace1. Now DualParent is visible in both TestSpace1 and TestSpace2. TestSpace1 is the primary parent of the document DualParent. Now if I should delete DualParent in TestSpace1, DualParent is actually still visible in TestSpace2. If I try to access DualParent in TestSpace2, then I get an error message in explorer explaining thet DualParent is no longer there. This is strange behavior and not something our clients would want.

So, I was looking for a way to change the default delete behavior, or override it or somehow have Alfresco behave differently.

A better delete behavior and one I would like to implement would be when delete is selected, a check is made to see if the node has multiple parents, in DualParent's case TestSpace1 and TestSpace2. One is the primary parent. One is an association. If there are multiple parents, then the actual node itself is not deleted, but instead only the association to in this case the primary parent. This way, we can avoid the error message. An alternative would be to delete the parent as well as all the associations.

Do you see what I am getting at? Why someone would want custom delete behavior? What would you suggest? Would the onDelete business rule take care of this?

esource

What do you mean by "override the default delete behavior". By all means you can define a policy implementing your "onDelete" buisness rules. But you can't interferre with the deletion process itself.

can you explain in more detail what you mean by "onDelete" business rules?

savic_prvoslav

You have delete Dialog bean.

targa2000

what he means is implementing a behavior that captures actions on the node, for instance onDelete of a node or beforeDeleteNode.

esource

yes, thank you. I have implemented behavior to capture when the node is deleted. I tried to throw an exception before the node is deleted, but this did not stop the deletion. Unfortunately it appears I cannot stop the deletion.

glaenen

Hello,

Did you ever solved this issue? I'm facing exactly the same problem.

Thanks,

Glenn