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.

API differences Javascript vs JAVA

darkredd

Hello everyone,

A silly question perhaps, however here goes: I am trying to leverage an already existing custom action which creates document links.
I have a slight lack of understanding of API differences.

In Javascript I am able to use the custom action's logic to create link with a script (Action Rule). But using Java with the same logic I do not get the same output.

Javascript

fNode.createNode(sNode.name + " Link", "{custom.uri}filelink", pr)‍

Where pr is a list of properties to be attached to the newly created link.

Java

nodeService.createNode(parentDest, ContentModel.ASSOC_CONTAINS, QName.createQName(LINK_URI), ContentModel.TYPE_CONTENT, linkParams)‍

Where linkParams is a list of properties to be attached to the newly created link.
I did not use the FileFolderService because it does not offer me a way to attach properties to the node.

With javascript I am able to create a link as if I had clicked on a document Library action itself, but with JAVA it just creates a new node altogether without any reference to the source node.

Am I misusing the JAVA API or is there just a difference entirely?

Find more posts tagged with

Comments

mrogers

IIRC I don't think you can have properties on an association. Well except the name and type which are special cases. linkParams are actually properties for the new node.

I suspect your LINK_URI is not correct. There is a convention to follow that is enforced by the file folder service.

darkredd

Hi mrogers,

Thanks for your response. However my "LINK_URI" is correct because it's a copy and paste of the uri which I use in javascript. On the original post {custom.uri} is a replacement of the actual uri which in fact is assigned to LINK_URI. Based on your response I would think I am then uri the NodeService.create() method in a wrong, specifically when it come the association part.
What would you suggest I look at to achieve this?

darkredd

Hi,

I managed to find a solution to my problem. As suspected it was lack of understanding of the API. I had placed my arguments in the wrong order as expected by the method, and one QName ("ContentModel.TYPE_CONTENT") was wrong. In the end I had to change the method to look like this:
This is the new order:

nodeService.createNode(parentDest, ContentModel.ASSOC_CONTAINS, ContentModel.TYPE_LINK, QName.createQName(LINK_URI), linkParams)‍

The one with an error was:

nodeService.createNode(parentDest, ContentModel.ASSOC_CONTAINS, QName.createQName(LINK_URI), ContentModel.TYPE_CONTENT, linkParams)‍

Now I am able to achieve what I had set out to do.
Thank you.