Regardless of the level of security provided for both facilities access, and for electronic access, if the data being accessed is not encrypted, then there’s a gaping hole in security. Encryption, both of data in transit and at rest fills this hole.
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.
There must have been many times when you have wanted to collaborate on a project or include others on a conversation to get their input, but ran into roadblocks such as limited email, outside suppliers or unsecured instant messaging. This is the “collaboration gap”, and it has wasted lots of time and money. Here are a few typical scenarios….any look familiar? “I need an approval for this image and then I can send out this email campaign. The Sales Manager is anxious to get this out so that his sales team can start pursuing these leads. Once I get the image approved I need to check with Accounting to make sure we are up to date on our subscription to the image supplier. I wish there was a way to keep all these project centered conversations together and everyone who is interested informed on the progress.”
Many of you have asked for the ability to mass update fields within CRM On Demand, above the 50-field limitation. And you'd like to schedule these changes at off-peak hours. Some users have had to export data into a spreadsheet, manually update it, and then re-import it, which is time-consuming and prone to errors. Users need an easy way to switch all the Accounts owned by a sales rep to a new one. Or update the same field for a whole slew of Opportunities, instead of one at a time. Users have also requested the need for picklist options to ensure that data integrity is maintained by forcing a user to select only those options that are valid.
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.