SAP C4C Enhance Account Search

[Former Member]

As you see,I want to enhance Account Search and find & use a Enhancement Option,but when I searched account in SAP Cloud UI for testing, no breakpoint is entered.

So，do I choose a error Enhancement Option or anything I should do in advance？

Looking forward to your reply...

[JayantSaini]

Hi Baoxiang,

Have you wrote any ABSL code inside the enhancement option and assigned a breakpoint to it?

Thanks

Jayant

[Former Member]

Hi Jayant,

of course,I raise a message which is defined in .enht and get into debug model after setting a breakpoint

[HorstSchaude]

Hello Baoxiang,

I am puzzled: Does the breakpoint work or not?

Second: If you read the docu from the Repository Explore you will find that the related BO is the "UtilitiesExtensibility" and not the "Account". 😞

Bye,
. Horst

[Former Member]

Hi Horst,

Thanks for your reply,

First ,the breakpoint didn't work if I use "Enhancement Option: UtilitiesAccountSearch"

Second, I find that the related BO is the "UtilitiesExtensibility" but I can't understand the mean of "UtilitiesExtensibility" ,especially "Utilities".

Finally and most important, If I want to achieve my demand that enhance Account search,what can I do?

[HorstSchaude]

Hello Baoxiang,

Okay, so forget the Enhancement Option.

Please take a look at How to Add Extension Fields to Standard Queries with Key User Tools (HTML 5) or at How to Add Extension Fields to Standard Queries with Key User Tools (Silverlight).

HTH,
. Horst

[Former Member]

Hi Horst,

Thank you for answering so many questions to me and solved many of my problems.

But in this problem I think you may be not understand me,maybe I didn't make myself clear.

I want to filter data(custom or standard ) before I get into OWL view according to some logics, but not add some extension fields to standard queries and then fill these extension fields to find data.

My point is automatically filling in the default values for the query field.

Look forward to your reply

Baoxiang

[HorstSchaude]

Hello Benny,

Okay, got it.

But this is not possible. 😞
The Extensibility Explorer of the UI Designer does not support any extension into a DefaultSet of a standard query.

Sorry,
. Horst

[Former Member]

Hi Horst,

Thanks for your reply.

So,my custom BO query can be supported ?

For example,I use ABSL code to make my expression clearer.

//Before I get into OWL view set queryfield value
MyCustomBo.queryfield.A = "A1";
MyCustomBo.queryfield.B = "B1";
//Then when I get into OWL view, system will only show data(A="A1" B= "B1") in my OWL view
//I want to use ABSL code to control queryfields value 

[HorstSchaude]

Hello Benny,

Sorry, no. 😞

The OWL is filled based on the result list of a query. This query has a DefaultSet which can be defaulted via settings in the UIDesigner (as showed in blog from Pradeep). The result list contains node IDs for which a Retrieve is executed.

ABSL scripts are only executed in the resp. event

• AfterModify
• BeforeSave

Don't mix this up with the DefaultSet defaulting via Transformation Definitions based on Customer Reuse Functions realized in ABSL.

HTH,
. Horst