On 28 October PeopleTools 8.52 is presented as generally available download via eDelivery. PeopleTools 8.52 is certified to upgrades for 8.9 and later applications. Release notes for PeopleTools 8.52 can be found here.

For a quick overview of this Tools release see previous post.

PeopleTools PeopleBooks is also available via this link.

The Attachment Framework is available within PeopleSoft for use with several vanilla parts. However, users usually want more places where attachments can be added to functionality. At this point technical people can be glad Application Packages are implemented into PeopleSoft these days, and moreover, that Oracle put the Attachment Framework into these objects.

As an example the usage of personal dossiers can be brought up. A breakdown of functional areas where all relevant documents of an employee can be placed in. Accessible for the employee and in some cases maybe for their manager or team secretary. In order to get something like this going I would need a record where the documents can be stored, a page where users can use this functionality and the Attachment Framework packages. A lot more functionality can be thought of to incorporate into something like this, but the basics are just this.

With PeopleTools you have the ability to create pagelets using the Pagelet Wizard. Pagelet Wizard pagelets, also known to the rest of the world as portlets, are small pages that provide display-only snapshots of applicable content which can be placed on the PeopleSoft Homepage. With the Pagelet Wizard you can create a variety of pagelets:

• HTML
• IB Connector
• Integration Broker
• Navigation Collections
• OBIEE Report
• PeopleSoft Query
• Rowset
• Search record
• URL

This post describes how you can get more control in formatting and setting up your HTML pagelets.

On 22 may 2011 Oracle released Oracle Fusion Applications R1 Beta version and was available for download from eDelivery. Yesterday (04 october 2011 ) at Oracle Open World 2011, Oracle announced general availibilty of Oracle Fusion Applications. This final version is now also available for download from eDelivery.

So what has changed from Beta to Final?

As a Peoplesoft developer (working with Peopletools-release 8.47.08), I have spent quite some time resolving issues caused by unexpected database-commits. As far a I know there’s no overall topic on this in Peoplebooks, therefore I will share my experience via this blog.

1) Database-updates via DML in a SQLExec-statement (e.g. INSERT INTO PS_TEST_TABLE VALUES(‘value_field_1′,’value_field_2′), triggered via an online component:
Peoplebooks states that DML in a SQLExec-statement is only allowed in FieldChange, SavePreChange, Workflow and SavePostChange events.
There’s a big difference in the outcome per event though; when this statement is put in a FieldChange-event, the DML is committed instantly, and this is something you probably don’t want!

2) Database-updates via DML in a SQLExec-statement (e.g. INSERT INTO PS_TEST_TABLE VALUES(‘value_field_1′,’value_field_2′), triggered via an Application Engine:
These updates are being committed according the AppEngine’s commit-settings.

2) Database-updates via a component interface, triggered via an online component (e.g. component A triggers component interface B_CI, triggering component B):
These updates are being committed as soon as the CI save-method is being invoked from the calling component (e.g. component A).

3) Database-updates via a component interface, triggered via an Application Engine (eg. AppEngine AE_1 triggers component interface B_CI, triggering component B):
These updates are being committed according the AppEngine’s commit-settings.
An exception to this rule I just recently encountered: the GetFile-statement leads to an immediate commit, even when used in an AppEngine-context!