topic Re: Need email notification to point to Share not Alfresco in Alfresco Archive

Need email notification to point to Share not Alfresco

tctim — Wed, 27 Jan 2010 15:13:02 GMT

Hello-I want to change the following code to point to Share instead of to Alfresco since my users only have access to Share.From notify_user_email.ftl**************You can view it through this link:https: //mydomain/alfresco${document.url}*************An example desired rendered URL would look like

Re: Need email notification to point to Share not Alfresco

tctim — Thu, 28 Jan 2010 14:12:18 GMT

What I am trying to achieve can be seen on the document details page for any content item in Share - in the right hand nav there is a box titled Share with "Document URL". In this box is the URL to this particular document - I need to know how that URL is dynamically generated. I thought I had it figured out when I changed the URL in the notify_user_email.ftl to http: //mydomain/share/proxy/alfresco-feed/api/node/content${document.url} but the ${document.url} generates a leading /d/d that breaks the URL.

For example -
The URL to the document is:
https: //mydomain/share/proxy/alfresco-feed/api/node/content/workspace/SpacesStore/b2e3c064-9988-422e-8416-05795e70d5fe/notify_user_email-3.ftl

The above example generates the following URL:
https: //mydomain/share/proxy/alfresco-feed/api/node/content/d/d/workspace/SpacesStore/b2e3c064-9988-422e-8416-05795e70d5fe/notify_user_email-3.ftl

Thoughts?

Re: Need email notification to point to Share not Alfresco

tctim — Thu, 28 Jan 2010 17:04:59 GMT

Yup - one of those days. I meant to say I wanted to know how the URL was generated in the "This Page URL"….

Re: Need email notification to point to Share not Alfresco

mikeh — Thu, 28 Jan 2010 19:50:51 GMT

Unfortunately it's a bit tricky, assuming you want to direct the user to the details page..? The "The Page URL" is literally copied from window.location.href, so it's not really generated at all.

As for the others, there's some work in the DocLib webscripts to work out whether an arbitrary nodeRef (which could live anywhere in the Repository) is actually part of a Site or not. This is done by examining the node's qnamePath. Something like:

var qnamePaths = node.qnamePath.split("/");
var displayPaths = node.displayPath.split("/");
if ((qnamePaths.length > 5) && (qnamePaths[2] == "st:sites"))
{
   // This asset belongs to a site
   var site = displayPaths[3];
   [generate the url]
}‍‍‍‍‍‍‍‍

You should be able to generate the URL from there, although you'd have to "know" the first part, e.g. http://serverort/share/page/site/{site}/document-details?nodeRef={nodeRef}

Thanks,
Mike

Re: Need email notification to point to Share not Alfresco

tctim — Thu, 28 Jan 2010 19:59:31 GMT

First - thanks for the reply…

This is beyond my skill set - I was hoping it was as easy as adding something like ${document-link.page} to the end of the known part of the URL.

I sure would have thought this would have been basic functionality for the application - even this forum has the email alert ability.

Re: Need email notification to point to Share not Alfresco

mikeh — Thu, 28 Jan 2010 20:24:02 GMT

The core Repository (where your e-mail template gets populated) knows nothing about Share Sites or how to generate URLs to arbitrary pages that may or may not exist. Share is one example of a remote application that uses the Repository for storage, so this separation is valid. URLs would have to be generate by code that was "Share aware" such as the example I gave.

Thanks,
Mike

P.S. I'm not sure how comparing a REST-based two-tier CMS to a PHP forum is particularly relevant. :?

Re: Need email notification to point to Share not Alfresco

tctim — Thu, 28 Jan 2010 22:36:23 GMT

Ok - I'm not that great of a coder and all I want is the code to put into the notify_email_user.ftl to provide the correct URL on the email notifications.

Is there a document somewhere that can walk me through the process of how to create the appropriate dynamic URL?

Tim

Re: Need email notification to point to Share not Alfresco

tctim — Sat, 13 Feb 2010 15:18:52 GMT

I still haven't figured this out but here's how I **think** one would dynamically construct the URL.

Sample URL
https://mydomain.com/share/page/site/az/document-details?nodeRef=workspace://SpacesStore/66c42c1b-0d58-4757-a08b-c20ab51f3be6

So it seems to me the only thing I need to figure out is how to reference the site - az in this example and the variable that represents the document in the SpaceStore - 66c42c1b-0d58-4757-a08b-c20ab51f3be6 in this example.

