Document Type (ttrpi2510m100)

The unique identifier of the document type.

The document type determines how the document is constructed and how it will be sent to one or more destinations.

If this check box is selected,, the document type is used for creating separate documents from a report that can contain data for different receivers. These documents must be distributed as well. If this check box is not selected, the document type can only be used to apply overlays.

If this check box is selected, the document type is also used to build up the documents if you choose Preview in the print session. In that case a batch with one or more documents is created. You can view those documents and distribute them. It is also possible to convert the batch (with the Convert Preview Batch to Distributable Batch (ttrpi3201m000) session) to a ‘normal’ batch to process the documents in the Document Rendering and Distribution (ttrpi3210m000) session.

The type of receiver to which the documents of this document type will be sent to.

Allowed values

• Business Partner

  Use business partner if the documents must be sent to business partners. In this case the distribution settings for business partners must be specified in the Document Output Management Details (tccom6170m000) session. Use this setting for invoices, requests for quotation, and so on.

• Contact

  Use contact if the documents must be sent to contacts. In this case the distribution settings for contacts must be specified in the Document Output Management Details (tccom6170m000) session. Use this setting if you want to be more specific in the distribution of your document, for example if you want to send a Sales Quotation to the specific contact, rather than to the business partner.

• Employee

  Use employee if the documents must be sent to employees. In this case the distribution settings for employees must be specified in the Document Output Management Details (tccom6170m000) session. Use this setting for timesheets, salary slips, and so on.

• User

  Use user if the documents must be sent to users; those are users that login into the /baanerp/baan system. In this case the distribution settings for users must be specified in the User Document Type Settings (ttrpi2551m100) session. Use this setting for user history reports, and so on.

• Custom

  Use custom if none of the other receiver types apply. In this case you must implement your own library to provide the destination(s) to which a document must be sent. This library must be specified here as well. For more information, see Infor LN Document Output Management User Guide.

Specify the period that documents of this document type must be retained when the Cleanup Batches (ttrpi3200m000) session is run and the documents satisfy all other selection criteria of this session.

The period can be specified in:

• Days
• Months
• Years

Use keywords to be able to find the created documents back in the Documents (ttrpi3510m000) session. The used keywords must be mapped to report variables in the Report Rules (ttrpi2520m000) session.

Zoom session which is used to get an overview of the possible values related to the keyword. This zoom session is activated if you search the documents in the session Documents (ttrpi3510m000) based on this keyword.

The field in which the zoom session returns the selected value.

If this check box is selected,, the document to be distributed is built up by multiple LN reports. The Print Production Order Documents (tisfc0408m000) session produces such a report. It is constructed by different LN reports, but the result is one physical report. Selecting this check box will do the same in constructing the documents to be distributed: data from different LN reports are merged into one document. If this check box is selected, you can also define Main – Addendum document relations through the Distribution Options of the report rules. If this check box is selected,, the Group by field must be filled.

This field defines how multiple sub-documents must be combined into one document. If the specified field changes during report processing, the sub-documents are merged to one main document. If the LN report is not sorted on the field you are using for grouping, do not select the Automatic Rendering check box. Automatic Rendering may construct the main document too early.

Allowed values

• Keyword 1 - 4

  All sub-documents with the same value for keyword 1 – 4 will be merged into one main document.

• Splitfield

  All sub-documents with the same value for splitfield (which is like the keywords mapped to a report variable in the Report Rules (ttrpi2520m000) session) will be merged into one main document.

If this check box is selected,, if you want to render the documents directly if they are created by the print session. If you do not select this check box, you must release the batch for rendering in the Batches (ttrpi3500m000) session. Note that to render the documents automatically, the Document Rendering and Distribution (ttrpi3210m000) session must run in daemon mode.

If this check box is selected,, if you want to distribute the documents directly after they are rendered. If you do not select this check box, you must release the batch for distribution in the Batches (ttrpi3500m000) session. Note that to distribute the documents automatically, the Document Rendering and Distribution (ttrpi3210m000) session must run in daemon mode.

Indicates whether the document must be digitally signed. A document must be signed if one of the report rules must be signed.

The signing type.

Allowed values

In Person

Documents are distributed after they have been manually signed by an authorized user.

Seal

Documents are signed automatically with a seal.

Indicates whether multiple documents can be signed together.

Allowed values

Yes

Multiple documents can be signed together.

No

Only one document can be signed at the same time.

When Viewed

Documents can be signed together, but must be viewed by an authorized user before.

Not Applicable

A signing condition to decide whether the document must be signed.

This field is optional.

If this check box is cleared, the "Publish Alerts” and “Alert Level” fields are disabled and show the values of the alert level settings from the parameters table. If this check box is selected, the "Publish Alerts” and “Alert Level” fields are enabled and you can specify a value.

When the BOD publishing public interface is not available, the alert settings cannot be changed and are not visible.

If this check box is selected, alerts must be published when a failure occurs in DOM. Alerts can only be published when ION is used.

The default value is "Not Applicable". Select an alert level:

• Batch
• Document
• Destination
• Not Applicable

When an alert level switches to failed and the Publish Alerts check box is selected for the document type, an alert is published. Depending on the alert level, document type specific or general, either a destination failure or document failure or batch failure publishes an alert.