KUMAconnect#
General#
With the APPs "KUMAconnect" and "KUMAconnect Output Link" you have an integration interface that connects the DMS/ECM of ELO Digital Office GmbH (professional and enterprise) directly with Microsoft Dynamics 365 Business Central1.
For this purpose, an ELO2 client, the "ELO2 Integration Client", is directly integrated into numerous fact boxes and / or page parts of Microsoft Dynamics 365 Business Central1. This allows working directly in Microsoft Dynamics 365 Business Central1 with the ELO2 DMS/ECM. Files and documents can be archived by drag & drop.
With the "KUMAconnect Output Link", documents created in Microsoft Dynamics 365 Business Central1, e.g. order confirmations, invoices, etc. can be archived directly in ELO2 DMS/ECM without further intervention. All files and documents are automatically tagged with appropriate metadata. For a business process or a transaction in Microsoft Dynamics 365 Business Central1, these are then displayed by the Integration Client directly in the filing structure in ELO2.
The app communicates with an ELO2 DMS/ECM system using modern web services. For this purpose, a KUMAconnect APP is also installed in ELO2 DMS/ECM so that the two systems can communicate directly with each other.
In addition, standard templates are provided that contain a complete configuration of the Integration Client, the outgoing documents, the metadata and the archive structure including the reference structure. An authorization concept rounds off the templates. The functional scope and operation of the ELO2 Integration Client can be accessed via the link.
Facilities for ELO2 are set up in the ELO2 Admin Console. Here the metadata is defined, the storage paths and reference paths. Please contact your ELO2 partner for this.
Setup#
DMS Setup#
Before the Integration Client is displayed in the Fact Box or in the Page Part, the app requires the following settings in order to be able to communicate with the ELO2 archive. This setting is first made in the "DMS General Setup" page.
| field | description |
|---|---|
| ELO Rest API URI | Here the URI of the REST API of the connected ELO2 system is stored. The rest API is used to archive documents in the background in ELO2. Example: http<s>://<server>:<<port>/rest-<<archive name>/ |
| ELO username | name of the ELO2 service user through which the Rest API is allowed to communicate. |
| ELO Password | Password for the ELO2 service user |
| KUMAconnect Fact Box activated | This switch activates or deactivates the KUMAconnect interface. If it is active, the Integration Client is displayed in the Fact Boxes or the Page Parts |
| Display of the client in lists | The Integration Client can also be displayed in many list pages. Here it should be noted, however, that scrolling within the list may be somewhat delayed if the Integration Client is active in the list pages. This can be turned off across the board using this switch |
| Use Single Sign On | With this switch the Windows credentials are transferred to ELO2 for automatic login when the Integration Client is called. |
| ELO Integration Client URI | The base URI of the ELO2 Integration Client is stored here. Example: http<s>://<SERVER>:<PORT>/ix-<ARCHIV>/plugin/en.elo.ix.plugin.proxy/wf/apps/app/elo.integration.Client/ |
| Auth with oAuth2 | Logging in to ELO2 can also be done via OAuth, this can be enabled here. |
| ELO oAuth2 URI | Here URI of the OAuth authorization point is stored. Example: login.microsoft.com/common/oauth2/v2.0/authorize? |
| Fact Box Height | What height should the fact box be in all pages or page parts? Default: 500px Info: the width cannot be configured. |
| KUMAconnect archiving of outgoing documents activated | Here you generally activate whether documents created in Business Central should also be transferred to the ELO DMS/ECM. Which documents these are is set in the following "Document setup". |
Note
If you have KUMAVISION medtec365 in use, you have further setup options and functions available at this point. You can find more information about this topic here.
User setup#
Users who are to use KUMAconnect must be assigned an ELO2 profile in the "User setup". The profile is configured in the ELO2 archive. Here, for example, it can be configured that the ELO2 web client and not the ELO2 full client is called up for the function "Open in ELO". Or that the function "Edit in Office" is available to the user. So open the "User Setup" in Microsoft Dynamics 365 Business Central1 and go to the row of the corresponding user. If the user does not already exist in this setup, simply add him/her.
In the column "ELO Profile" (often on the far right of the table) you can then select the ensptechende user profile. If no "ELO profile" is entered in the cell, this user cannot use KUMAconnect and the integration client is not displayed.
Note
If the column "ELO profile" is not displayed, the general setup is not yet complete.
DMS Document setup#
You can open the DMS Document Setup via the call "Configuration of Report Archiving" in the menu ribbon of the DMS Setup. Via the "DMS Document Setup" you can control at which event the source document should be uploaded to the ELO2 archive in the background. The events are taken into account, if the archiving of the source documents is activated in the "DMS General Setup".
Note
Please note that the call is only available to you if the switch "Use report ID to identify documents in ELO" is deactivated. This function switch is available from KUMAVISION KUMAconnect version 2.1 or higher on ELO2 side.
| Validity area | The department can be set here. Depending on the department, other outgoing documents can be configured. Possible validity areas: - Warehouse - Purchasing - Sales - Service - Reminder . |
| Table of records | A record is related to an outgoing document. For each output document, the field "Archiving on event" can be used to control when and whether it should be archived. Possible values are: - Do not archive - Processing outside of KUMAconnect (Only relevant for Special Industry Solutions) - When printing - When sending e-mail - When printing or sending e-mail - When releasing - When posting |
The following output documents are configurable:
| Range | Table ID | Table name | Document type |
|---|---|---|---|
| Sale | 36 | Sales header | Offer |
| Sale | 36 | Sales header | Order |
| Sale | 36 | Sale header | Invoice |
| sale | 36 | sales header | credit |
| sale | 36 | sales header | Blanket order |
| sale | 36 | sales header | complaint |
| Sale | 36 | Sales header | Draft Invoice |
| Sale | 36 | Sales header | Proforma invoice |
| Sale | 110 | Sales delivery header | Output |
| Sale | 112 | sales invoice header | invoice |
| Sale | 114 | Sales credit memo header | Credit memo |
| sale | 6660 | returns header | returns |
| Purchase | 38 | Purchase header | Inquiry |
| Purchase | 38 | Purchase Header | Order |
| Purchase | 38 | Purchase header | Invoice |
| purchase | 38 | purchase header | credit note |
| purchase | 38 | purchase order header | framework order |
| Purchase | 38 | Purchasing header | Complaint |
| purchase | 120 | purchase delivery header | receipt |
| purchase | 122 | purchase invoice header | invoice |
| purchase | 124 | purchase credit memo header | credit memo |
| purchase | 6650 | return delivery header | return delivery |
| Service | 5900 | Service header | Quotation |
| Service | 5900 | Service header | Order |
| Service | 5900 | Service header | Invoice |
| Service | 5900 | Service header | Credit note |
| Service | 5900 | Service header | Output |
| Service | 5965 | Service Contract Header | Contract Offer |
| Service | 5965 | Service Contract Header | Contract |
| Service | 5992 | Service Invoice Header | Invoice |
| Service | 5994 | Service credit memo header | Credit memo |
| warehouse | 7316 | goods receipt header | goods receipt |
| warehouse | 7318 | goods receipt header | goods receipt posted |
| Warehouse | 7320 | Goods issue header | Delivery |
| Warehouse | 7322 | Goods issue header | Posted delivery |
| Dunning notice | 295 | Dunning notice header | Dunning notice |
| Dunning notice | 297 | Registered dunning header | Dunning notice |
DMS Report setup#
You can open the "DMS report setup" by calling "Configure report archiving" in the DMS setup menu. The DMS report setup can be used to control which event should cause a report to be uploaded to the ELO2 archive in the background. The events are taken into account if in the "DMS Setup" the switches "Archive outgoing documents" and "Use report ID to identify documents in ELO" are activated.
Note
Please note that the call is only available if the switch "Use report ID to identify documents in ELO" is activated. This functionality is available from KUMAVISION KUMAconnect version 2.1 or higher on ELO2 side.
| Table with records | A record is related to a report. For each report you can control when and if it should be archived via the field "Archiving on event". Possible values are: - do not archive - processing outside of KUMAconnect (Only relevant for special industry solutions) - when printing - when emailing - when printing or emailing - when releasing - when posting - when posting asynchronously. |
After installing the app, all reports supported by KUMAconnect by default are already preconfigured. Further reports can be added individually. It should be noted that these must also be configured on the ELO2 side.
Integration Client Activation#
In this setup you can select whether the ELO2 Integration Client should be displayed in the Fact Box or in the Page area or not at all on this page.
Note
In pages of type List the ELO2 Integration Client can only be displayed as Fact Box.
| field | description |
|---|---|
| Page ID | ID of the page where the ELO2 Integration Client should be embedded |
| Page Name | Name of the page on which the ELO2 Integration Client should be embedded |
| Enabled | The following selections are available: - Disabled - Factbox - Page Party - Factbox and Page Part |
The Integration Client can be activated on the following pages:
| Pages ID | Pages Name |
|---|---|
| 20 | Personal account |
| 21 | Accounts Receivable |
| 26 | Accounts Payable Card |
| 30 | Article card |
| 39 | Fibu book.sheets |
| 41 | Sales quotation |
| 42 | Sales order |
| 43 | Sales Invoice |
| 44 | Sales credit note |
| 49 | Purchase request |
| 50 | Purchase order |
| 51 | Purchase Invoice |
| 52 | Purchase credit note |
| 88 | Project card |
| 130 | Sales delivery charge |
| 132 | Sales invoice |
| 134 | Sales credit note |
| 136 | purchase delivery charge |
| 138 | purchase invoice |
| 140 | Purchase credit memo |
| 254 | Purchase ledger sheets |
| 434 | Reminder |
| 438 | Registered Reminders |
| 507 | Frame order |
| 509 | Frame order |
| 1171 | User task |
| 5050 | Contact card |
| 5159 | Sales order archive |
| 5162 | Sales quotation archive |
| 5164 | Purchase request archive |
| 5167 | Purchase order archive |
| 5600 | Purchase order archive |
| 5768 | Goods Receipt |
| 5900 | Service order |
| 5933 | Service Invoice |
| 5935 | Service credit note |
| 5964 | Service quotation |
| 5972 | Posted service credit note |
| 5975 | Posted service delivery |
| 5978 | Posted service invoice |
| 6050 | Service contract |
| 6053 | Service contract quotation |
| 6620 | Frame order archive |
| 6623 | Frame order archive |
| 6630 | Sales complaint |
| 6640 | Purchase complaint |
| 6650 | Posted return delivery |
| 6660 | Posted return delivery |
| 7330 | Posted goods receipt |
| 7335 | Goods issue |
| 7337 | Posted goods issue |
Note
If you have KUMAVISION medtec365 in use, you have further setup options and functions available. You can find more information about this topic here.
Document buffer#
If an error occurs during the transfer of documents created in Microsoft Dynamics 365 Business Central1, this document is temporarily stored in the "Document Buffer" table.
Possible causes are that the ELO2 system is not accessible, e.g. it is being maintained, or there is an error in the configuration of the archive structure in ELO2. If the transfer event "on release" is used for a document, this document is always stored temporarily in this table. The background is a locking behavior of Microsoft Dynamics 365 Business Central1.
Normally, the table should be empty. If this is not the case, the background job that performs the processing may not have been activated. This table will be filled if there was an error or a block during the transfer of the source documents to the ELO2.
| field | description |
|---|---|
| Mode | Type of record |
| No. | consecutive number |
| Number of errors | Number of attempts to resend the faulty document to ELO2 using the task queue. If there is always a 1 here, the task queue is probably not set up for this. (See Setup background job) |
| Last Error | which error occurred during the last transmission. Here can be for example the following messages: - getArchivingSubFolder ... "the ELO2 filing structure is missing in the ELO2 software" - preparePrintout ... "data record for the structure could not be determined by ODATA" - no document service found ... "no document was defined for the usage in the document service in KUMAconnect" |
| Table ID | Transfer came from table |
| Record ID | Transfer was made for the record with the ID |
| Page ID | Transfer came from the page with the ID |
| Parameter string | What other parameters were used in the transfer to enable archiving in ELO2. Example: {"tenant": "kumaconnectqs", "company": "CRONUS AG", "systemId": "Warehouse Shipment Header:{B95B9BD8-33FD-EC11-9949-9087C1D55CB9}", "objectId": "Table Warehouse Shipment Header", "referenceId": "Page 7335", "usage": "KVSDMS Whse. Shipment", "keys":{"No":"AUSG000005"}} |
Setting up a background job for the document buffer#
The background job to be set up via the task queue items monitors the DMS document buffer. If there are entries here and the background job performs a new processing.
The following settings must be entered for the new job:
| field | description |
|---|---|
| Type of object to be executed | Please select code unit |
| ID of the object to be executed | Please select here the code unit with the number 5593405 |
| Label of the object to be executed | KVSDMSSendFaultedDocuments |
| Description | A free description can be entered here |
| ... further fields | Further fields are described in the help of Microsoft Dynamics 365 Business Central1 Online Help |
-
Microsoft, Microsoft Dynamics, and Microsoft Dynamics 365 are trademarks of the Microsoft group of companies. ↩↩↩↩↩↩↩↩↩
-
ELO, ELOprofessional, ELOenterprise, ELOoffice and ELO ECM-Suite are registered trademarks of ELO Digital Office GmbH in Germany and/or and other countries. ↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