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.
<params> <param name="id">#{actionContext.id}</param> <param name="dummy">dummy1</param> </params>
var curForum; forums = companyhome.childByNamePath("Forums"); logger.log(forums.name); forumsChildren =forums.children; for(i=0;i<forumsChildren .length;i++) { child =forumsChildren[i]; if(child.id.equals(args["id"])) { curForum = child; logger.log("Current Forum Name : " + curForum .name); } }
you can pass the ID for the space e.g. SpaceDetailsBean.space.id should work ok. Of course SpaceDetailsBean.space.id is only valid when in the context of the Space Details dialog page. Generally the "current" space can be found using:NavigationBean.currentNodeId
companyhome.childrenByXPath("//*[@cm:name='"+ myNodename + "']")
var id = args["id"]; // assume the 'id' arg contains a node id var node = search.findNode("workspace://SpacesStore/" + id); if (node != null) { // we found the node… }
I read the other post again and now it worked for him. When i saw your answer i tried some things and i now know what the problem is! <action-group id="document_browse_menu"> <action idref="test_js" /> </action-group>This one does not work <action-group id="doc_details_actions"> <action idref="test_js" /> </action-group>This one does not work <action-group id="document_browse"> <action idref="test_js" /> </action-group>This one does workIs this all how it should work, or should i be able to get actionContext.id from document_browse_menu and doc_details_actions?