This is the last of a series of four articles that will explain the enhancements to Oracle CRM On Demand in Release 27 (R27). This article’s focus is on the updates to CRM Integration Tools. In this article we cover:
Welcome to the ActivePrime Blog
In our blog, you’ll find helpful and informative posts dedicated to improving CRM performance and usability. Our topics include deep dives on the technical aspects of CRMs like searching and data quality. You’ll also find insightful posts about user productivity and adoption.
In our first three blog articles in this series you learned the canonical “hello world” program, options for storing your code, and reviewed the API classes including Context, Screen, TitleBar and the concept of chaining.
In this blog article we’ll discuss CRUD; creating, reading, updating and deleting records. Our last article included a review of making changes to on-screen values, meaning there is programmatic access to object fields values that are being shown on the CRM On Demand UI (User Interface). However, what about when a field is not being displayed on the UI? For instance, if on Account objects the District Office is not displayed on the UI, and you want to work with the data in that field, this is where CRUD operations come in handy.
Ok. So why discuss classes here?
Two Options for Storing Code
The first option is to store the code as a client side extension in CRM On Demand, as discussed in our first blog article. The main benefit of using client side extensions is that Oracle handles everything about the storage. There is no need to worry about having a separate web server with proper configuration of HTTPS; there are no SSL certificates to purchase and configure. The disadvantage is that any changes you make to your code must be loaded separately into each CRM On Demand system that you have. For Oracle partners with many customers, this can be cumbersome.
Storing your code, context, and the screen.
Classes and chaining plus the titlebar.
CRUD. Create, Read, Update and Delete records.
Archiving in Oracle CRM On Demand means different things to different users. It may mean removing attachments to free up space to keep your allotments in check. Or, archiving may mean removing records from the workflow. It could also mean a clean up unused Accounts, Contacts, or Leads to improve CRM performance and usability. Some believe that data is power, and therefore no data should be archived, while others strongly believe that irrelevant data is distracting. It's important that precedents are set for how to purge data from your CRM, especially as your business grows. There are limits, or allotments, to the number of records and attachments you can create before Oracle will ask you to purchase more storage.
Performance: per·for·mancenoun \pə(r)-ˈfȯr-mən(t)s\ : an activity (such as singing a song or acting in a play) that a person or group does to entertain an audience : the way an actor performs a part in a play, movie, etc. : the act of doing a job, an activity, etc. Source: Merriam-Webster Dictionary
Although some may refer to their CRM as a complicated performance, what they are really driving at is its performance. Confusing?
Some users complain that their experience with the CRM is hindered by poor performance; what they mean is that page load times are slower than expected.
We live in an instant gratification world, no doubt about it. We click and we expect. We don’t wait. We give up when page load times are longer than a couple of seconds. It is no wonder the CRM Admin constantly gets emails, texts, and calls that there must be something wrong with the CRM system because pages take too long to load!