Current Siebel Adapter Explorer (iWaySM 55 SP1) (and likely other adapters) does not allow the user to filter the fields before generating default schemas for later exposing insert,update,delete,query operations as web services.

The result is that for example the Account Siebel object (Sales app) shows up with close to 300 fields!!

One way to approach this problem would be to define processes for each operation to use transformation agents to reduce the list to a manageable list.
Any best practice comment on this would be greatly appreciated.

Thanks

Hi cmanjarres,

This is forwarded internally and here is the suggestion: Currently, the Siebel adapter is limited in it's conditional logic handling. The division has reviewed a specific case and has deemed it reasonable to approve a new feature to enable the adapter to accept special characters in parameter values such as “GT” for > and “LT” for <. This modification to the adapter is planned for an iWay release after Service manager SP2. There are ways around the adapter limitation which involve custom Seibel business components, process flow logic [transformations etc) and custom Java agents.

Hope this helps.

Cheers,

Kerry