Making association links work (high-level advice needed)

[hbf]

Like some others, I want the Web Client user to be able to click on an association in the "Details of" dialog of a node (node A, say). What would show up then is the "Details of" dialog of the content node at the end of the association (let's call it node B). Ideally, if the user clicks the "Close" button of the latter dialog, she would be back in the origin "Details of" dialog, the one of node A.

I tried to implement this and have almost succeeded. (Again, like in the case of my AMP for TinyMCE textareas in the Web Client, I want to make the result available to others in form of an AMP.)

The problem I have run in is that when the user clicks on an association, the browser visits the correct URL (showDocDetails with the noderef of B) but still, the properties of node A are shown (see this issue also).

I just need some high-level advice to be able to continue working! Can somebody help?

1. Is it correct that the problem is due to a dialog/wizard being open? (As mentioned in the issue, the link to B works if you first close the dialog and enter the link into the browsers URL textfield.)

2. Provided my assumption 1. holds, what would be the way to go to alter this dialog? I guess I would have to add ANOTHER dialog (the one for B) onto the dialog stack. Would I use the Dispatch Mechanism for this? I have the feeling I need to alter showDocDetails (i.e., the filelink-details.jsp behind it) and replace it with a version that pushes on the dialog stack…

I am grateful for any guiding sentences!

Kaspar

[hbf]

I have created a new version of my AMP which now also shows a "Create" button next to the "Search" button in the "Modify Content Property" dialog. Clicking it creates a new target node of the association and associates to it. Additional information is available on the wiki page (see link one of the previous posts). Notice that there are some known issues; see again the wiki page.

[alexandra]

An really interesting feature that leverages the power of Alfresco. However, since I haven't the same understanding of the architecture I wonder if it would be possible to extend an assoication with custom attributes. That would in essence create a "relationship object" with its on attributes on its own "View details" page. Such a feature could be use to define  the type of relationship between two or more documents like "similiar content", "used as reference" and so on…

[lvs]

Hi,

First of all thank you very much for your contribution, I downloaded your AMP and it works fine!
I woul dlike to modify it in order to show a link directly to the content of the child. I also would like to add in the child node a link to its parent.
I would be very grateful if you can give me some peaces o advise about how I can do this changes because I do not know much things about JSF…
Thanks a lot
Laura

[itrub]

Dear colleagues
My name is Iliya Trub, I am software engineer from Moscow.
I use your very good plug-in for Alfresco, try to develop it  and I have two technical questions, concerning it:
1) I open on view the card of document A and click on reference to child-associated document B. Document B was opened on view. But when I close B-document dialog I do not return to view card of A-document, but to the folder, where B-document is stored. But this is not a problem. The most important for me is the second question

2) Let us open view card of A-document  not from folder, but from the task panel, when document A is on workflow.  In that case the component tree does not contain component dialog:body:document-props, so the broadcast method fall down with error "Null Pointer Exception", when try to perform getChildren method. It contains component dialog:body:content-props. But how to change the lines of broadcast-method to adopt your code to that situation? The second case. I try to modify your code in order to make reference on associated document not only from view card, but from edit card also. The same situation. Edit card does not contain component documentrops, it contains content-props. If I try to apply getChildren.clear() to content-props component, I get after click on reference  the same edit card of A, without transition to view card of B. This phenomena is well known for you.
Could you give me advice, what I can try to do in order to extend the functionality of web link program in such directions?
Thanks in advance
Sincerely, Iliya