Changelog

Follow new updates and improvements to conlutio.

March 24th 2023

New

Bitte beachten Sie, dass wir nur noch bis Juni 2023 Informationen über diesen Kanal veröffentlichen. Bitte nehmen Sie sich 1 Minute Zeit und registrieren Sie sich für unseren Newsletter, wenn Sie weiter Update-Informationen erhalten möchten:

https://www.conlutio.de/service/#newsletter

Please note that we will only publish information via this channel until June 2023. Please take 1 minute and sign up for our newsletter if you want to continue receiving update information:

https://www.conlutio.de/en/service/#newsletter

The support package 11 for xtMail Suite Version 500 is available now. Changes are ...

New:

  • Department and department description is now shown in contact persons dialog

  • Deletion of "direct upload" attachments is now supported when stored in external archives

Improved:

  • Change: Performance for MM cockpit improved

Fixed:

  • Dummy Partners (NG_GET_DUMMY_ADRNR) didn't work for module V7

  • Various stability improvements

Type @ to mention posts

December 5th 2022

New

The support package 10 for xtMail Suite Version 500 is available now.

New:

  • Full support for BOM explosions to find attachments (MM only)

  • Success message in output type log, if mail was processed by xtMail Suite

  • UI recipients list - new columns for contact person function and department

  • New Parameter KOMPBV1 (item data) for /CONLUTIO/IF_XTMS_BADI_NG method KOMKBV1_FILL

  • New Parameter KOMPBV2 (item data) for /CONLUTIO/IF_XTMS_BADI_NG method KOMKBV2_FILL

  • New Parameter KOMPBEA (item data) for /CONLUTIO/IF_XTMS_BADI_NG method KOMKBEA_FILL

  • New Checkpoint group to analyse attachment determination (Transaction SAAB)

Improved:

  • Performance for V3 cockpit improved

  • Jumping to documents from purchasing cockpit always in "change"-mode now

Fixed:

  • Module QM - Workpapers were not determined correctly sometimes

  • Module QM - communication language determination improved

  • Module MM - Maintaining maildata in ME31L and ME31K is now possible without opening output types before

  • Module FI - 2410 Balance Confirmation extended for Vendor / Language from KNA1/LFA1

Other:

  • Internal changes and improvements for a future release

Type @ to mention posts

November 14th 2022

New

The support package 09 for xtMail Suite Version 500 is available now. While it mostly contains bug fixes, there are also a few new features

New Features:

  • New recipient type (G) for a fixed e-mail address

  • New recipient type E (accouting clerk)

  • New attachment type P for archived original files (created by print and archive)

Improved Features:

  • New parameter KOMPBV3 (item data) for /CONLUTIO/IF_XTMS_BADI_NG method KOMKBV3_FILL

  • Recipient type N (NAST) supports personal numbers (e.g. ZM) now

  • Support for access sequences with constants in dummy output types

  • Support for new S/4HANA 2020 data model for storing GOS Attachments, when determining file extensions with more than 4 characters

Fixed:

  • Correction for the switch to xtMail Suite in V7 print programs (method S4_SWITCH_PDF)

  • Recipient type N (NAST) found too much recipients, if no default-address was maintained in partner

  • Signature for sender type F (accounting clerk) was filled with wrong data

  • Empty filename for attachments type O (GOS) in rare situations (if TOAAT-FILENAME is empty)

  • Contact persons with no partner function were not found (new bug from 500-08)

  • CC flag in dummy output type condition recipients was not reseted for further addresses

  • Access sequences in dummy output type with non-character fields could cause a dump

  • Purchasing cockpit: Navigation to contracts and scheduling agreements are working now

  • Purchasing cockpit: When maintaining e-mail data, partners were determined incompletely

  • When using print preview in ME21N, a dump could occur in NG_CHECK_RECIPIENTS_EXIST

  • When using the new direct upload to archive (function from 500-08) in Create-Transactions, a dump could occur

Please write a mail to support@conlutio.com if you want access to the new support package.

Type @ to mention posts

May 6th 2022

New

The support package 08 for xtMail Suite Version 500 is available now. These are the changes in this release:

