Developers often fall in a dilemma where to start and how to start, when asked to develop an OAF application/module from scratch. Here are few guidelines which can make the developer’s work easier and help to build it faster.
Note : : Following are generic steps for starting an application. They may slightly vary as per the requirement.
Ø Database design should precede development
i) Tables must be ready
ii) Queries for all List of Values must be ready
iii) Queries for Common VOs must be ready
Ø Decide the required package structure, module wise, for all the modules in your application. See to it that the package is distributed to the lowest level possible to increase modularity and also ease the migration process. It also overcomes the integration issues by reducing the dependency.
Ø Create all the necessary EOs related to the tables that are required for the application. There should be only one EO per table and it should be reused for several VOs.
Ø Create Association Objects (AOs) ,if any, to establish relation between EOs.
Ø If you have any entity validations, create Entity Experts for all your EOs
Ø Create all the common LOV VOs in the LOV server package.
Ø Create one application module for containing all the LOV VOs
Ø Create LOV regions based on LOV VOs and attach respective COs to the regions if required.
Ø Create all the common VOs for your application.
Ø Create View Links (VLs) ,if any, to establish relation between different VOs.
Ø Create Application Module (The Application Module must be reused across pages. Create one application module per Application/Module based on the complexity. If the module is too complex, you may divide it into segments(set of pages) and create one Application Module per segment(s)). And attach all the VOs to the Application Module
Finally, create PG files and COs and attach the corresponding Applciation Module to the pages.