Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

[Entry:path] token not working as expected.
Last Post 06/27/2011 3:57 PM by Tim Johnston. 5 Replies.
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Stefan Cullmann
New Member
New Member
Posts:12


--
03/02/2009 1:49 PM
Peter,

one of the most requested features for notification was the ability to get information about the actual path.

The name/title of the document means normally nothing without the precise context, for example
/committee/ultrasonic/meetings/2009-03-5/schedule.doc.
We don't want to title that document "schedule of the march meeting of the ultrasonic committee".

I tried to work with [Entry:Path], however that returns only  list of iintegers,
for example 0;367; 2124; 4563; 4789;

Any idea?
Stefan Cullmann
New Member
New Member
Posts:12


--
03/02/2009 2:30 PM
I just read inside the tempate document that this behaviour is by design. :-(
Peter, please consider something like [Entry:PathAsString] for a future release.
Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
03/03/2009 5:09 PM
Hi Stefan,
OK. Point taken. I'll make a note of it.
Peter
Tim Johnston
New Member
New Member
Posts:14


--
06/22/2011 10:43 PM
Peter, did you ever add this suggested token? I too would like to be able to include the "path" in my email notifications as I agree, the file name without a folder context is pointless..

Thanks, TJ
Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
06/27/2011 10:30 AM
Yes, it is [entry:fullpath]. There's also [entry:folderpath] which does just the folder.

Peter
Tim Johnston
New Member
New Member
Posts:14


--
06/27/2011 3:57 PM
Thanks Peter!

I'm not sure if there are other new tokens that have been added recently, but I think the notification tokens annex in the notifications help document may need to be updated.

Thanks again, TJ.
You are not authorized to post a reply.