Tuesday Mar 26, 2013

Debugging Series: Fusion Applications Incidents

When a critical software failure occurs in Fusion Applications that is outside the remit of the functional product, the error handler code should call an API to generate a Diagnostic Framework (DFw) incident. The resulting incident record is identified by an Incident Number, unique to that WLS Server, and defined by its Problem Key, usually based on the error message such as ZCX-3075002.

[Read More]

Monday Mar 25, 2013

Debugging Series: Fusion Applications Logging

This article is intended to help developers working with Fusion Applications to leverage and implement logging in their custom code. Here we will illustrate how to use the same techniques and processes that exist in the standard product and its technology platform, as well as share a few tips-and-tricks.[Read More]

Friday Mar 22, 2013

Tip of the Week #1

This post is the first in a weekly series of short articles that provide you with hopefully useful tips for your development work with Fusion Applications.

In JDeveloper, to improve the productivity you may choose to open jspx and jsff pages in source mode by default instead of design mode. This can be done by following:

  • Go to Tools –> Preferences –>File types
  • Go to tab Default editors and change the value of the file types to source



Jspx and jsff files by default open in design mode and depending on the complexity of the page it may take some time to render them in the visual editor. However, most of the time developer needs to open jsff or jspx to just go to do non design tasks like navigating to the corresponding page definition file, looking into the page structure or doing simple changes in the page layout which can done in the source mode or in the structure window without the need to view the page in visual editor. Another reason is most of the time the page in the visual editor does not look like the actual page at all.


Monday Mar 18, 2013

Fusion Security: Overview

There is a wealth of documentation regarding security implementation for Fusion Applications; this series of articles is intended to collate information from various sources. The goal is to provide a high level overview of the implementation and components involved.

[Read More]

Monday Mar 11, 2013

Tailor, Customize, Extend, Personalize, Localize, and Integrate – All Explained

When discussing modifications to Fusion Applications many terms are often used by different people to mean different things, so it made sense to have a short post that helps confirm exactly what we mean by each of these. Please feel free to share to help everyone speak the same language.[Read More]

Monday Mar 04, 2013

Finding Code Artifacts for Customization (Part 1)

Customizations to Fusion Applications may be implemented at runtime (RT) using composers or design time (DT) using JDeveloper. In the former case locating the code artifact to be customized is implicit; we are in the context of the code artifact when we invoke the composer. The latter is more complicated as we may not know the name of the page / region to be customized. While JDeveloper allows us to search the EAR archive based on the name of the object, we are not able to search based on the content of the file (other than on the operating system level) nor are we able to view content of the page / region as it is presented through the application.

This series of documents is intended to illustrate the options that we have to map RT UIs to code artifacts and to inspect their structure.
[Read More]

Follow us on twitter Fusion Applications Extensibility, Customizations and Integration forum Fusion Applications Dev Relations YouTube Channel
This blog offers news, tips and information for developers building extensions, customizations and integrations for Oracle Fusion Applications.


« March 2013 »