I would think it would be something like
https://mydomain.com/share/page/site/${document.site}/document-details?nodeRef=workspace://SpacesStore/${document.node}

But I can't find the reference document that outlines the list of the ${…}

Re: Need email notification to point to Share not Alfresco

janvg — Mon, 19 Apr 2010 11:38:43 GMT

Will the introduction of the repository browser in 3.2 r bring any solutions for this ? I believe more and more users will only face Alfresco through the share client (not the webclient), so it would be very useful if the e-mail templates would re-direct us to the correct interface.

Re: Need email notification to point to Share not Alfresco

felipe_gdr — Fri, 02 Jul 2010 20:30:34 GMT

Hi,

what do I do with this piece of code?

var qnamePaths = node.qnamePath.split("/");
var displayPaths = node.displayPath.split("/");
if ((qnamePaths.length > 5) && (qnamePaths[2] == "st:sites"))
{
// This asset belongs to a site
var site = displayPaths[3];
[generate the url]
}‍‍‍‍‍‍‍‍

I cannot put it inside a template, so where should it go?

Thanks

Re: Need email notification to point to Share not Alfresco

jager13579 — Tue, 24 Aug 2010 14:47:48 GMT

Using that sample code from the webscripts, I figured out how to get the site name into the url for the document. The code below assumes you know the folder is a site. I am assuming this because I created a separate email template for sites and choose that template when I create the rule. The code below could be easily extended to check using the qname.

<#assign ref=space.nodeRef>
<#assign displayPaths=document.displayPath?split("/")>
<#assign site=displayPaths[3]>
http://${url.serverPath}/share/page/site/${site}/document-details?nodeRef=${document.nodeRef}
‍‍‍‍‍

Re: Need email notification to point to Share not Alfresco

mikeh — Wed, 17 Nov 2010 08:21:41 GMT

Hi All,

is this possible? i´ve tried many thing to accomplish that but still not able to do such a thing.

any help is welcome.

thanks

All the code you need is in this thread.

Thanks,
Mike

Re: Need email notification to point to Share not Alfresco

b_fergerson — Wed, 15 Dec 2010 21:37:59 GMT

What I am trying to achieve can be seen on the document details page for any content item in Share - in the right hand nav there is a box titled Share with "Document URL". In this box is the URL to this particular document - I need to know how that URL is dynamically generated. I thought I had it figured out when I changed the URL in the notify_user_email.ftl to http: //mydomain/share/proxy/alfresco-feed/api/node/content${document.url} but the ${document.url} generates a leading /d/d that breaks the URL.

For example -
The URL to the document is:
https: //mydomain/share/proxy/alfresco-feed/api/node/content/workspace/SpacesStore/b2e3c064-9988-422e-8416-05795e70d5fe/notify_user_email-3.ftl

The above example generates the following URL:
https: //mydomain/share/proxy/alfresco-feed/api/node/content/d/d/workspace/SpacesStore/b2e3c064-9988-422e-8416-05795e70d5fe/notify_user_email-3.ftl

Thoughts?

Hate to bump an old thread; however, I ran into the same problem and wanted to share my success. I used this basic concept here and was able to actully just trim off the beining of the string when you use the ${document.url} variable. I used ${document.url?substring(3)} instaed with a begening of https: //mydomain/share/proxy/alfresco-feed/api/node/content and my generated URLs work like a charm!

Re: Need email notification to point to Share not Alfresco

mpeters — Thu, 08 Dec 2011 17:47:19 GMT

We have done it that way:

${url.serverPath}/share/page/document-details?nodeRef=${document.nodeRef}
${url.serverPath}/share/proxy/alfresco/api/node/content${document.url?substring(4)}
‍‍‍

The first link opens the Share page of the document. The second link opens or downloads the document directly.

You may force the download of the document (rather then opening in browser) with:

${url.serverPath}/share/proxy/alfresco/api/node/content${document.url?substring(4)}?a=true
‍‍

If ${url.serverPath} returns something with localhost or so, consider to set repo.remote.url in alfresco-global.properties.
Example:

repo.remote.url=http://your.domain.com:8080/alfresco
‍‍

I hope this helps. If you find errors please respond!
🙂

Regards
Markus

Re: Need email notification to point to Share not Alfresco

vpetrena — Fri, 27 Feb 2015 12:38:00 GMT

Hi, this was very helpful. How would a reference to the folder in which the document is look like?