Report Rules - Check In To Document Management

Hi Oliver,

I don’t think you can easily do what you want right now, assuming there is no document with the same Doc No as the invoice number at any given time the report rule is run.

The code that handles the "archiving" of the report/PDF has two "paths", you could say. Either you provide a document number, or you don't, and two different paths are taken.

If you provide one, and a document with that number exists, then a new revision is created and the PDF is checked in to it (assuming database storage is used for the document class in question). You can try this by manually creating a document with an invoice number you know, and then print that invoice.

If you don't provide a document number, well, then it works like what you have seen, that a new document is created and the PDF is connected to it.

So, the problem is that you want to combine these two pieces of business logic, but they don't work very well together.

In order to get new revisions of the same document created, you need to provide a document number, but you don't have that the first time the report is printed. And to get the document created in the first place you need to leave out the document number.

Something that might work is to set up a custom event that, when certain invoices are created (you need to find a good triggering point), then an empty document is created, with the document number set to the invoice number. Then, you have a report rule that sets the document number. Then, since the document exists, the "add new revision" logic should kick in.

Worth trying, perhaps?

/Mathias