Symptom
After a search, the default method of sorting is “Relevance” even though sorting by relevance is not possible here. Therefore, only a blank entry is permitted as the default value.
Reason and Prerequisites
This problem is caused by a program error.
Solution
Implement the attached correction instructions.
Symptom
Web Services Security UsernameToken Profile 1.0
The URI of the attribute /wsse:UsernameToken/wsse:Password/@Type is wrong.
Other terms
WSSEC 1.0, UsernameToken, Type attribute
Reason and Prerequisites
This optional URI attribute specifies the type of password being provided in the wsse:UsernameToken element. The pre-defined types are implemented with the wrong URI.
Solution
Apply the note.
The attached version of the simple transformation SEC_WSSE_USERNAMETOKEN is [...]
Symptom
@WebServiceRef is used without ‘name’
Other terms
WebServiceRef, web service client
Reason and Prerequisites
According to JAX-WS specification, @WebServiceRef doesn’t require ‘name’ attribute. The fix provides support for @WebServiceRef used without ‘name’.
Solution
Update to 7.20 SP01 or a subsequent SP.
Symptom
Perform Search on documents/Records and provide the value to any
of the multiple-valued attributes.
The Search result is displayed with the wrong value [ the value of the previous attribute in the search result ] in the multi valued attribute column.
Other terms
search, document, record, multi value, attribute
Reason and Prerequisites
While looping through the search result, a flag [...]
Symptom
You receive incorrect data for queries where the F-table has attributes of type DATE or TIME. You find the following entry in the trace of TREXIndexServer: “Attribute engine function not implemented (index attribute flags ) getAggregateMeasures”
Other terms
BWA, BIA, Accelerator, wrong result, date, time, not implemented
Reason and Prerequisites
Prerequisite: SAP NetWeaver [...]