Attachment constraints

Attachment constraints limit the types of documents that can be attached to cases in Infor Public Sector and Rhythm for Civics. You can also use attachment constraints to require certain types of documents to be attached.

You can define attachment constraints for case types or for specific milestones. The constraints for a case type affect the Start Application process, and the constraints for a milestone affect cases at that milestone.

At a minimum, each attachment constraint specifies an allowed document type. If no attachment constraints are specified for a case type or milestone, then all document types can be attached.

To set requirements for a document type you can add a requirements formula to an attachment constraint. For example, your formula might use the MinimumRequired property of the Hansen.Core.Attachments.DocumentTypeRequirement object to specify the number of documents that must be attached at a particular milestone.

There are two other formulas that you can use to disable document type permissions for an attachment constraint. You can't grant any new permissions through these formulas, you can only disable existing permissions.

The standard permissions for document types are defined in two places:

For Infor Public Sector, document type permissions are defined in Access Control.
See "System Administration" in the Infor Public Sector User and Administration Library for more information about document types.
For Rhythm for Civics, document type permissions are defined in the Portal Configuration grid in Document Type Setup.
See the Infor Rhythm for Civics User and Administration Library.

For example, the standard portal permissions for a certain document type might allow customers to delete attachments in Rhythm for Civics, but you might not want to allow customers to delete documents from a particular case type. You can use a portal permission formula to disable the Delete permission for portal customers.