I am wondering if it was possible to be able to click on a hyperlink which gets stored as one of the index fields. We would like some of our users to be able to click either on the result list or the DocuWare viewer and whatever the link has is where the users will be re-directed to.

Can that be done? We tried saving a couple of links on the result list and even on the document but the links are not clickable.

I have the URL for google.com but I would have to select edit index entries and then manually copy and paste the URL. I would like to be able to just click on the link.

I also have the option of putting the URL as part of the content of the document but no matter the format it still doesn't allow me to just simply click on it.

Currently, Any user can create a personal stamp and update the document(s) metadata without any validation.

From the Configuration page, "Configure Stamp" permission under functional profile doesn't affect "Personal Stamps", and the user will still have the permissions to create stamps and use it.

In the case we have a workflow process with one task contain two decisions (Approved, Rejected), the decision will affect "status" filed to be updated as (approved, rejected).

Users need to have the permission of (write, modify) on the "status" field to take the decisions, at the same time user can create a personal stamp with fixed entry into the status filed, and change it to any unwanted value ( ABC, XYZ, or any other value).

this functional profile feature will allow us to control user entry as needed.

According to your FAQ #1858, Because of technical reasons it is not possible to display in Web Client placeholders in fields with field masks. Only in Windows Client placeholders can be displayed.

A large portion of our customer base is comprised of County Clerk’s Office within the State of Indiana. The primary field that they use to look up documents is a 24-character Cause Number, which includes numbers and letters separated by dashes in a state-defined format. In the Windows Client, we create a field mask which not only eliminates input errors but speeds data entry. The first 2 digits always represent their County Identifier, so we auto fill the first 2 spaces. Then each additional space is restricted to only allowing a number or a letter to be entered, and automatically places the dashes without having to type them.

Another problem with field masks has now arisen. Not only does the Web Client allow incorrect entry and not notify the user until they have completely filled out the dialog box and clicked on either ‘Search’ or ‘Store’, but the field mask will no longer supply the first 2 characters or the dashes. Unfortunately now our county government users all over the State of Indiana are going to have to be retrained to type the dashes in. When we are talking about that kind of loss in productivity along with the loss of speed inherent with a browser-based product, what is the incentive for our users to upgrade?

Your support staff claims that this issue is being addressed in the upcoming ‘Dolphin’ release. Once the issue has been resolved, we need a hotfix to address our current 6.5 installs. It’s very frustrating that every time we run into a problem, we’re told that it must be a bug in whichever version our particular client happens to be using. And the DW developers won’t even look at fixing it in anything but the latest version.

When you put a string inside a keyword field/variable, the system split the string in separate keyword entries at each space or comma in the string wich is simply horrible to handle.

You have a dirty workaround solution by putting your string in a text variable concatenated with quotes and then assign the text variable in the keyword field.

Plus, currently, if there is quotes inside the string itself (for example, french words and/or expressions are using quotes), your trick with the intermediate string variable doesn't work at all...

You should add the possibility, in the data assignations inside the workflow designer AND/OR directly at field configuration, to specifiy the save mode "KeyWord mode" or "String mode" for example.
This way we will not be forced to put a string inside a variable concatenated with quotes at each keyword assignation (seriously, that's a crazy aberration... This should be managed natively)

Thanks