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 |
Can you explain why is peoplesoft no longer supporting apache jserv?
When I create my component interface, why can't I see any Getkeys?
Architecture of CI? Or what are the main elements in the component Interface?
How should web application servers be used with peopletools 8.1x and peopletools 8.4 in ibm?
What are standard properties when a component interface (ci) is created?
Which are standard properties when a component interface (ci) is created?
Explain the various steps that describes the peoplecode logic while implementing a component interface?
Explain how does the people soft enterprise portal work with 8.1x and 8.4 applications?
In ibm how should web application servers be used with peopletools 8.1x and peopletools 8.4?
Tell me which data types is not supported by the peoplecode programming environment?
Explain which can be mapped as find keys for a component interface?
What are the main attributes of a Component Interface?