The Swan UI brings together some of the
best UI concepts from Oracle E-Business Suite, PeopleSoft, and JD Edwards
applications. This new look and feel applies to the whole Oracle E-Business
Suite (OAF, JTT (CRM) and Oracle Forms 10g products). The internal
codename for improving the user interface was "Project Swan".
So the "R11-Duck" has
been changed into a nice "Swan".
Converting From Previous Versions
If you've customized or extended Release 11i screens according to our published customization standards, there shouldn't be significant effort involved in getting to the Project Swan look-and-feel. This is expected to vary a bit by the type of screen.
Oracle Applications Forms
Project Swan changes for Forms are limited to changing the color scheme and using non-boldfaced fonts for field values. These changes will be made in the technology layer, so no changes need to be made by Forms designers. There will be no change to the position or layout of any fields on the forms.
Oracle Applications Framework Screens
In most cases, no code changes will be needed, since the cosmetic changes will be implemented at the OAF technology layer. There may be specific cases where the use of custom stylesheets may require additional tweaks.
CRM/JTT Screens
Like OAF, in most cases, no code changes will be needed, since the cosmetic changes will be implemented at the technology layer. There may be specific cases (e.g. custom renderers, custom stylesheets) that require additional tweaks.
If you've customized or extended Release 11i screens according to our published customization standards, there shouldn't be significant effort involved in getting to the Project Swan look-and-feel. This is expected to vary a bit by the type of screen.
Oracle Applications Forms
Project Swan changes for Forms are limited to changing the color scheme and using non-boldfaced fonts for field values. These changes will be made in the technology layer, so no changes need to be made by Forms designers. There will be no change to the position or layout of any fields on the forms.
Oracle Applications Framework Screens
In most cases, no code changes will be needed, since the cosmetic changes will be implemented at the OAF technology layer. There may be specific cases where the use of custom stylesheets may require additional tweaks.
CRM/JTT Screens
Like OAF, in most cases, no code changes will be needed, since the cosmetic changes will be implemented at the technology layer. There may be specific cases (e.g. custom renderers, custom stylesheets) that require additional tweaks.
Given that the vast majority of existing screens should automatically be uplifted to the Swan UI, I haven't yet been told whether there will be tools to aid in conversions. It's likely that we'll provide you with the same internal Swan conversion guidelines that E-Business Suite product teams are using today (albeit with better spell-checking and grammar).
What is the abbreviation of SWAN
ReplyDeleteSWAN? Full form
ReplyDelete