product tips

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.

CRM On Demand Technical Tips and Tricks: Javascript API - CRUD. Create, Read, Update and Delete records

CRM On Demand Technical Tips and Tricks: Javascript API - CRUD. Create, Read, Update and Delete records

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.

CRM On Demand Technical Tips and Tricks: Javascript API - Classes, Context, The Screen, Chaining Plus the Titlebar

CRM On Demand Technical Tips and Tricks: Javascript API - Classes, Context, The Screen, Chaining Plus the Titlebar

In this blog article we’ll discuss working with the JavaScript API more, including working with classes, context, the screen, chaining plus the titlebar.

Classes

Javascript doesn’t have classes!

Ok. So why discuss classes here?

Even though Javascript doesn’t have classes, there are ways to effectively simulate classes. The Oracle CRM On Demand JavaScript API does something like this class simulation, and classes “look” as you’d expect them too. They have properties and methods, just like other languages such as C++, Java, and Python.

CRM On Demand Technical Tips and Tricks: Javascript API - Storing Code

CRM On Demand Technical Tips and Tricks: Javascript API - Storing Code

In our first blog article in this series, you learned how to create a custom button with a canonical “hello world” program. In this article, we discuss options for storing your Javascript code.

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.

CRM On Demand Technical Tips and Tricks: Javascript API - Introduction and Buttons

CRM On Demand Technical Tips and Tricks: Javascript API - Introduction and Buttons

This post is part of a series of technical articles we are writing on the Javascript API. In this series, we will cover:

  1. Custom buttons.

  2. Storing your code, context, and the screen.

  3. Classes and chaining plus the titlebar.

  4. CRUD. Create, Read, Update and Delete records.

Modern CRM user interfaces, like Oracle CRM On Demand, are built on standards-based web technologies of HTML, CSS, Javascript, and JSON. This article outlines how to create a custom button in CRM On Demand which will launch will launch a canonical “Hello World” program. Let’s jump right into code and make it happen!

CRM On Demand Technical Tips and Tricks: Archiving

CRM On Demand Technical Tips and Tricks: Archiving

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.

CRM On Demand Technical Tips and Tricks: Performance

CRM On Demand Technical Tips and Tricks: Performance

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!