This release provides the ability to trigger documents to be generated and sent automatically following events, and to send the documents to an email, SFTP or server location
In the current version of this feature, Final Invoices (FIV) and Disbursement Invoices DIV) can be triggered to send to a destination by Job events
Use the screen in Administration -> Document Management -> Document Autosend to set up which documents are sent, when autosending happens, and where the documents are sent to
Documents can be set to either send the stored, unarchived versions that exist in Documents tabs of Jobs, or Expedient will be able to generate and send the document from the Job Documents tab.
In this current version, where Expedient is sending a Final or Disbursement Invoice, the invoice must be posted before Expedient will send a stored version of the document.
For example, the screenshot above shows that Expedient will send any unarchived documents with ‘DIV’ document code stored to Jobs.
Select the event, or set of events, that must occur in the Job before the document is triggered to be sent. Select ‘All’ or ‘Any’ to determine if all events in a set, or a single event in a set must have occured
For example, the screenshot above shows that the DIPD and IPRN event must both happen before the Disbursement Invoice DIV is sent out.
If Expedient is unable find a stored document, or cannot contact the destination for the documents, an error message is sent to the email addresses listed in the screen above. The message will contain details of the document and the job where the autosending could not be completed
The Interface tab shows the final destination for the documents in the front tab.
Select to send the documents listed in the front tab to an email address, to an SFTP location, or to a directory on the server
As the events occur in Jobs, Expedient will check at configured time intervals, if there are any documents that should be triggered to be automatically sent by the events.
Expedient will create an event, code DCAS, in the Job to confirm that the AUTOSEND process has happened.
Where a document could not be sent, because a posted and stored invoice did not exist, or the destination could not be found, an event, DCAF, will indicate the failure
The events screen, available from Job Registration, will show further details of automatically sent documents. Use the ‘Recipients’ button in the Events screen to see how the document was transferred
The configuration screen has a toolbar button link to the Document ID Masterfile, so that autosave configuration can be easily updated
In later updates to Document Autosend, Expedient will add more documents that can be automatically sent and expand the ability to send the documents to external parties e.g. clients