• Seth,

    Seth,

    All of my code works against on-premise 6.11.

    I don't have anything else to test it on since I am just an end-customer, not a reseller/integrator...

     

    Thanks,

    Joe Kaufman

  • OK

    Tim,

    I will correct you, then.  *smile*  I just used my code (which uses the same core API method as Seth's code) to staple two documents together directly in a file cabinet -- no tray involved.

    I did get two 500 errors, the first because I tried to staple two non-PDF documents together (which apparently throws an error) and then another 500 error when I tried to staple together documents whose IDs did not exist in the file cabinet.

    Once I cleared up those error, I got a successfully stapled document, verified in the web client.

    I still do not know what a 405 error may indicate. The PDFs I stapled together were in a file cabinet with versioning turned on, and the operation still had no problem once I used the right type of documents (PDF) and used the correct document IDs. My code is below:

    =====================

            static public Document MergeDocuments(FileCabinet fileCabinet, List<int> docIds, ContentMergeOperation mergeOp = ContentMergeOperation.Staple)
            {
                // NOTE! This actually merges the documents in the DocuWare file cabinet, meaning a new, merged document
                // is created in the database and the documents that were merged are gone.
                LastError = "";
                if (fileCabinet == null)
                {
                    LastError = "Parameter 'fileCabinet' cannot be null.";
                    return null;
                }
                if ((docIds == null) || (docIds.Count == 0))
                {
                    LastError = "Parameter 'docIDs' cannot be null or of zero count.";
                    return null;
                }
                Document mergedDocument = null;
                try
                {
                    mergedDocument = fileCabinet.PutToContentMergeOperationRelationForDocument
                        (
                            new ContentMergeOperationInfo()
                            {
                                Documents = docIds,
                                Operation = mergeOp,
                                Force = true
                            }
                        );
                }
                catch (Exception ex)
                {
                    LastError = ex.Message;
                }
                return mergedDocument;
            }
     

    =====================

    As I said, it uses the same core API call Seth is trying to use, "PutToContentMergeOperationRelationForDocument".

     

    Thanks,

    Joe Kaufman

  • Zack,

    Zack,

    Interesting software. Sort of kludgey to use and no warnings or confirmations of what exactly is about to get stapled (I just stapled together a bunch of documents and now they are gone -- test data, but still).

    But it works. Seth, it worked on a test cabinet I had with versioning turned on. So, perhaps you want to try using it on the file cabinet you are having trouble with, and perhaps it will throw an error that means something more than the 405 error you are getting. Like I said, the software is not very user friendly, but maybe you will find it more intuitive than I did. The 30-day trial is free, so you can at least see if it works against the cabinet you are using.

    Other than that, I am not sure why DocuWare cannot provide more information on what the error means. I use similar code and it works for me, so it must be something with the particular file cabinet in play. Without add'l information about the error, though, that is going to be rather difficult to figure out. We shouldn't have to purchase third-party software to use an API call that is clearly documented in the .NET sample code.

    Can anyone from DocuWare weigh in on this?

     

    Thanks,

    Joe Kaufman

  • Any progress?

    Seth,

    Just wanted you to know I am back online here at the DW forums...  Any progress on the stapling issue we discussed on LinkedIn?

     

    Thanks,

    Joe Kaufman

  • By design

    Hello,

    I am not entirely sure of your question here, but what you are seeing is by design -- all DocuWare date/time fields are stored as UTC values, normalized to a universal time. This makes the data portable (and viewable) across time zones in a way that would not be otherwise possible.

    When you view such fields in the web client, they are converted back to your local time zone, as you are seeing.

    If you are accessing the data directly from the database, you need to calculate the UTC offset and adjust the date/times yourself if you want to see local time. Most programming environments handle UTC conversions in one way or another these days...

     

    Thanks,

    Joe Kaufman

  • Versioning

    Ester,

    Have you turned on versioning at the file cabinet level? That can be done in the web client by configuring a file cabinet.

    Once you turn on versioning I do not believe it can be turned off without deleting the file cabinet entirely and re-building it.

    Check in and check out will only appear for a file cabinet with that option checked.

     

    Thanks,

    Joe Kaufman

  • Separate print jobs?

    Josef,

    I was also thinking this was like scan configs, where we were part of a lengthy thread on that in March of 2017 (wow, time flies!):

    https://www.docuware.com/forum/english-forums/docuware-questions-about-usage-and-configuration/scanning-dynamic-import-config-barcode

    (And yes, it still stinks that identifying isn't performed on every page, because I see no downside to it and Fortis had the capability.)

    But then I thought this should be different from scanner-based configurations, because isn't each document sent as its own print job? That would mean documents are inherently separate and should identify individually. If a bunch of documents are printed as one "batch" job then identification would fail for all documents except the first one found to match a config, but a single document per print job should work.

    David, are you sending documents to the DW printer one by one, or as some sort of batch job? You say you "print a batch of different types", but I am not sure how that works. Are you saying you consolidate a bunch of different documents into a single PDF and then send it to the DW printer? Perhaps I am just clueless as to how the DW Printer batches things up -- I assume it is a separate document per print job, queued up like any Windows printer would.

    Thanks,
    Joe Kaufman

  • Callum,

    Callum,

    That works, but is this truly the new home of official DW documentation on the Platform? That is one weird link...

     

    Thanks,

    Joe Kaufman

  • .NET code

    Jose,

    The .NET help has some examples of merging documents:

    http://help.docuware.com/sdk/platform/html/7e48a8c5-4726-4f79-aeb6-885ec341c904.htm

    But it looks like the ContentMergeOperation only supports stapling and clipping.

    For pure attachments, I searched the URL resources page for the Platform service and cannot find the word "attach" anywhere on there. I have not done much with attachments, so I do not know the difference between attaching, clipping, and stapling.

    I also have not done anything with versions in the Platform service. But hopefully someone will weigh in, at least with some additional .NET examples.

     

    Thanks,

    Joe Kaufman

  • Link times out for DocuWare platform info

    Hey all,

    I used to be able to go to:

    https://docuware-online.com/DocuWare/Platform/Home/XSL

    to get help on the Platform SDK (general help, not just .NET stuff).

    This link appears to no longer work. I can change "docuware-online.com" to the name of our on-prem server and see the documentation from there, but that information is obviously version-capped to what we are currently running. If I want to look at something for 6.12 or 7.0 I am out of luck.

    Can anyone tell me where this content has gone or when the link above will be back up?

     

    Thanks,

    Joe Kaufman