Professional Documents
Culture Documents
Component Interface in Peoplesoft
Component Interface in Peoplesoft
What is a CI ? How it works ? Why use CI ? CI Architecture How to create a CI ? Setting CI security Testing a CI Sample PeopleCode Building APIs Runtime considerations
Why use CI ?
Loading data using CI mimicsonline data entry The data entered confirms to all PeopleSoft online validations and edits
CI Architecture
Component Component interfaces Component interface API
CI Architecture
How to create a CI ?
CI is a PeopleSoft definition that can be created in PeopleSoft Application Designer
Component (Search record) Search key fields Search key fields & Alternate Search key fields Physical key (provided the component has add-mode permissions)
Methods
Methods
A function that performs a specific task on a component interface at runtime Standard methods - Find, Get, Save, and Cancel methods The Create method for components that have the Add action enabled User-defined methods - Functions that are made accessible through the component interface. Each function maps to a user-defined method
Test in interactive mode. Retrieve history items. Test the standard, custom, and collection methods.
Programming CI in PeopleCode
Generating a PeopleCode Template
Open the desired component interface definition in Application Designer. Insert the component interface into a project. Save the project. Open the PeopleCode editor. You can associate component interface PeopleCode with a record, a component, an application message, or Application Engine. Select the component interface from the project workspace. Drag and drop the object from the project into the PeopleCode editor. Make any necessary changes to the PeopleCode in the PeopleCode editor window.
&oHcompinterface.HSKILLSET; rem For &<*> = 1 To &oHskillsetCollection.Count rem &oHskillset = &oHskillsetCollection.Item(&<*>); rem <*> = &oHskillset.HSKILLSET; rem &oHskillset.HSKILLSET = <*>; rem <*> = &oHskillset.RATING_SCALE; rem &oHskillset.RATING_SCALE = <*>; rem End-For;
/*If Not &oHcompinterface.Save() Then errorHandler(); Exit; End-If;*/ /*If Not &oHcompinterface.Cancel() Then errorHandler(); Exit; End-If;*/
Runtime Considerations
Win Message() is unavailable -> Use MsgGet() function Email From a Component Interface To use a component interface to send email, use TriggerBusinessEvent PeopleCode event, not Send Mail.
Multiple Instances of a Component Interface Because of potential memory conflicts, COM or C++ applications shouldnt create multiple, simultaneous instances of the same component interface, either within a single procedure, or in both a parent and a child procedure.
Summary
CI is a powerful integration tool Exposes a PS component for access from other third party applications (Java, C++,COM) Data load using CI mimics online data entry