![]() Limitations of PeopleTools Component Interfaces and Web Services.When you are writing code against a Component Interface API, there is an important boolean property on the CI called EditHistoryItems. Component Interface EditHistoryItems Gotcha.Some indications of when you should be using CI. Signs you should be using a Component Interface.PeopleCode Events that do not fire in Component InterfaceĪ summary of the PeopleCode events that do not fire in Component Interface.Using ExcelTOCI to Delete a User ProfileĪ walk-thru for using excel to CI to call the DELETE_USER_PROFILE component interface.Should you create a new CI definition if one already exists? Should I Re-use An Existing Component Interface (CI) Definition Or Create A New One?.What Criteria should lead to the use of CI? Page and Component Interface: A WarningĪ warning about %page and Component Interface.ScrollSort and Component Interface Lost PointerĪn issue with ScrollSort and Component Interface. ![]() Should you expose a CI Definition as a web service?Īn example looking at CS Course Catalog Component Interface to use the Component Interface Find Method. Should You Expose a Component Interface as a Web Service.SQL audit to find problematic CI's for event mapping Find Component Interfaces with NO Menu Attached.New book chapter on table update strategies in PeopleSoft. Best Practices with PeopleSoft Table Updates and Inserts.New book chapter on strategies to integration with PeopleSoft. Strategies to Integrate with PeopleSoft.
0 Comments
Leave a Reply. |