WHAT WE THINK...
Most teams end up seeing an OpenUI implementation as 2 separate projects
The Web team needs to get an understanding of the concept and architecture of the PM/ PR before their web skills can be used. A silo-based approach only leads to question like –
Who does the Siebel side of the work?
Who does the web part?
What is part of the 'Siebel side work'?
I thought the ‘other’ team was doing this!
Siebel has 5000+ views available for you to “convert” to OpenUI. You need to figure which ones are 'useful'. A good start is to go with a 95:5 rule – I have evidence that 95% of the views in a person’s responsibility will never be used. Ask yourself if you REALLY need to show that view across 4 browsers?
A little bit of usage analysis goes a long way in figuring out which are your bread-n-butter views. Start your OpenUI project with those views, don’t try to do everything, come up with a low impact deployment plan.
Most likely you're looking at OpenUI because you already have Siebel. Are their processes that JUST DON’T work for your call centre users? Does it take too many clicks to get to the info they really need? NEWS FLASH! OpenUI will NOT make that go away. You will have to sit down and put effort into defining these processes first and then figure out how to use OpenUI to create that perfect user workflow.
Do you use scripts for all sorts of field and form validations? Could there be vanilla User Properties that could be used for those? If your Siebel App is not designed and configured properly, just migrating to and installing OpenUI is not going to magically fix those configuration issues."
"It takes forever to see the Quote Line Items on Chrome!'
'OpenUI is really slow!'
'It can't take that long to show me the pricing on an Order!'
Any or all of these sound familiar? Let me share a secret - Its NOT OpenUI! It’s your Siebel app! OpenUI will not fix the performance issues caused by bad application design or an un-tuned DB schema!
Upgrading to OpenUI is like adding extra gears to your bike. Sure it’s supposed to make it easier to use, but its not going to fix that flat tyre. You'll need to get that tyre replaced before you see the value of paying for some fancy new gears.
Developers may be itching to add animated views and flashing text… but again… do you really need it? Your users will quickly grow tired of the novelty. So, just because OpenUI lets you do it doesn’t mean you HAVE to do it.
Are you experiencing similar problems ? Well you are not alone ! So get in touch for a no obligation chat – we can help !