I am using the Generate Web Client URL activity. I am linking to the shortcut (which is the entry ["current entry"] that is triggering the notification), however, it is generating a URL for the actual record/document the shortcut is to, not the shortcut itself. In the second image below, I am linking to a document that resides in the folder with a purple arrow but it is taking me to it's record in the folder with a red arrow. The link needs to go driectly to the shortcut that is triggering the workflow.
Question
Question
Replies
I might be misunderstanding what you are trying to do, but similar to this recent discussion, it's worth keeping in mind that shortcuts don't have the same full standing that folders and documents do. So for a shortcut to be the source entry, the action can only be something like a move of the shortcut; any metadata that is modified belongs to the target entry even if the user accessed it through a shortcut. And when you talk about a url for a shortcut - if this is a document shortcut (which I think it is, based on the screenshots) - there isn't really a way in the web client to reference the shortcut as a distinct entity from the target. DocView.aspx will only show the target entry. What you could do is to open the parent folder of the shortcut, but then it might not be clear what entry is of interest.
That is a shame, becuase yes, the folder it resides in would not be sufficient. I want the link they click to go directly to the shortcut as it would if they were in the repo browsing to it. And once the link opened the shortcut, if they clicked "back", it would take them to the folder the shortcut resides in, not the folder the document it is referencing resides in. Thank you for the info.