ATTACHMENTS node
The
node of the Hansen8 configuration has these attributes:Attribute | Description |
---|---|
Attachment Default Sort Ascending | Indicates whether attachments are sorted in ascending order. If not, they will be sorted in descending order. |
Attachment Default Sort Column | Specify the column that will be used to sort attachments in the Attachments grid. Specify Title, Description, Filename, DocumentType, Created, or Modified. The default is Title. |
Attachment Stream Expiration | Interval, in minutes, before attachment information stored in Redis expires. |
Blocked Extensions | List of file extensions that are not allowed as attachments. |
Display Extensions | List of file extensions that Infor Public Sector will display in a browser window. For example, you may want to display image attachments such as .pngs in a browser window. If the extension of an attachment is not included in this list, it will be downloaded when a user selects it. |
IDM Execution Account (Windows Name) | Account that will be used if a Batch Manager task needs
to access Infor Document Management. For example, an
IDM provider might be used for a Process Attachment Links task, or an
IDM document output report might be used by a Correspondence Schedule
task. This is the Infor Federation Services ID associated with the user's Ming.le account. In Infor Public Sector this is shown in the Windows Name field in the User InfoViewer. |
Temporary EDMS Upload Url | Path to the directory where attachments are stored temporarily before being uploaded to an EDM provider. The path is relative to the Infor Public Sector application directory. |
Temporary Upload Url | Path to the directory where attachments are stored temporarily before being uploaded. The path is relative to the Infor Public Sector application directory. |
The
node can have two children: and .The Infor Public Sector User and Administration Library.
node defines configuration settings for the Process Attachment Links task in the Batch Manager. See "Batch Processing" in theThe
node can have these attributes:Attribute | Description |
---|---|
Agency Detail Moniker + Parent Bind | Comma-separated list of detail page monikers for which
attachment downloading is supported. For each detail page you must
specify the moniker and the bind to the parent component, in the form
Moniker:Bind. For example, for a service request
detail you would enter something like
InforClient.SRDtl.SRDetail:SRDetailKey.ServiceRequestNumber. Note: For
application details in the CDR modules, the parent bind must point
to the generic
Application object, not the
application object for the specific module. For example, the moniker
for a building application detail might be InforClient.BldgDtl.AppDtl:AppDtlKey.ApplicationDetailKey.BuildingApplication.Application. |
Allowed Domains | Comma-separated list of domains from which attachments may be downloaded. If you don't enter any domains, then all are allowed. |
Document Type | Document type that will be assigned to downloaded attachments. |
EDM | EDM provider to use for downloaded attachments. |
Enabled | Set to True to enable the attachment downloading functionality. |
Max Content Length (In MB) | Maximum file size for downloaded |
Request Timeout (Minutes) | Number of minutes before a request to download an attachment will time out. The default is 60 minutes.Maximum file size for downloaded attachments. The default is 1536 MB (1.5 GB). |
You can use the
node to restrict the MIME types that can be added as attachments. If you list one or more MIME types, then only those types are allowed. If you don't list any mime types, then all are allowed.The
node can have one or more MIME type nodes as children. Each MIME type node can have these attributes:Attribute | Description |
---|---|
Allowed Mime Type | MIME type that is allowed for attachments. |
Description | Description of the MIME type. |