I've received a sufficient number of emails on Project Swan, our Release 12 user interface facelift, that we'll take another run at it today.
Just for fun, we'll do a few more before-and-after comparisons. Here's our Release 11i Login Screen:
Here's a draft of the Release 12 equivalent:
Here's a draft of the Release 12 equivalent:
Here's an existing Release 11i CRM/JTT screenshot for iSupport:
Here's a draft of the Release 12 equivalent:
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.
Migration Tools or Documents?
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).
Alternate Colour Schemes
A common question at last month's OAUG conference was whether we would support alternate colour schemes, since many of you distinguish DEV, TEST, and PROD environments with different colours.
Short answer: Yes, you'll still be able to customize colour schemes in the new Swan UI. It isn't clear whether we'll provide you with a preset selection of different schemes, but you'll be able to design your own.
Related Article:
The above is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision. The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle.
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.
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).
Alternate Colour Schemes
A common question at last month's OAUG conference was whether we would support alternate colour schemes, since many of you distinguish DEV, TEST, and PROD environments with different colours.
Short answer: Yes, you'll still be able to customize colour schemes in the new Swan UI. It isn't clear whether we'll provide you with a preset selection of different schemes, but you'll be able to design your own.
Related Article:
- Updated User Interface for E-Business Suite Release 12
- Native Sun Plug-In to Replace Jinitiator in E-Business Suite Release 12
The above is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision. The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle.
Comments (12)
Very nice to see Russian language on your screen :-)
If seriously, this blog is my favourite blog now.
I always want to know what happens with technology behind the Apps.
Thank you for your work!
Posted by Pavel V Luzanov | May 6, 2006 1:40 AM
Posted on May 6, 2006 01:40
You're welcome, Pavel; thanks for the feedback.
Regards,
Steven
Posted by Steven Chan | May 6, 2006 2:16 AM
Posted on May 6, 2006 02:16
Oh, I wish I could say, Richard. I can't yet, but will definitely post something here as soon as I get clearance to publish a date.Regards,Steven
Posted by Steven Chan | May 17, 2006 9:07 AM
Posted on May 17, 2006 09:07
Any idea what the release date is for version 12 Steven?
Posted by Richard Byrom | May 17, 2006 11:24 AM
Posted on May 17, 2006 11:24
hello steven,
what about Jinitiator, we'll always need to install it before being able to use the new interface ? it's not clear within your explanations.
Thanks for your answer
giao
Posted by giao | June 7, 2006 3:01 AM
Posted on June 7, 2006 03:01
Pierre-Mark,We plan to support the native Sun Java plug-in with Release 12; Jinitiator won't be required at all. See this article:Native Sun Plug-In to Replace Jinitiator in E-Business Suite Release 12You might be interested in other Release 12 posts summarised here:Release 12 Sneak PreviewsRegards,Steven
Posted by Steven Chan | June 7, 2006 9:03 AM
Posted on June 7, 2006 09:03
Steven, will release 12 simply be called that or is 12i still going to apply - which is correct?
Posted by Richard Byrom | June 8, 2006 5:01 PM
Posted on June 8, 2006 17:01
Richard,
So far, it's been called Release 12 in everything I've seen. If the marketing types decide to rename things in the final hours, I'll post an update here.
Regards,
Steven
Posted by Steven Chan | June 8, 2006 5:16 PM
Posted on June 8, 2006 17:16
Steven,
Do you have any idea what SWAN means? Is it an acronym, or just the idea of a wonderfully looking bird? Does it have any meaning? I cannot find anything about this on the web, and I am very curious.
Regards,
Arnoud
Posted by Arnoud Roth | March 23, 2007 3:07 AM
Posted on March 23, 2007 03:07
Arnoud,Project Swan was the internal codename for a wide-ranging series of Release 12 user interface changes, screen/form optimizations (such as tweaks in tab order, field names, placement, and so on). As far as I can tell, it was in direct reference to the waterfowl. At some point prior to the release of Release 12, this terminology started being used in external customer and conference presentations. Given human nature, it was only inevitable that "Project Swan" was eventually shortened to "Swan."By the time OpenWorld 2006 rolled around, the use of the term Project Swan (or even Swan) was being discouraged internally by some groups. I suspect the change in heart came from a desire to avoid the association with the tale of ugly ducklings. Now, we just refer to it as "the new user interface in Release 12." However, the old codename has been used so widely that residual remnants still linger out there, including here on my blog. I've left these references to avoid charges of historical revisionism, but I suspect that it's not really a point that many users spend all that much time reflecting on.Regards,Steven
Posted by Steven Chan | March 23, 2007 10:55 AM
Posted on March 23, 2007 10:55
Steven,
I am new to this all Oracle World and knowing about this change from 11i to R12 is quite interesting. However, I haven't been to find anything that tells me whether you can change this new look and feel as you are able to do in 11i.
I have just heard that all this look and feel is hardcoded.
Any additional light on this would be great!
Regards!
Mario
Posted by Mario Bagnara | August 21, 2008 7:54 AM
Posted on August 21, 2008 07:54
Hi, Mario,
There are several different ways of personalizing your EBS environment, depending on the types of changes you'd like to make to the look and feel. For a start, I'd recommend scanning through the Oracle Application Framework (OAF) Personalization Guide for Release 11i:
http://download.oracle.com/docs/cd/B25516_18/current/html/docset.html
This should be a good starting point.
Regards,
Steven
Posted by Steven Chan | August 25, 2008 10:10 AM
Posted on August 25, 2008 10:10