/scripts/ahub.form.attachments.js
0

Message handling in SAP C4C Service

Mar 16, 2017 at 02:58 PM

273

avatar image

Hello All,

We have a requirement like to display some warning message on "Edit" of service ticket. And below are the ways we thought and the doubts.

1. Is it possible to add some action to "Edit" button in service ticket? If so where and how to add.

2. We added the logic to raise message in "AfterLoading" event of Service ticket. But here the raise message statement execution is giving the exception. Is that correct way to do?

3. In C4C, how the message is handled and where its collected. The standard error messages are persistent and able to see even when we come out and go in of Service ticket. Likewise is it possible to make the custom message stay in screen all the time.

Expecting the response asap.

Thanks,

Swadini S

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Danny Falss Jan 26 at 05:56 PM
0

Hi Swadini,

regarding

"1. Is it possible to add some action to "Edit" button in service ticket? If so where and how to add."

in c4c sales definitvly not - there no way to interact with that button (save button can be controlled within the BO TI)


" 2. We added the logic to raise message in "AfterLoading" event of Service ticket. But here the raise message statement execution is giving the exception. Is that correct way to do?"
You do not get an UI exception/backend dump when opening the object from the feed - you'll get a exception/backend dump when opening from a search.

I just verified this for c4c sales - object opportunity with a mass-enabled AfterLoading-event
As neither SDK compiler nor SDK help denies message raising here and it is working from the feed I have opened an incident for this.

So, I guess this is what you have done too, in afterLoading-event simple trigger a raise:

if (!Opportunity.yourIndicatorField) { 
	raise YourCustomDefinedMessageObj.Create("W");
}

"3. In C4C, how the message is handled and where its collected. The standard error messages are persistent and able to see even when we come out and go in of Service ticket. Likewise is it possible to make the custom message stay in screen all the time."

Afaik you would have to attach in a own Collection and raise the messages all the time in afterLoading or modifyAfter events to have them shown as system like messages.

Alternativly you bring them as textbox to the header or make a custom container for them; but the message(s) are not integrated into the message view


B.R.

Danny

Share
10 |10000 characters needed characters left characters exceeded
Skip to Content