The only Peoplecode events you should be using

最新推荐文章于 2023-11-14 23:22:23 发布

WTK870424

最新推荐文章于 2023-11-14 23:22:23 发布

阅读量965

点赞数

分类专栏： peoplesoft 文章标签： events components notifications behavior validation

peoplesoft 专栏收录该内容

203 篇文章

订阅专栏

本文聚焦于在PeopleTools中高效利用代码事件，推荐95%代码应部署在组件级而非记录级，详细介绍了关键事件如ComponentPostBuild、ComponentSavePostChange等，并指明了避免使用的事件，旨在提高开发效率。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

The only Peoplecode events you should be using

When designing pages and components in PeopleTools, there are many different peoplecode events that you can use. In fact, there are too many options. We write alot of PeopleCode and here is our opinion of where 95% of your code should be. You generally want to place 99% of your code at the component level and not at the record level.

PeopleCode events to use

Component PostBuild
- For code you need to trigger once when the component loads.
Component SavePostChange
- For updating other records and sending notifications after the transaction has committed.
Component Record FieldChange
- For record field change peoplecode. Add it at the component level always not at the record level. If you need the same behavior across components, then create a function.
Component Record RowInit
- For logic you need to trigger when a row is loaded from the database. Add it at the component level always not at the record level. If you need the same behavior across components, then create a function.
Component Record SaveEdit
- For enforcing valid fields and such. Notice we do not add it at the component record.field level. We have every piece of validation logic in one event so it is easier to modify later.