Siebel Composer is an exciting new feature being introduced in Developer Preview mode in IP2015, the ability to develop Siebel in the browser and deploy changes in real-time is causing great excitement amongst Siebel customers.
Questions on the new Siebel Composer feature and IP 2015 Vs IP 2014
Q1) What are the changes from IP2015 vs. IP2014, with regard to GUI and OpenUI themes (Will “Aurora” still be there?)
A1) There are no significant changes in the GUI. Some bug fixes, a new theme (Simplified UI) and some new UI visualizations. Yes, Aurora is intact.
A1) There are no significant changes in the GUI. Some bug fixes, a new theme (Simplified UI) and some new UI visualizations. Yes, Aurora is intact.
Q2) How stable are the OpenUI themes? (e.g. “tangerine“ and “grey“ were de-supported in IP2014)
A2) We’re not expected themes to change significantly until at least IP2016. Themes need to keep up with time, so expect some changes. Following the Siebel Open UI Best Practices for theme development/customization will minimize the impact of changes to OOTB themes. Siebel Open UI Deployment Guide (Doc ID: 1499842.1)
A2) We’re not expected themes to change significantly until at least IP2016. Themes need to keep up with time, so expect some changes. Following the Siebel Open UI Best Practices for theme development/customization will minimize the impact of changes to OOTB themes. Siebel Open UI Deployment Guide (Doc ID: 1499842.1)
Q3) What’s the upgrade path for GUI customizations, e.g. are there changes in the CSS structure in IP2015?
A3) The class names themselves are mostly intact and we have backwards compatibility to IP2013 themes (even though we don’t ship the IP2013 themes), but Aurora is a brand new theme built from the ground up with Responsive Web Design in mind.
A3) The class names themselves are mostly intact and we have backwards compatibility to IP2013 themes (even though we don’t ship the IP2013 themes), but Aurora is a brand new theme built from the ground up with Responsive Web Design in mind.
Q4) Can (GUI) customizations be easily transferred to IP2015 or will there be enhanced effort to rebuild that stuff?
A4) As long as Siebel Open UI Best Practices for CSS Customizations were followed, effort to apply to a future Open UI release should be minimal. Rebuild would not be needed in this case.
A4) As long as Siebel Open UI Best Practices for CSS Customizations were followed, effort to apply to a future Open UI release should be minimal. Rebuild would not be needed in this case.
Q5) Regarding the existing use of OLE functionality and Siebel ActiveX components, because these will no longer be available with OpenUI, what alternatives are there?
A5) Browser based Java objects would be the best option for the short term. Note: most browsers are removing support for NPAPI later this year or with the next major release. So, java based/plugin based client side have a very short shelf life.
A5) Browser based Java objects would be the best option for the short term. Note: most browsers are removing support for NPAPI later this year or with the next major release. So, java based/plugin based client side have a very short shelf life.
Q6) Can you give any indication about the volume of the changes in IP2015?
A6) IP2015 is a smaller release, hence IRM based content is much smaller going from IP2014 to IP2015. It’s hard to put an exact number on it, but it is certainly smaller than IP2013 to IP2014.
A6) IP2015 is a smaller release, hence IRM based content is much smaller going from IP2014 to IP2015. It’s hard to put an exact number on it, but it is certainly smaller than IP2013 to IP2014.
Q7) How are Workflows being edited in Siebel Composer in IP2015?
A7) Workflows remain in Tools for IP2015, Siebel Composer is only being released as a Developer Preview in IP2015 and not intending to be fully functional just yet.
A7) Workflows remain in Tools for IP2015, Siebel Composer is only being released as a Developer Preview in IP2015 and not intending to be fully functional just yet.
Q8) How about Web Templates and Siebel Composer?
A8) Web Templates are migrated from SWT files to Tools metadata. Migration runs as part of the IRM process. Editing web templates in Siebel Composer in IP2015 is not recommended just yet, because it does not come with an intuitive facade, but in IP2016 this will be addressed when Siebel Composer is completely ready.
A8) Web Templates are migrated from SWT files to Tools metadata. Migration runs as part of the IRM process. Editing web templates in Siebel Composer in IP2015 is not recommended just yet, because it does not come with an intuitive facade, but in IP2016 this will be addressed when Siebel Composer is completely ready.
Q9) Will Siebel Tools still be enhanced?
A9) Focus is on Siebel Composer as the new development environment for Siebel. Hence Siebel Tools development will shrink over time as functionality from Siebel Tools is fully moved over to Siebel Composer.
A9) Focus is on Siebel Composer as the new development environment for Siebel. Hence Siebel Tools development will shrink over time as functionality from Siebel Tools is fully moved over to Siebel Composer.
Q10) What changes will happen to the SRF technology
A10) For the first couple of releases, the SRF mode will still be there, but it will support only the features that it supports today. All new features for Responsive Web Design, Deployment Agility, Siebel Composer, etc will be available in the no SRF mode.
A10) For the first couple of releases, the SRF mode will still be there, but it will support only the features that it supports today. All new features for Responsive Web Design, Deployment Agility, Siebel Composer, etc will be available in the no SRF mode.
