• RE: A report or list of users and what access or permissions they have

    Sam,

    You are most welcome!

    Hope your DBA gets a nice listing back for you -- just glad someone has access to the data. Not sure what cloud folks end up doing when direct queries are required!

    Thanks,
    Joe Kaufman
  • RE: A report or list of users and what access or permissions they have

    Sam,

    We are on 6.11, SQL Server, on premise. So, a query of the database gets us the information we need, at least the basic add, edit, view, and delete capabilities by user/group and file cabinet. The queries are fairly complicated, but here they are, run against the dwsystem database of your SQL Server:

    For GROUP permissions:
     
    SELECT G.Name AS GroupName, R.Name AS RoleName, FC.Name AS FileCabinetName, FCP.Name AS Permission
        FROM DWGroup G INNER JOIN DWGroupToRole GR ON G.gid = GR.gid
            INNER JOIN DWRoles R ON GR.rid = R.rid
            INNER JOIN DWFCProfileToRole FCPR ON R.rid = FCPR.rid
            INNER JOIN DWFCProfile FCP ON FCPR.fpid = FCP.fpid
            INNER JOIN DWFileCabinet FC ON FCP.fid = FC.fid
        WHERE G.oid = 1 AND G.type = 1 AND G.Active = 1
            AND R.type = 1 AND R.active = 1
            AND UPPER(FCP.Type) LIKE '%FCPROFILE%'
        ORDER BY G.Name, R.Name, FC.Name, FCP.Name

    For USER permissions:
     
    SELECT U.Name AS UserName, FC.Name AS FileCabinetName, FCP.Name AS Permission
        FROM DWUser U INNER JOIN DWFCProfileToUser FCPU ON U.uid = FCPU.Uid
            INNER JOIN DWFCProfile FCP ON FCPU.fpid = FCP.fpid
            INNER JOIN DWFileCabinet FC ON FCP.fid = FC.fid
        WHERE U.oid = 1 AND U.Active = 1
            AND UPPER(FCP.Type) LIKE '%FCPROFILE%'
        ORDER BY U.Name, FC.Name, FCP.Name
    

    If you do not have access to the database, or if the structures have changed between 6.9 and 6.11, you may be out of luck. But these queries return a handy listing of groups and users and the permissions they have for file cabinets.

    Do note that if your security setup is more convoluted (as in you use a lot of complex, custom-built Profiles) this data will probably be of less use to you. But if you keep things fairly vanilla, it generates a nice summary of what people can see.

    Hope this helps!

    Thanks,
    Joe Kaufman
     
  • RE: Is a document read?

    Pierre,

    What platform are you running on? That is, do you have access to the underlying database server for DocuWare?

    On version 6.11, on premise, I can go into the SQL Server database and check the fields:

    DWLASTACCESSDATETIME
    DWLASTACCESSUSER

    and see who last viewed a document. I just viewed an old document and it updated those fields to the current date/time and my username.

    Those fields also appear to be accessible via Platform SDK API queries as well as URL Integration, though I am not sure how you could expose them on a regular search dialog. What you could do is add a field of your own that uses a "Predefined entry" of "Access date" and "Access user" (short or long name). Then you could search by access date and access user. I do not think there is any other way to expose those system entries on a standard Search dialog.

    Good luck!

    Thanks,
    Joe Kaufman
     
  • RE: URL Creator -- Pass query without Base64 encoding?

    Simon,

    Don't worry about the late response -- you came through! I got this working!

    I had previously noticed that the final URL (that displays in the browser once the document comes up) shows the query "in the clear". But any time I tried to use that URL with an unfound document, it displayed a very nasty system message I did not want users to see that (and I assumed the URL just wasn't working right). But when I switched out "Document" in the URL for "Result" (like in your example), it works to display a nice screen whether a document is found or not. In other words, instead of going directly for the document, it went for the Result List.

    And by utilizing displayOneDoc=True in the URL I can make the viewer appear immediately, which is ultimately what I want (this integration works with one document at a time).

    This is a much more straightforward integration once one figures out the escaped characters in the URL. And it turns out our ERP system displays the DocuWare viewer right inside its own frame (it is pseudo-browser-based), so it looks much more seamless and doesn;t fire up a new browser tab for every viewed document.

    Thanks so much!

    Joe Kaufman
  • RE: URL Creator -- Pass query without Base64 encoding?

    Fabian,

    I really cannot thank you enough for triggering this idea -- we now have integration working via an application that serves up integration functionality via command line programs! I don't when (if ever) I would have had that idea if not for your web service comment!

    Have a great weekend!

    Thanks,
    Joe Kaufman
  • RE: URL Creator -- Pass query without Base64 encoding?

    Fabian,

    Thanks for the response and the web service idea. We aren't exactly equipped to start writing web services, so I was hoping for a different answer. But it is what it is. 

    I actually already have a WinForms application that I write little command-line snippets for, so perhaps I could use that to pass parameters to and generate a URL to execute on the client side. Same idea as a web service, just an application service. So, I appreciate you sparking the idea for that!

    Thanks,
    Joe Kaufman
  • URL Creator -- Pass query without Base64 encoding?

    Hey all,

    I am trying to integrate DocuWare with a new ERP system, and the new ERP system allows for  parameterized URLs to be built and summoned via right-click menu options.

    I can get everything working by hard-coding the file cabinet guid, and I can grab query criteria from the context of whatever form I am on in the ERP tool. But the "q" parameter in DocuWare URLs is followed by the query that has been Base-64 encoded. The URL creation area in the ERP tool does not have any functionality with regards to encoding any part of the URL.

    Is there a way to pass the "q" parameter "in the clear", that is, without any encoding? Is there a setting on the server that would allow the query string to be passed in the clear? Without this I do not know how I am going to get this working...

    Thanks,
    Joe Kaufman
  • RE: Added Field to File Cabinet -- no one else can see

    Tobias,

    Thanks for confirming! Much appreciated!

    Joe Kaufman

  • RE: Added Field to File Cabinet -- no one else can see

    Hey all,

    Figured it out -- the file cabinet in question DID have Profiles in play, and apparently when you add a new field you have to explicitly grant the rights to that field per non-default Profile. I made sure the new field got added to our custom Profiles, and it shows up now. The new field automatically gets added to the default Profiles by the looks of it.

    Thanks,
    Joe Kaufman
  • Added Field to File Cabinet -- no one else can see

    Hey all,

    I added a field (index) to a file cabinet yesterday and added it to all dialogs. Shows up fine for me.

    I found out today a different user cannot see the new field. It just isn't there in the store, search, result, or index dialogs.

    I have "owner" permissions on the file cabinet but have never seen a certain field be unavailable for some users and not others. WE have not done field-level lockdowns or anything like that, so I do not understand what is going on.

    I cleared cache on the other user's workstation and all that -- no difference. What am I missing?

    Thanks,
    Joe Kaufman