Phil Robson DocuWare Corporation Senior Director Professional Services, Americas

Jon,
I'm not aware of that problem. Can you post the actual expression and the WF History showing the error condition? I'll then have to work through it.

Phil

Gilles,
Fair point. I had a quick look for the bug yesterday and could not find it, so I did not dwell on it. However, there is a fix for the LIKE operator imminent in the Cloud, and presumably in the next On-Premise 7 update. I'll test it once it is released and report back here.

Phil

Ok. Everyone keep cool. LIKE does work. However, what it does not LIKE to do is to parse a concatenated string.
Therefore this will fail:

SomeFieldFromDatabase LIKE '%' + GV_PO_Number + '%'

This will work:

SomeFieldFromDatabase LIKE '%' + 0881 + '%'

Of course that is useless since our PO number is dynamic not a fixed entry.....

The solution is to work the problem. Since it does not LIKE to concatenate strings in the WHERE clause with a LIKE operator, we simply concatenate the string we intend to use in another variable first.....

Follow me here....

String Variable - GV_PO_Number
String Variable - GV_TempVar
String Variable - GV_Returned_Value

Data Assignment 1:    Assign the PO Number to GV_PO_Number. (I assigned 0881)
Data Assignment 2:    Use an Arithmetic expression to create the value to parse to the database
GV_TempVar =   '%' + GV_PO__Number + '%'

Data Assignment 3:   Execute the query (UpdateValue is simply the field name I used in an external DB)

GV_Returned_Value = UpdateValue LIKE  GV_TempVar

Result = AAAC-00881

Note!! Each data assigment must be a seperate step, do not assign them in one step.

Phil Robson
Senior Director Support Americas

https://www.docuware.com/sites/default/files/forums-images/LIKE.png

Nathan,
All official documentation can be found at help.docuware.com.
The FAQ site is being transitioned to a new portal and therefore we are not duplicating documentation at this time.

Phil

Try this:

LIKE "*" & GV_PO_Number & "*"

Phil

You are enclosing the variable in quotes. This will make it search for the litteral string GV_PO_Number, and not the actual value.

Try this WHERE clause: LIKE "%" & GV_PO_Number & "%"

Here we parse the actual value of the variable encapsulated with the wildcard % sign.

Phil Robson
Senior Director Support Americas

I did forget to mention that if the user is supplied a document link, and the view window expires, then instead of a document, they will be presented with an empty search dialog. Just something to keep in mind. Sadly, there is no way to give the user a message that the view window has expired.

Phil.

Casey,
You can do this. There are some strict rules that you must adhere to for it to work.

Setup.
Each user that is to partake in the "Expired View" process must not be in any role or group other than the Expired View Role.
Create your Expired View role, adding the required users.
Create a Date field in the file cabinet "Show Until".
Create a Search Dialog called "Show Me Search". Add the Expired View Role only to this Search.
Create a Result List called "Show Me Result" and allocate it to the "Show Me Search". Add the Expired View Role to the Result.
Create an Index Profile called "Show Until". Filter this profile with the field "Show Until" Is(Where clause) > CURRENTDATE().
Check only the Search and Display document boxes. Add the Expired View role to this profile.
Create a Custom Profile called "Show Until2". No rights boxes at all are to be checked. Add the Expired View role to this custom profile.

When a document is to be shared, either by searching, or by sending a document link, then the user sharing the document should edit the index entries and enter a date appropriate to the vewing window. The user in the Expired View role will only be able to see, or search, or click the supplied link while the View Until date is greater than the current date.

Phil Robson
Senior Director Support Americas.

David,
Oddly I found this issue in the bug list this morning with 3 caes attached to it, but no one had escalated it for a hot fix. Aracelys will contact you with a short questionnaire the answers of which will assist me in escalating this issue for a hot fix.

Phil Robson
Senior Director Support Americas

Leon,
I am not at all sure why it worked initially, but the error indicates that it is not expecting the parenthesis is the string.
An easier way is to use the Contains operator, and select Email of the user as the entry. The result will be what you want, but DocuWare will contruct the query correctly.

Phil Robson
Senior Director Support Americas