• Questions about Stamps

    Hey all,

    I have two questions about Stamps.

    1. Permissions. It looks like you can assign Profiles to a stamp, or assign access by User. This is not very flexible. If I want to give access to a "VOID" stamp, say, just for Accounting, I want to be able to do that. And I kept security simple such that I assign Groups to Roles, and that is where we stop -- we don't really use Profiles for much. So, why can't I assign permissions to a stamp by Role instead of by Profile or User. Every other permission I have encounted in DocuWare has the ability to assign permissions by Role, which is why I never took security to the Profile level (and I don't want to). Please advise.
    2. Removing a stamp. What if a user stamps and saves a document in error? I thought the stamp would be treated as an annotation such that it could be selected and removed (and it is treated as an annotation when it comes to printing), but that does not appear to be the case. I cannot select a stamp on a document even if I have not flattened it, and there does not appear to be any other stamp removal funcitonality. If someone made a mistake, we would have to save the page as a PDF without annotations and then replace the page via editing. That seems cumbersome. Any advice on removing a stamp placed in error?

     

    Thanks,
    Joe Kaufman

  • Bump

    Phil,

    Were you able to find anything out on this matter, including if something will change in a future version (if it hasn't already)?

     

    Thanks,

    Joe Kaufman

  • JSON

    Benoit,

    I have Fiddler up and running and it is showing me traffic to our DocuWare server (6.11 running on-premise, straight HTTP), but I am not seeing any XML. The XML pane is always empty, and instead, JSON is populated.

    How are you getting the web client to communicate via XML when doing something like changing an index field? All I see is JSON...

     

    Thanks,

    Joe Kaufman

  • Fiddler

    Benoit,

    That is a great tip. I recall using something to try to see what the web client was doing, but now I cannot remember the tool. I will take a look at Fiddler.

     

    Thanks,

    Joe Kaufman

  • Konrad,

    Konrad,

    I have found XML construction to be a bit finickywhen I am using Visual Foxpro and the ServerXMLHTTP request object. In some XML I have that looks similar to yours (defining "Field" values), I use these two lines as my XML headers:

    <?xml version="1.0" encoding="utf-8"?>
    <?xml-stylesheet type="text/xsl" href="/DocuWare/Platform/Content/standard.xslt"?>

    Let's see if I have a longer <Document> example...here's one:

    <?xml version="1.0" encoding="utf-8"?>
    <?xml-stylesheet type="text/xsl" href="/DocuWare/Platform/Content/standard.xslt"?>
    <Document xmlns:s="http://dev.docuware.com/schema/public/services" xmlns="http://dev.docuware.com/schema/public/services/platform">
        <Fields>
            <Field FieldName="{fieldname}">
                <{fieldtype}>{value}</{fieldtype}>
            </Field>
        </Fields>
    </Document>

    It looks like you might be lacking the second line in the XML headers, the one that establishes stylesheet type?

    If you are more familiar/comfortable with JSON, you might try that. It seems easier to construct, but I did not have much luck with it. But maybe I was not setting my request headers appropriately. JSON seems to be the thing a lot of web-based services are leaning towards, tohugh DocuWare still stores a LOT of stuff as XML in their back-end database (like embedded properties).

    Hope this helps. Getting Playform Service stuff working in anything other than .NET has always been a struggle from what I see on the forums.

     

    Thanks,

    Joe Kaufman

  • Carolynn,

    Carolynn,

    I wrote an expansive document on "power searching" involving wildcards, operators, and even arithmetic operators like "<" and ">".

    I can't post documents, though, and do not want to publicly post the document and link it here.

    If you are on LinkedIn (or something) can you let me know how to reach you there? We can exchange email addresses at that point and I can send you the document. It might be of help to you...

     

    Thanks,

    Joe Kaufman

  • (I work with Ron...)

    Phil,

    It would definitely be nice to know the outcome of this. In my opinion, if two out of three indexing spots hide the functionality on multi-cabinet results (even if the selected document is from the "primary" search dialog), then it should be hidden everywhere. The fact that it works for the primary but not for the others makes it all the more confusing, and just shouldn't be allowed now that we understand how a multi-cabinet result list is really sort of a nebulous. user-driven concept. To keep security intact and prevent confusion, it would be better if changing such indexes was not allowed across the board.

    Alternately, if multi-cabinet searches could be created at the configuration level (not user by user), then dialogs could be created and assigned privileges and everything would work as it should. However, it appears to be pretty ingrained (especially with regard to Platform SDK resource entry points) that dialogs are under a single file cabinet. My guess is that configuring multi-cabinet searches as persistent dialogs is not in the cards for a loooong time.

     

    Thanks,

    Joe Kaufman

  • Good point, as I am still

    Good point, as I am still trying to get my head around configuration in general. I quite like the desktop tools and tend to have trouble finding things in the web interface (and it feels a little more sluggish even though we are on-premise against a monster server).

    I might wait for 6.13 when some things at least get refined in the web client based on some of the feedback (like yours) that started when 6.12 was released to the cloud.

     

    Thanks,

    Joe Kaufman

  • OK, I might have to seriously

    OK, I might have to seriously consider upgrading from 6.11 to 6.12, just not really sure how to go about it (I have never installed any updates or hotfixes, and I am not the network infrastructure person at my company).

    Any advice on the best way to approach an upgrade? Is it something I should just open a support ticket for? My main issue is that we obviously can't do it during any times I am here, as that is when the system is live. Just afraid of what would happen if the upgrade gets botched and the system stops working. That's why we only upgrade systems if we really need something fixed or some new feature (everything else we custom build, so upgrades wre continual).

     

    Thanks,

    Joe Kaufman

  • Even Import Configurations?

    Even Import Configurations? That looks like it would have been a bear to convert to pure HTML5...

     

    Thanks,

    Joe Kaufman