Siebel IP17 – Statement of Direction

ip17sod

It has been released, the yearly ‘Statement of Direction’ – for many regarded as a ‘State of the Union’ for Siebel – for the release to come. That will obviously be Innovation Pack 2017, to see the daylight around April/May next year. John Bedford posted on Oracle OpenUI blog last week about it.

The full details can be found per usual on Oracle Support:

Innovation Pack 2017 (17.0) for Siebel CRM Statement of Direction / Planned Features (Doc ID 2179185.1)

For sure, Innovation Pack 2017 first and foremost is focused on Siebel Composer, Siebel Composer and again Siebel Composer. The one and most import design theme, at the roots of Siebel as we have known it over the past two decades. IP15 and IP16 have presented ‘developer previews’ and after two years in infancy, innovating and maturing – it will be the real deal in Innovation Pack 2017. And no, Siebel Tools will not cease to exist – and a lot of activities will still be managed through Siebel Tools. Scripting, Workflow, Incremental Repository Merge, … it will remain in Tools. Don’t be fooled.

The Workspaces – no-more-local-database – introduced with Innovation Pack 2016 will become default. And for that Workspaces will be enhanced to allow for full multi-level branching, to support parallel, multi-release development. I say will allow because it certainly will require very strong governance, not getting lost at the same time. Governance and overseeing ongoing developments will become even more important than it’s today. So: Lead Solution Architect: be prepared!

Composer and Workspaces lay out the foundation for agile development with Siebel better than ever before. But agile development also requires (regression) test automation, ideally on a daily basis. It has always been the Achilles’ heel and never an easy task, relying on 3rd party software such as Oracle’s Application Test Suite. Since a couple of years Oracle has been using internally a Selenium-based solution for regression testing of all OpenUI applications using a Keyword-driven framework build around Selenium. This has matured and it’s good to see it surface in the Statement of Direction. It will create only a loose dependency with Selenium, where all test scripts/suites and executions are managed and stored in the Siebel database.

And yes, Siebel becomes elastic where finally one would be able to dynamically provision a new Siebel Server in an up-and-running Siebel enterprise at zero-downtime. Though this feature is reserved for customers deploying on Oracle’s Public Cloud infrastructure.

To close off, Siebel REST API will be enhanced to support Swagger for service description. As well, REST API will be more dynamic in terms of ability to describe on the request the needed output (e.g. child entities and fields required). Great!

– Jeroen

PS: This might become my final post on the Oracle Implementation Advisor Blog…

 

 

 

 

 

 

 

Advertisements