We are back with the second article on Siebel Open UI usability improvements. In the first article, we set the stage and drafted your first steps in the Siebel UX transformation journey (e.g. making friends with the "digital" team at your company). Now we will continue by sharing different kinds of topics regarding the Nexus Bridge.
For the second year in a row I am leaving San Francisco and Oracle OpenWorld very excited. Last year Oleg and I started to work on the idea, which eventually became the Nexus Bridge for Siebel Open UI. This year I have presented the process for running Siebel UX improvements projects at the Siebel Customers Advisory Board meeting in San Francisco. Nexus Bridge is a crucial technical enabler in Siebel UX projects run by both by Idea Port Riga and several other customers.
This autumn, Idea Port Riga partnered with the Siebelhub team to share our vision about improving Siebel UX with you, the great Siebel community!
While working on this post, we came across the "CRM Technology Value Matrix 2019" by Nucleus Research. Their verdict that "Siebel CRM has the most breadth of capabilities," yet "the product falls behind in usability," perfectly matches our view on Siebel in 2019.
Siebel UX is not up to date. Siebel Open UI introduction in 2012 made it possible for Siebel customers to change Siebel UI's look & feel by modifying CSS and writing small pieces of jQuery code. By doing so, you can make Siebel look in accordance with the corporate brand book and slightly improve how users feel using the system. Still, these changes do not bring Siebel UX to the level users expect from web applications in 2019 when it comes to visual aesthetics and ease of use.
This article will guide you through configuring integration between SalesForce and DropBox, how to avoid user interaction to grant access to DropBox and also how to keep SalesForce notified about changes in DropBox.
There are some situations when you think it would be good to take files from DropBox, parse it in SalesForce and make some operations according to parsed data within SalesForce. Even more, it would be good if SalesForce could take required action right after the file has been changed or uploaded to DropBox.
Recently we were executing a memory usage analysis in my current (node.js) project. This article summarizes some of our findings, which may be useful to other projects. It does not describe the very basics of the mark-and-sweep garbage collection algorithm. Instead, it focuses on the details of the particular tools we used.
It’s not something new that Mobile Phones and Mobile Applications comes into our daily life, and they come not only as a tool for communication and entertainment. Many enterprises adopt mobile technologies to give their field workers ability to fulfill operations that previously could be done only in office.
Enterprise mobile applications are recognized as a separate class of mobile application. Microsoft outlines a set of features important to enterprise users and providing tools and practices to fulfill them.
Sometimes there is an urgent need popping up in the middle of an investigation of what is happening with your application server – e.g., a process is showing up, but refuses to serve network connections. There could be thousands of reasons why it is stuck, but one of the most common and a classic problem is deadlocked threads, i.e. threads that didn't share some of the resources on start-up correctly.
Suppose that weeks of developing business processes, building user interface and integrating Siebel with other systems are gone at last; implementation can be considered completed, and users have started to work with Siebel. There are no fatal bugs, nor annoying performance issues. Still, there can be something left to improve, specifically ergonomics of your Siebel implementation – and, possibly, efficiency of users' actions and operations in Siebel.
On one of my recent projects I’ve been asked to describe how our Restful API can be consumed by a third party service. In a SOAP world this task usually boils down to providing a WSDL, which can simplify understanding of exposed API, and can also be used for generating API clients in a most standardized manner.