WHEN SHOULD I BE USING A COMPONENT INTERFACE?
If you need to insert/update/delete data through PeopleCode, and your PeopleCode will require replicating a lot of existing business logic that already exists in a component then a component interface is the best approach. Once you learn how to use them, they will be the fastest and most robust solution for such cases. If you are performing simple changes, then using a CI becomes overkill as there is an overhead to using a CI on both the system and on development time. Similarly, large amounts of batch processing may be too much for a CI to handle or may be considerably slower using a CI.
| Is This Answer Correct ? | 0 Yes | 0 No |
Explain is bea weblogic the same thing as the web server that was previously on the tuxedo cd?
Tell me which data types is not supported by the peoplecode programming environment?
Tell me what are the status available in peoplesoft domain status menu?
In ibm how should web application servers be used with peopletools 8.1x and peopletools 8.4?
What are the main attributes of a Component Interface?
Tell me can a peopletools 8.4 and a peopletools 8.1x database run on the same machine?
When I test my component interface, why do I get a "Not Authorized" error?
Explain which are standard properties when a component interface (ci) is created?
Explain why is peoplesoft no longer supporting apache jserv?
Why does my component interface not have a Create method?
Tell me why did peoplesoft bundle ibm websphere advanced single server edition rather than advanced edition?
Explain the various steps that describes the peoplecode logic while implementing a component interface?