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 |
Tell me where are workflow work items found?
Explain is bea weblogic the same thing as the web server that was previously on the tuxedo cd?
Tell me what http servers and java servlet engine combinations are supported with peopletools 8.4?
Explain which are standard properties when a component interface (ci) is created?
Tell me which data types is not supported by the peoplecode programming environment?
Which are standard properties when a component interface (ci) is created?
What are standard properties when a component interface (ci) is created?
Can you explain the various steps that describes the peoplecode logic while implementing a component interface?
My PeopleCode didn't update the value of a field. Why not?
Do you know for the servlet layer on the web server, what version of the java servlet api are the pia java servlets coded to with peopletools 8.4?
Explain will the peoplesoft internet architecture, now that it embeds bea weblogic and ibm websphere, work with my other corporate web servers and tools?
Why does my component interface not have a Create method?