Version 7.1 Doc Notes

See also: Release Notes for platform changes.

New Pages for Administrators

• Platform Installation Guide - Tells how to plan, install, configure, monitor, and tune the platform for maximum performance and security.
• Permissions Hierarchy - For Platform Administrators and other users, explains the restrictions on the ability to manage roles, users, teams, and other artifacts of the platform.

New Pages for Developers

• Composite Objects - Shows how to access and update multiple related objects in a single transaction.
• Application Architecture - Shows how the resources available in the platform work together to create an application.
• Lab Exercises - Short programming tutorials.
• REST APIs - Previously missing documentation has been added, along with new resources.

Documentation Changes

Improved Navigation

The navigation and categories panes have been restructured to make it easier to find the information you need. If you previously depended on search to get to pages, you may now find that you can "drill down" to the right page, just as quickly.

Improved Readability

Terms like JVM are now subtly highlighted with a light green, dashed underline. When you hover the cursor over such a term, a tooltip appears, giving a short definition.

New Terminology

These terms have been added to clarify administrative roles:

Term	Description
Platform Administrator	Someone who manages users, roles, applications, and other artifacts of an installed platform.
System Administrator	Someone who manages the installation, monitoring, and maintenance of the platform itself.

These have been added to clarify new platform features:

Term	Description
Composite Object	One or more objects joined by Object Relationships, and dealt with as a single transaction-safe entity.
Standard Object	The original platform object, which contains table data, forms, and operational methods, in contrast to a composite object (only used in discussions of composite-object transactions, when the distinction is necessary for clarity).

Terminology Changes

In order present a clear and consistent ontology (entities and their relationships) to developers and end users, several changes in terminology have been made. Those changes could throw you off, if you're used to searching for particular terms, so the changes are listed here. A couple of two terms have been added, as well.

Old Term	New Term	Description
system-generated objects	system objects	Pre-defined objects that come with the system.
objects	custom objects	Objects created when applications are installed or while they run. (So the generic term "objects" now refers to both Built-in or CRM Objects and Custom Objects.)
object identifier	object type identifier	Either an object's computer-generated objectID or human-designated objectName, either of which identifies the object, or type, (e.g. "User"), as distinct from the recordID, which identifies a particular instance of that type (e.g. "George").

Ontology Pages

To help new users come up to speed on the platform, a variety of Ontology pages have been created to elucidate the platform's conceptual terminology and the relationships among platform entities.

Tip: Whenever you dive into a new area of the platform, it can be helpful to review the Category:Ontology page relevant to that area.