Planned
2Committed and queued
More Placeholders for filenames/attachments
There are placeholders which can be used to create a filename for attachments in the sending profile. Eg. Order_Confirmation_{{DOCNUMBER}}.{{EXTENSION}}. The available placeholders are limited to fields in Structure /conlutio/ms_filename: This structure should get extend to also allow document or business partner specific fields to be replaced. Examples are: Sales: Customer purchase order number (VBAK-BSTNK) Customer: Shipper's (Our) Account Number at the Customer or Vendor (KNVV-EIKTO) It would further be very useful if customers could append own fields to /conlutio/ms_filename and to fill them with a new BAdI-Method.
Function to reset manual changes in the dialog
If manual changes are made to the e-mail in the dialog, no data determination is carried out for the changed parts. It would be desirable to have a function (button) to reset all manual changes and to replace the content with the automatically found data again.
In Progress
1Actively being built
Completed
15Recently shipped
Support file type in attachment profile for direct upload
There is a "file type" parameter in the attachment profile, but this is not used for the "direct upload" attachment type. It would be desirable to be able to use this field, for example, to only allow PDF files to be uploaded.
Corrupt files when loading from GOS
In rare cases, files in XML Office format (e.g. .xlsx, .docx) which are taken over from the generic object services are corrupted. The Microsoft Office programs can still open these files, but show a warning message. This problem is caused by unnecessary characters at the end of the file which are added during import. This error is corrected with Support Package 08.
SD maintain mail data during creation of document
Maintaining mail data during creation of SD documents not possible - error "No parameter found for organization unit !" --> During call dialogue organization unit not determined correctly --> check *-VBELN+00(01) NE '$' for LE, SD, SDBIL, TR in PREPARE_UI_WITH_DATA
Direct upload using an external archive system
The direct upload function currently saves uploaded files in a database table. This table can become very large under certain circumstances. There must be a possibility of storing the files in the external archive system (via Archive Linke content repositories) when using the direct upload function.
Display archived E-Mail from sending log
If an outgoing e-mail was archived there is now an easy way to open it from the sending history. Before that it was only shown in the generic object services. Clicking this function will open the EML-File and open it in the local mail client (e.g. Outlook).
New Cockpit Action - Forward in Outlook
If an email was already sent successfully and is listed in the cockpit transaction, there should be a new action button "Forward in outlook". When clicking this button a copy of the email with all recipients, subject, mailtext and attachments should open in Outlook, but the user can change it to forward it to somebody else. Update, function will be available in detail screen of sending log:
Changing language or partners displays wrong e-mail content
This is only a display problem (new UI) but should get fixed: Create a new document, e.g. an sales order Call the dialog of xtMail Suite one time and leave it again Change the partners of the sales order or change the communication language without saving the changes. Call the dialog of xtMail Suite again -> It still displays the data based on the partners or language of the first call. When sending the e-mail, always the correct data is used.
New sender type - reply-to address
E-mails can have an additonal "reply-to" address which might be different from the actual sender. This is a header field in the e-mail (https://en.wikipedia.org/wiki/Email#Message_header). The sender profile should be extended with a new sender type (with a fixed e-mail address) to set the reply-to address(es) in the header if it should be different from the sender address. . Preview Support Package 08:
Email recipient - fixed recipient
We already have several organizational units that in certain cases would like to send an email to the same email address that is independent of the document, e.g. in the case of a fall-back solution. So far we have solved this using the BAdI. However, we would like to forego the developments if there were also a fixed email address as the recipient type -> analogous to the organizational unit in the sender profile.
BCC Text is cut off when logon language is EN
The text for BCC is cut off when language EN is used for logon. This leads to a strange view. If the longer correct text is selected when changing, an error message appears.