more than 50 char email subject to SAP inbox

[Former Member]

Hi Guys,

I have the ff email reqt in my workflow:

1. Subject with more than 50 char

2. Message URL with more than 80 char

3. Message text in bold

I cannot address all 3 when using send mail step so I created an activity step instead and call my method that made use of CL_BCS class.

But it seems like I cannot make use of it because I'm sending my email to SAP Inbox.

Subject with more than 50 chars works only when sending outside SAP, as per note 698087.

Is there a solution for this?

Can I send an email to SBWP with more than 50 char?

Please help me out, as I already exhausted all possible solutions I found on the net.

I also implemented snote 0001523530 but it doesn't work.

Thanks.

[Former Member · Accepted solution]

Since the requirement is for this to be sent to SAP Inbox, they had decided to shorten the subject to 50 characters or less.

[ronen_weisz]

I would  try to bypass the problem.

If you are using cl_bcs already, why not send an email? all the requested subjects, urls and bold will work, and users usually prefer to receive mails to their regular email account.

Another option is to send a task which calls a screen, this also should give you the requested options.

[Former Member]

Hi Ronin,

I am sending an email to someone's SAP inbox.

It has to be in SBWP because part of the message is a Web Dynpro link they need to review and approve.

Yes, the more than 50 character subject works if I'm sending the email to a regular email account but not in SBWP.

Can you elaborate the second option that you mentioned?

By the way, my email is triggered by a WF and is executed in background.

Thanks.

[ronen_weisz]

Hi,

If you need the users to approve something, this is a task not a mail (mail been only informative)

Tasks subjects are not limited to 50 chars, you can add links to decision tasks by attaching objects and as you said yourself in bold chars will work in the SAP business workplace.

The second option I mentioned was to use a task which method calls a screen (to be more exact - calls a function module or a program which calls a dialog screen), and then you have all the options since this is a regular ABAP screen.

P.S

The extended notifications which inform users of waiting tasks is using a BSP application, in it html tags work very well.

Ronen

[Former Member]

Hi Ronen,

Thanks for the info.

But it needs to be an email because there are informative texts, along with the WD link, that needs to be sent to the approvers. And the action is on the Web dynpro, the approvers need to click a button there, not on the WF's user decision. Then I will trigger a terminating event in my WD in order for the step to be completed and proceeds to the next.

I actually made use of CL_BCS, because of send mail restrictions on the text format and lengths.

I guess I cannot use the second option because the task is in background.

Thanks.

[ronen_weisz]

If it's an email - why not send it to the regular (outlook/lotus notes etc.) email there you do not have any restrictions on the length / url / bold chars when using cl_bcs?

And why is the task a backgroud task? a lot of workflow task are approved by events and not directly in the workflow inbox (asynchronous tasks), even in WD you can easily raise an event to end the task.