As far as I know the workflow task list does not require to re publish the WF hence no need to wait for a new instance (at least this is the case in 6.11-6.12)
You just need to refresh the web browser.
Thanks a lot, using the FAQ is the right way to find the relevant basket GUID
Thanks a lot for your fast feedback
Looks like promising. I should have done better research :-(
We are going to test and give you feedback
Alhough we did a bunch of tests, we cannot use the "Document tray" Integration Type.
Using either the SDK or the URL Creator.
The server returns a
The request could not be served.Status:
406 - Not AcceptableMessage:
You do not have the rights to view this basket. Please contact your administrator.ExceptionRequestNotAcceptedException: You do not have the rights to view this basket. Please contact your administrator.
As this done using admin with full rights, looks like this is not the real problem.
The encrypted URL generated on a 6.12 Peters Engineering looks like :
To find the Document Tray Guid, we assumed this the file number looking like a GUID in the storage location for the web basket
May be a wrong guess?
Any help would be appreciated
Thanks in advance.
If I read the latest FAQs correctly, a workflow task calling a webservice via HTTP will fail if called so after November 1st 2018.
If I am right it means one has to change the call asap to be on the safe side.
But, being on the safe side will not mean to be immune to such behavior as some old task with HTTP call might still be active. As some workflow task can last for quite some long time (for an order pending for instance)
Any recommendation to avoid problem ?
I do not know about Fortis but I can confirm that our customers really like DocuWare for its GUI, simple and efficient.
And in general, they like it because it is simple to use and they can get access to any kind of document from anywhere. The way everything is integrated in the same client, store, search, workflow tasks, viewer, ... is also a key element.
Talking about speed, I would recommend first to make some tests using the diagnostic mode available in the client. Tick the "Activate diagnostic mode" in Parameters/General and work with DocuWare.
It can show you if there is a bottleneck and if yes, where it is in the long process triggered to view a document.
The client PC performance is also important. SSD hard disk for the file server makes also a big difference as opening a document in DocuWare requires a bunch of I/O
Hope it helps
Depends where you are located and what kind of legal value you are looking for.
We can help you for french and belgium market and soon for swiss market for certified electronic signature
On Premise or Cloud.
I do not know if my post is still relevant as you discussed quite a lot.
Any way, here is my "contribution"
Without access to the database and without creating an autoindex job to process all the database to copy the system DOCID to a custom DOCID, I found that searching the DOCID using the fulltext gives pretty good result.
Sometimes it might return more than one document as the DOCID number can also be a value in a document.
Of course this is fully manual, a little but quick and dirty, but it can help
To integrate DocuWare within a portal we need some kind of authentification gateway.
OAUTH 2.0 seems to be the solution to cover the need
Is there any plan to support OAUTH 2.0 with DocuWare ?
Other idea ?
PS : URL Creator does not fit the need.
Thanks for your feedback
Too avoid such situation it would be nice (and time sparing) if DocuWare team does some kind of survey before removing a functionnality
Thanks in advance