New Features:

  • Attachments from the "Direct upload" function can now also be stored using a document type. This way attachments are visible in the Generic Object Services after upload, and they can be stored in an external archive server instead of table /conlutio/msattu. A migration report to move old attachments from this table to the archive is coming soon.

  • Direct upload function can now be limited to specified file types (https://conlutio.featurebase.app/submissions/60bb7601caccca00138b742f)

  • xtMail Suite can now be used for new FI BTEs:

    2310 Correspondence / Periodic Account Statement

    2410 Customer Balance Confirmation

  • Additional Reply-To Address can be set now (https://conlutio.featurebase.app/submissions/60bdf279caccca00138b8494)

  • Enduser languages are fully re-translated for the following languages: German (DE), Englisch (EN), French (FR), Italian (IT), Spanish (ES), Simplified Chinese (ZH), Slovakian (SK)

  • Signatures with text-symbols to replace user information, is now working when sender-address is set from BADI method

  • Improvements in handling legacy data after switching from old customizing to sending profiles.

Fixes:

  • Fixed a bug causing corrupted files in some rare situations (https://conlutio.featurebase.app/submissions/62469b4a5a389f571a15520d)

  • Fixed an issue when double clicking in attachment list opened the wrong attachment

  • Fixed a problem when trying to maintain mail data while creating a new document in SD (error "No parameter found for organization unit !")

  • Fixed a short dump when a print program tried to send an email for the same NAST record more the once (e.g. output type with "Copies" Parameter > 1).

  • Fixed a problem when calling the print preview in MM documents, which could cause a short dump.

  • If only one recipient exists, the email address of the recipient is displayed directly in the sending log again.

Type @ to mention posts

December 13th 2021

New

UI:

  • New: Display archived EML-File from sending log without using GOS (Details)

  • New: Function to forward/repeat an e-mail in Outlook (Details)

  • Bug Fix: Fixed a short dump (ITAB_DUPLICATE_KEY) that could rarely occur when calling the xtMail Suite dialog from sales orders.

General:

  • New: Support for output type KONS in module MR (document header BKPF instead of RBKP)

  • New: Support for medium 7 output types is available in all modules now.

  • Bug Fix: Fixed a problem when adding GOS attachments from old BADI

  • Report /CONLUTIO/MSDUNNINGDOC is checking standard authorizations F_MAHN_BUK, F_MAHN_KOA, V_VBRK_VKO and V_VBRK_FKA now, before reading dunning documents and outgoing invoices.

  • General stability and performance improvements

Type @ to mention posts

September 14th 2021

New

Dialog:


  • New: A completly new determination analysis is introduced now which is available for the new user interface (Details)
  • New: It is now possible to set the mailpriority when changing an email to High/Medium/Low) (Details)
  • New: When viewing an e-mail which was already sent and if this document has an archived main document (e.g. the purchase order PDF document), double-cklicking the main attachment will display it now.
  • Bug Fix: When calling the dialog multiple times while changing date of the document wrong data was displayed in some cases. When sending the e-mail the data was always correct. This is fixed now. (Details)
  • Bug Fix: The BCC text in the recipients dialog was cut-off in logon language EN. (Details)
  • Improved messages when trying to delete an attachment from the attachment list.



General:


  • Bug Fix: With support package 05 a bug was introduced which is fixed again now. The Sender of an email was not the expected email address and/or you have set the xtMail Suite sender as the recipient, but this recipient address cannot be found. (500-05-#001)
  • Bug Fix: You are using xtMail Suite BAdI NG method SET_RECIPIENTS_NG with sender profile and new GUI, but the recipient(s) changed via BAdI are not displayed in xtMail Suite dialog. If the e-Mail is send the recipient(s) changed via BAdI are correct . With this fix the changed recipient are also displayed correctly now (500-05-#002)
  • When sending profiles with new UI are active, less old (unnecessary) coding will be performed now. This improves performance and stability of xtMail Suite.
  • The old Parameter NGFIRST which was only used by a few customers is now obsolete. When using the new UI the function is turned on always now. Basically it just says that sending profiles have to be maintained to use xtMail Suite - otherwise the mail is not send with xtMail Suite. With this the behaviour is more predictable and always linked to existing customizing.
  • Better error handling in case that attachments stored on a external archive system are unreachable.
  • If the sender is the purchasing group, a reverse search is carried out using the e-mail address in order to determine an associated user. The user is required to enrich the signature. With this change locked users are no longer taken into account in this search.
  • Structures for text symbol replacement in V1, V2, V3 and V7 are filled more reliable now.
  • More preparations for a new translation of xtMail Suite. (Details)
  • Some additional small bug fixes and improvements.
Type @ to mention posts

September 14th 2021

New

Sometimes it is difficult to find out why certain parts of an email were found (or not found). With the new determination analysis, which is available from Support Package 06, there is now a new tool that makes the analysis of the origin of the data much easier.


The determination analysis can be called up from the maintenance of the mail data and provides information on all components of the e-mail.




Type @ to mention posts

June 6th 2021

New

Dialog:

  • New column "file size" in attachment list (Details)
  • New column "recipient full name" in recipient list (Details)


General:

  • It is now possible to archive the outgoing E-Mail in EML format (Details)
  • The customizing was cleaned up and is now focussed on the send profiles.
  • Profile names have been extended from 8 to 16 characters
  • I18N: Preparation for an updated translation of the UI (Details)
Type @ to mention posts

June 6th 2021

New

Starting with support package 05 it is possible to archive outgoing e-mails in EML format in the generic object services. This format can be opened in Outlook (and many other e-mail programs) and shows the complete e-mail with all its attachments. This means that the e-mail can also be forwarded from Outlook.


You can find the settings in the customizing for the xtMail Suite under Send Profiles -> Outlook Integration. These are advanced settings for the send parameters, so you should have previously maintained Send profiles per application and organizational unit.




In general, the EML generation is switched on by activating the GOS switch. A document type can optionally be given.

  • If you leave the Document type field empty, the EML file is stored as a normal attachment (comparable to services for objects -> Create -> Create attachment)
  • If you maintain a document type that was previously customized in transactions OAC2 / OAC3, the EML file is stored as a Business Document (comparable to services for the object -> Create -> Store business document)


If you want to use a document type, you may have to make the file type EML known in transaction OAD2. In this case, use the MIME type message/rfc822.


Type @ to mention posts

June 6th 2021

New

General:


  • The attachment profile supports attachments from DMS as source again
  • Drag'n'Drop for attachments is blocked in display mode now
  • Fixed searching the last editor of a QM document via change documents
  • Better handling of item level output types when new UI is active


Cockpit Transactions:


  • Double click on a MM contract works now correctly
  • The name of a partner (NAME1) was determined wrong in some cases in the cockpit mail list
  • Bug Fix: Role ZM (Personnel Number) is now determined correctly when maintainance dialog is called from cockpit transaction
Type @ to mention posts