You are viewing limited content. For full access, please sign in.

Question

Question

Search is not returning shortcuts

asked on February 17, 2021

I have a client that needs to perform a search for shortcuts with a specific field value so that they can rename the shortcuts. This post of course explains why this isn't working but there is a reason that they don't want to set the resolve shortcuts on the workflow user as they have hundreds of workflows and many of them are running searches and this could cause issues for those workflow processes.

https://answers.laserfiche.com/questions/55384/Search-results-does-not-return-shortcuts

The client was hoping that a modification could be made as a feature request. We came up with 2 possibel solutions.

1.  When Type = S then return shortcuts in a search based on field values

2. Since this is primarily an issue in workflow maybe have a check box in the search repository options that could use the resolve shortcuts option only for that activity?

Let us know if this is something that would be viable.

2 0

Replies

replied on February 17, 2021

I'd like to know of a solution to this as well. I have a couple of workflows that handle shortcuts and my only solution has been to keep shortcuts separate from the documents so I make sure that only the shortcut is modified when I search for the file name. Having a way to search for a specific shortcut in a folder of documents and shortcuts would be very helpful so I don't accidentally modify the document itself when I try to search for it. Thanks for the post.

1 0
replied on February 17, 2021

Agreed, this would be very useful.  Our most common practice right now is just to delete a shortcut and rename it, because trying to work with a shortcut directly is difficult with the tools we have.  Of course, deleting and recreating a shortcut can be difficult as well, given we have to recreate any paths the shortcut(s) currently utilize.  Being able to work more directly with them (when specified) would be a much better option.

1 0
replied on February 18, 2021

Update - I did discover and have used the "Retrieve shortcuts" feature in Workflow, which does simplify things.  It would still be nice to be able to search for them if we want to specify that, but if anyone else has this issue, Retrieve Shortcuts is a good workaround.

0 0
replied on February 19, 2021

Basically what it comes down to is that fields are not actually a property on the shortcut itself, but on the entry the shortcut is pointing to. This isn't an issue when you search across the location that contains both the shortcut and target entry (like the whole repository) and tell it to return shortcuts, but if your search is limited, it will not find the fields in the area that the search is limited to. What 'resolve shortcuts' does is requests that the search query check the entries all shortcuts it finds is linked to to check there which, as you can imagine, can lead to poor performance and why it is a separate option. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.