Prerequisites for IDM integration

Before you start integrating Document Management with SyteLine, ensure that these prerequisites are met:

• In an on-premises environment, the Application Event Service is configured to monitor the SyteLine site, as described in the SyteLine Multi-Site Implementation Guide. As part of this, ensure that each site which is monitored by the service has a configuration name defined on the Sites/Entities form, in the Configuration Name field. The name in this field should exactly match the configuration name.
• In a cloud environment, on the Sites/Entities form, verify that the value of the Configuration Name field exactly matches the configuration that you are using.
• On the SyteLine Document Types form, ensure that the document type PDF exists, with the pdf extension.
• On the SyteLine Report Options form, verify that every defined output type matches an extension shown on the Document Types form.
• In the Shared Groups tab on the Document Types form, for any document type that you want to send to Document Management (including PDF), ensure that appropriate groups are assigned to the document type. Then ensure that those groups are assigned to the users who will be generating the documents that are sent to Document Management.
• On the Event Handlers form, verify that an event handler called TaskPostPerform is defined and active.
• Ensure that users who will generate documents through these workflows have the IDM-User and IDM-RelatedInformation security roles, as well as the appropriate roles to access the SyteLine forms, assigned in Infor OS Portal or Infor Ming.le. Users who will view the generated documents in Document Management or the Related Information context app must also have the appropriate roles assigned. See the information about Document Types and their Assigned Roles in the administration guide help.
• If you have enabled TaskMan Options and set the value to debugrep on the Process Defaults form, then you must define a txt extension for a document type in the Document Types form. This setting should only be used for report debugging purposes, and must be removed as soon as testing is done.