Oracle Sales Cloud

Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracles products remains at the sole discretion of Oracle.
Copyright 2014 Oracle and/or its affiliates. All rights reserved. |
Oracle Confidential Internal/Restricted/Highly Restricted
Oracle Sales Cloud

Implementation Partner Workshop
Configuration and Customization
February, 2015
Topics covered in this deck

Configuration and Customization
PaaS
Copyright 2014 Oracle and/or its affiliates. All rights reserved. | Oracle Confidential Internal/Restricted/Highly Restricted
Configuration and Customization Topics

Get Oracle
Sales Cloud
Initial Setup
Learn Core
SFA + SPM
Learn about
Data
Shapes
Configure &
Customize
the
Application
Administer
Key Areas
Integrate
with Other
Systems
How do you extend the product to meet your customers requirements?

How do you handle and test extensions and customizations before actually applying
them?
What Customization and Configuration features are available?
How can I make pages different for different groups of users?
When I need more complicated logic, what scripting support is available?
How do you migrate setup and customization data from one environment to an other?
What features of Customization and Configuration can we expect in the next release?
Any reference material?
How do you handle and test

extensions and customizations
before actually applying them?
Full Lifecycle Support

Business Analysts
Model Processes
Administrators
Extend the product
Implementers
Set-up Sandbox &
Environments
Business Owners
Tailor processes
Team
Measure, analyze,
improve, govern
Business Users
Collaborate and
Innovate
IT Operations
Manage, Deploy and Monitor
Lifecycle Management
Implementation Project
Go-live
Sandboxes
Sandbox Topics
Get Oracle
Sales Cloud

Initial Setup
Learn Core
SFA + SPM
Learn about
Data
Shapes
Configure &
Customize
the
Application
Administer
Key Areas
Integrate
with Other
Systems
What are Sandboxes

When to use Sandboxes
Why Sandboxes
Sandbox Operations
Integration Sandboxes
Tips & Considerations
What are Sandboxes?

Containers holding temporary copies of configurations and
customizations
Created by developers to make and test customizations

Mainline is the source of data and definitions used at the time of creating a
new sandbox
Clearly Sandboxes help isolate and control customization efforts without

impacting mainline where end users are working
Typical flow:
Setup Private(Testonly) Sandbox
Setup
Extend
Configure and
extend application
as per the
requirements
Test customizations
without publishing
Test
Prepare
Get approval for the
changes and
prepare to roll out
(Integration
Sandbox)
When to use Sandboxes

Any change made to the application that impacts Metadata
Services artifacts

Customizing/extending pages, objects, attributes, etc. using Application

Composer
Setting up security for custom objects
Any changes made using Page Composer
Changes made to the application using Setup and Maintenance (FSM)
Why to use Sandboxes?

Out-of-the-box functionality to help isolate and control customization efforts
without impacting other sandboxes and mainline users' configuration and/or
environment
Start with a Snapshot" of a point in time
If another user modifies the mainline, the sandbox will contain stale
information
While sandboxes prevent end users from seeing in-progress

customizations, they do not prevent two developers in two different
sandboxes from working on the same object
Note: Concept of sandbox extends to mobile customizations as well
Operation: Activate Sandboxes

Active sandbox holds the context for all the changes
A developer must activate a sandbox before customizing in it
Ensures that all customizations made by the developer are stored in the
sandbox
Each developer may have only one sandbox active at a time
Any number of sandboxes can be created but not active
A currently-active sandbox is shown at the top of the application screen
Operation: Publishing Sandboxes

Copying sandbox metadata to the mainline is referred to as publishing
the sandbox:

Overwrites existing customization files with the sandbox versions of the files
All sandbox customizations are immediately available to all users
The sandbox is marked as read-only and is only visible in the list of published
sandboxes
Operation: Deleting Sandbox

Deleting sandboxes cleans up the Metadata Services Repository and

database layers
After you publish your integration sandbox, delete all test-only sandboxes. Create
entirely new sandboxes for a new project.
You can delete only unpublished sandboxes
When you delete a sandbox, you should first confirm that the sandbox is
not active
Integration Sandboxes
Created specifically to contain all approved modifications
This sandbox is the only sandbox that is published

Only the integration sandbox
is published
Developer 1
Developer 2
Session 1
Sandbox 1
Integration
Sandbox
Session 2
Sandbox 2
MDS
Database
Both developers migrate their

customizations into the
integration sandbox
Working with Integration Sandboxes
Setup private
Sandbox
Setup
With an integration sandbox:

Each developer uses a dedicated sandbox to
make his or her own customizations
Once those customizations are completed,
tested, and approved, each developer re-keys
in his or her customizations into the integration
sandbox
The integration sandbox act as the final staging
point before publication to the mainline code
Configure and
extend application
as per the
requirements
Configure
Test customizations
without publishing
Test
Get approval for the

changes and
prepare to roll out
Prepare
Re-Key
Rekey Approved
changes into
Integrated sandbox
Life Cycle: Sandbox

Day1:
1.
Private Sandbox A created by Administrator 1
2.
Private Sandbox B created by Administrator 2
3.
Private Sandbox C created by Administrator 3
4.
Integration Sandbox A is created
Day2:
1.
2.
X
2
3
Each of the administrators have extended the

application to meet their requirements
Tested configurations and are ready to be
rolled out
X
2
3
X
2
3
Day3:
1.
Changes approved
Day4:
1.
Re-key approved changes to Integration

Sandbox
Day5:
1. Integration Sandbox A is published
2. On publish of Integration sandbox, all the private sandboxes become
stale
Tips for Success: Sandboxes

Never make your customizations directly in the mainline. Instead,

always use sandboxes whenever possible
Always do development work in the Non-Production Environment
Create an "Integration Sandbox" before starting development

This sandbox will be the "master repository" of approved changes
One developer per sandbox

Each developer has their own private sandbox that will never be published
Developers working on the same object in different sandboxes will not see
each other's modifications
Sandbox Considerations
Sandboxes should exist for a short period of time
Minimizes the risk of stale data in sandboxes
Conflict resolution: If one developer publishes a sandbox and a second

developer tries to publish a sandbox that modifies one of the alreadymodified objects, that developer receives a warning that the object has
been updated outside of the sandbox
The developer can choose to ignore the warning and publish anyway,
overwriting the original developer's modifications
Sandboxes only isolates Application Composer MDS data and Page

Composer changes that effect MDS
For a sandbox that contains Business Components customizations, sign

out and sign in again after switching in or out of this sandbox to avoid
any inconsistencies between the run time caches and the ADF Business
Components definitions
Lookup Types and Values
Lookup Types and Lookup Values are considered seed data and are not stored
inside the Metadata Services (MDS) repository. Accordingly, any Lookup Types or
Lookup Values that you create as part of a customization effort are retained in
the database, even after a sandbox is deleted
Web Services (including Object Workflows)

Web services do not reflect sandbox changes such as custom fields or objects
until the sandbox is published
Reports and Custom Fields
In order to create a Custom Subject Area (CSA) to include custom fields or

objects (always created inside a sandbox), one must first publish the sandbox to
report on these custom elements
Import and Export

To generate the object artifacts required for both file-based import and bulk
export one must first publish the sandbox
Even though a sandbox is deleted, related transactional data for custom

objects is retained because transactional data is stored outside of the
MDS
Extensibility Features and Scripting
How do you extend the product to

meet your customers
requirements?
Customization and Configuration Feedback

Partners and Customers told us
We need a single place to configure all the Pages including Desktop,
Simplified, Mobile and Outlook
We heard..
Application Composer is the place to go. Outlook, Simplified, Desktop, and
Mobile pages all of them can be configured using Application Composer

We would like to view different layouts for different business users based
on specific attributes of the user and the related Oracle Sales Cloud (OSC)
object. Achieving this is too complex in the current framework
We heard
With R8, dynamic layouts were introduced to display different layouts at
runtime based on login users role and object the user is trying to access
With R9
In R9, we have extended the feature of dynamic layouts to additional OSC
objects, Mobile as well as Outlook

We would like to logically group attributes of OSC objects in the related UI
rather than showing it in a lengthy form. Achieving this is too complex in the
current framework.
We heard
With R9, a new feature is introduced which facilitates grouping of fields while
defining the layout at design time.

Expose custom objects on Simplified Pages as top level cards and on spring
board
We heard
With R8, custom objects were provided as top level cards on Mobile in
addition to the already existing Desktop Pages.
With R9
With R9, custom objects are provided as top level cards on Simplified Pages
along with a configuration option to show/hide.

They said it is too cumbersome to move from an object to its related object and
thereby losing the context. Can there be some sort of drill down into the
referenced object from the parent/reference object.
We heard
A new feature called configurable object drill down (DCL) was introduced which
facilitated navigation of control from and to the related objects without losing the
context.
With R9
A new feature called Direct Page Linking can now open a specific sub tab of a
record detail page from a link in an email, report, or custom app.

They asked if it is possible to navigate to 1) the transaction record from
Reports/Analytics and 2) to other reports from within a report
We heard
With R8, reports/dashboard drill down to transactional data and other
related reports were enabled.
With R9
Drill down to transactional data from reports/dashboard extended to SUI
Pages
Topics
Get Oracle
Sales Cloud

Initial Setup
Learn Core
SFA + SPM
Learn about
Data
Shapes
Configure &
Customize
the
Application
Administer
Key Areas
Integrate
with Other
Systems
Customization and Configuration Capabilities

Application Composer
Extensions
Overview: What is Customization and Configuration

Modify existing applications
Extend existing applications
View modifications immediately
Add new modules and application
All within the standards-based Oracle Fusion Middleware Platform

Customization and Configuration Capabilities Needed for

Successful Sales Cloud Implementation
Administration
Configuration
Web
Services/Groovy
Access Control
Object Workflow
Authentication /
SSO Services
Search
Engine
Reporting &
Analytics
Multi-Device
Multi-Language
MultiCurrency
Benefits
Open Standards
Driven
Uniquely
Innovative
Simplified
Complete
Allows for full lifetime

CRM Support
Abstracted for the business

Composer Suite
Functional Extensions
SAAS Enabled
Design Patterns
Admin User
Web Based
Zero Downtime
Sales Cloud Apps
Pages Customization
Page Composer
Rich persona based Pages

Personalization
Portlets/Mashups
Wizard Driven
Analytics
Business Process/Logic
Process Composer
Web-based customization
Deployment ready
processes
Palette/Grid based
Reporting/Analytics
Reports Composer
Admin created data
structures
Measures
Aggregates/Rollups
End User driven
Facts/Measures
Web Center
Cloud Sales Model Extensions

Key Capabilities
Data
Model
Standard and Custom Objects

Custom Attributes
Relationships (1:M/ M:1 /M:M)
Indexing
Pages
Reporting
Search
Benefits
Designed to make Sales Operations more
Security
Logic
productive and efficient

Change and augment the Sales Cloud
data model to meet customer needs
Extend Model

Add custom objects

Add custom fields
12 custom field types (Including RecordType)
Add custom relationship
Parent child (one-to-many)

Reference relationship (one-to-many)
Dynamic Choice List (many-to-one)
Many to Many
Query with Join (Context Link) - Allow join query
between two top level entities without using a FK
Add groovy logic

Conditional Required, Updateable
Validation rules
Triggers
Actions and links
More
Extend Model
Fixed Choice List (List of Static Values)
Reuse of create lookup codes

Customize lookup codes for existing lookup type,
localizable
Multi-Select Static Choice List
Dynamic Choice List (List of Records)
Query Criteria for limiting set of eligible records

Configurable results and search forms
Constrain Properties
Conditional Required Property, Conditional

Read-only
Formula fields
Default Value
Expression based default value using Groovy

Builder
Many-to-Many Relationships

Supports creation of Many-to-Many relationships between OSC objects

(including custom objects)
Underlying intersection object is created as a separate entity to break down
the relation into One-to-Many
Intersection object fields can be exposed in either of the parent UI as an
additional sub tab
Navigation: Application Composer > Relationships
Web Service Support for Object Extensions

Web Service Patterns
Web Service for custom object supports CRUD operations
Web Service for standard object supports CRUD operations
Custom additions to XSD for custom field and relationship
Search Criteria on Query Operation
Can be called using groovy
Practices: Opportunity and Account Extensions

Practice 06A covers extending:
Opportunity object :
Add a conditionally updateable checkbox field to a standard object
Add a fixed choice list with a default value
Add a dynamic choice list that is conditionally updateable
Add a formula field
Account object:
Create a custom child object of a standard object
Sales Cloud Pages Extensions

Data
Model
Pages
Reporting
Security
Logic
Key Capabilities
Simplified Pages: Create and Extend
Custom objects as top level cards
Social Integration
Web/Mobile/Outlook
Simplified Pages: Dynamic Layouts
Sub tabs/Tree nodes
Actions and Links
Runtime page customization
Modify page layout
Add/Remove, show/hide, move fields
Wizard-driven
Direct Page Links
Benefits
Easy to use
Changes applied instantly
Overview: Extend Simplified Pages

Add sub-tab to OOTB pages

Child or Related Objects or **Intersection
object of a many-to-many relationship
Context Link
Web Content
Expose custom fields
Edit Pages layout
Add custom buttons
Dynamic Layout
Drilldown on custom dynamic choice list
Custom Object Card
Field Grouping
Direct Page Links
** - Indicates
feature in R9
Simplified Pages: Full Custom Object Support

Custom Objects can be added at the same

level as Standard Objects
Custom Objects with an intuitive user

interface
Custom Objects support all features

including
List Management
Dynamic Layout
Field Groups
Search and Select Dialog
Global Search
Many-to-Many Relationships
Direct Page Linking
More
Simplified Pages: Custom Object

Choose Icons and Themes
Choose an icon that best represent

the business model for the custom
objects
More than 35 icon families are

supported
An icon family has a number of

variations to support different
channels, tabs, home pages, and
themes
Icons dynamically change based on
users preferred theme
Some Variations:
Simplified Pages: Sub tabs

Key capabilities
Summary Sub tab
Default OOTB Sub tab on any standard object in OSC
Cant be reordered or hidden, but can be renamed
Add new Sub tabs by editing details page of a OSC object
Create Sub tab content using child or related or **relationship objects
(from many-to-many)
Drill down into the child object
Example: Quote object as a child object to Opportunity object
Create Sub tab content using context link

** - Indicates
feature in R9
Simplified Pages: Sub tabs ..Continued

Create Sub tab content from common components
Example: Notes
Common components like Appointments, Tasks are now clubbed into Activities

Create Sub tab content using web content

Custom top level object
Sub tabs cant be deleted once created, but can be hidden
Reorder, hide/show, rename Sub tabs
Summary tab is an exception, can only be renamed
Embed Analytics
Simplified Pages: Actions and Links to Pages

Once an Action or Link is configured, it

is added to an object's pages exactly as
a field
Actions:
May appear in the Actions menu
May appear as buttons on the
pages
Links:
Appear exactly like hyperlink fields
Add actions and links to pages

exactly as you do fields
Simplified Pages Menus and Buttons

Custom action item created under an OSC object can be added to its associated
SUI Pages page layout
Action menu customizations
Add menu items under Actions menu
Organize and group the actions to appear in the Action Menu
Action items (Custom/OOTB) can only be shown or hidden, or reordered but
cant be deleted
An Action item can be part of action menu and an action button
Action Buttons
Action Menu
Field Groups
Option to organize groups of

fields under a heading
Allows splitting up a large form

into smaller logical groups
Useful for large pages and forms

for better readability
Available on both
Creation/Detailed page layouts
Field Groups

Build one from the available views

Fields already part of existing region
are grayed out and cant be selected
further
Expand and collapse field groups to
organize page view
Provision to move fields between field
groups
Field groups once created cant be
deleted but can be edited/hidden
Overview: Extend Desktop Pages

Create work area
Configure Navigator Menu

Configure Local/Regional Search
Configure summary table, creation
page, buttons/links
Add sub tab
Child or Related Objects or

**Intersection object of a many-tomany relationship
Context Link
Web Content
Expose custom fields
Edit Pages layout
Add custom buttons/links
** - Indicates
feature in R9
Dynamic Layouts
Dynamic Layouts
Tailors user interface
Streamlines business process
Business flows govern how each form/page will be presented to the end
user
Improves user adoption

Sales Manager
Sales Rep
Dynamic Layout: Deliver Tailored users Experience

Unlimited ways of presenting a single Oracle Sales Cloud page, based on:
Field Values of the Record
User Roles
Any Groovy Expression
When to Use Dynamic Layouts (Use case)

Layout 1
Use a custom Product Category

field to drive different
opportunity details page
layouts:
Services opportunities have a

Solution Reviewer (Layout 2)
while Software/Hardware dont
(Layout 1)
Only Sales Managers

will see this button
Layout 2
Use role-specific layouts to tailor

the needs for different users:
Only sales managers will create
new quote from an opportunity
(Layout 2)
Solution Reviewer field displayed only for
Service products.
How-to: Define Page Layouts

Consider what drives different

display LAYOUTS for a given page
Design layouts using three types of
CRITERIA:
RECORD TYPE
ROLE
ADVANCED EXPRESSION (Groovy script)
Dynamic layout extended to

Mobile
Not supported in Desktop Pages

Manage Page Layouts

At design time in Application
Composer
Layouts can be re-ordered to
change the sequence of
evaluation at runtime
Default Layout criteria can not be
edited and always at the bottom
of the list
Layout once created cant be
deleted but can be deactivated
Manage Page Layouts

At run time
Only active layouts are evaluated
Layout conditions are evaluated
based on the listed order from
top to bottom
First layout matching all criteria is
displayed
If no custom layout matches,
default layout is displayed
No Layout = Default
eval True
Layout
Recommendation: Create custom layout by extending default layout for any UI

customizations rather than changing the default layout
Additional Examples for Dynamic Layouts

Customers can have different Pages layouts for:

Different Sales Methods, Sales Stages, or other business processes

Different user roles: Sales VPs, Sales Managers, Inside and Field Sales
Reps
Based on login users profile, e.g. EMEA vs North America
For complex scenarios, layouts assignment can be based on a
combination of dimensions or all of the 3 dimensions
Type
Role(s)
Adv Exp
How To Test Role-Based Layout?

For role-based dynamic layouts, is there any way to access the page without
giving a Sales Admin temporary access via App Composer?
The recommended approach is for CRM Admin to create test users with
both the CRM Admin role (so they can access the same sandbox) and the
role being tested (e.g. Sales Rep, or Sales Manager)
Object Drill Down
Object Drill down

Drill down into a related objects Details Page
Drill down is enabled on dynamic choice list
(including custom objects)
Drill down field initially is a regular choice list
Upon selection of the field, the field becomes a
drill down link, with an user option to clear the
value and select another value
Object Drill Down

Setting up Object Drill down

1.
2.
3.
Select the related object you want to query

to populate the list
Select the related object field value you
want to display for the user's selection
Add the field to the SUI Pages Layout
Example: Opportunity related objects
Account
Item
LeadHetc
Opty > Lead > Campaign

Cancel to navigate back
Benefits :
1. Maintain better user context
2. Better user experience with lower number of clicks
Practices: Customization and Configuration - Layouts

Practice 06B covers:

Custom Object Top Level Card

Many-to-Many Relationship
Working with Dynamic Layouts (Take-Home):
Switching layouts dynamically based on

Roles
Record Type
Composite conditions using Groovy
Direct Page Linking
Direct Page Linking

What is Direct Page Linking?
URL pattern to use for Direct Page Linking
List of objects that support Direct Page Linking
Direct Page Link: Introduction

Page links are links that point to a specific page
The direct page link URL uses a simple pattern which points to a particular
sub tab on a Simplified or to a detailed Desktop page
Typically, these URLs can be used in any reports, user interface pages to
view specific OSC objects detail page or from an external application hosted
on Java Cloud Services (PaaS)
URL Pattern to Use for Direct Page Links to Simplified Sub

tabs
Depending on the object whose details page you
are linking to, use the following syntax to create a
direct page link:
http://hostname:port/sales/faces/CrmFusionHome?
cardToOpen=<Object Details
Page>&tabToOpen=<Details Page Subtab>&<Primary
Key>=<123456>
In some cases, an additional parameter,

TF_subTabName, is also included in the URL to open a
particular sub tab
Example: https://adc-fap1111crm.oracledemos.com/sales/faces/CrmFusionHome?cardT
oOpen=MOO_OPPTYMGMTOPPORTUNITIES_CRM_CARD
&tabToOpen=MOO_OPPTYMGMTOPPORTUNITIES_CRM&
TF_skipToEditOptyId=300000087874610
Objects That Support Direct Page Linking

Simplified Pages
The objects that support direct page linking

differ depending on linking to simplified or
desktop pages
Account
Activity
Contact
Simplified Pages: Opens a sub tab of the

record details page
Household
Desktop Pages: Opens records detail page in

object work area
Opportunity
Lead
Top Level Custom Objects
Desktop Pages
Customer
Contact
Lead
Opportunity
Simplified Pages: Overview URL Patterns for OSC Objects

OSC Object
cardToOpen
tabToOpen
parameter
Account
ZCM_CUSTOMERCTRINFRA360_CUSTO
MERS_CRM_CARD
ZCM_CUSTOMERCTRINFRA360_CUSTOMERS
_CRM
TF_AccountP
artyId
**Yes
Contact
HZ_FOUNDATIONPARTIES_CONTACTS_
CRM_CARD
HZ_FOUNDATIONPARTIES_CONTACTS_CRM
TF_ContactPa
rtyId
**Yes
ZCM_CUSTOMERCTRINFRA360_GROU
PS_CRM_CARD
ZCM_CUSTOMERCTRINFRA360_GROUPS_CR
M
TF_Househol
dPartyId
**Yes
MKL_LEADS_CARD
MKL_LEADS
TF_LeadId
**Yes (Including
Analytics)
MOO_OPPTYMGMTOPPORTUNITIES_C
RM_CARD
MOO_OPPTYMGMTOPPORTUNITIES_CRM
TF_skipToEdit
OptyId
**Yes (Including
Analytics)
ZMM_ACTIVITIES_CRM_CARD
ZMM_ACTIVITIES_ACTIVITIES_CRM/ZMM_A
CTIVITIES_TASKS_CRM/ZMM_ACTIVITIES_AP
POINTMENTS_CRM
TF_ActivityId
CRM_FUSE_DASHBOARD_CARD/CRM_
FUSE_ANALYTICS_CARD
CRM_DASHBOARD/CRM_ANALYTICS
Household
Lead
Opportunity
Activities/Task/
Opty related
Appointments
Dashboard/Anal
ytics
**Yes

Overview
Profile (Accounts & Household)
Team
Contacts (Accounts, Household &
Leads)

Assets
Opportunities
Quotes(Accounts)
Leads (Accounts & Household)
Sales Team (Leads)

TF_subTabName
Relationships (Accounts & Household)

Recommendations (Accounts & Household)
Notes
Activities
Conversations
Simplified Page: URL pattern for Custom Object

For custom objects, use this direct page link URL pattern:
https://<host:port>/<marketing>/faces/CrmFusionHome?cardToOpen=CRM_CUSTOM_C
ARD_XXXX& tabToOpen=CRM_CUSTOM_TAB_XXXX&TF_ObjectId=123456
1. Copy the first part of the URL, https://host:port/<marketing>/faces/CrmFusionHome?, from the customer instance's actual
home page
2. Replace XXXX with the custom object's API name using all upper case letters. For
example, TROUBLETICKET_C
3. Obtain the API name from the object's overview page (click the object's node in
the Custom Objects tree in Application Composer)
4. Direct page links to custom object sub tabs are not supported
URL Pattern to Use for Direct Page Links to Desktop

Details Pages
In terms of Desktop details pages, Direct Page Linking is supported for the objects listed:

Contact
Customer
Lead
Opportunity
URL Pattern:
http://hostname:port/crmCommon/faces/deeplink?ObjType=<object_name>&ObjId=<123456>
ObjType: Opportunity, Lead, Customer, Contact

Example: https://adc-fap1111-crm.oracledemos.com/crmCommon/faces/deeplink?ObjType=Opty&ObjId=300000087874610
When I need more complicated

logic, what scripting support is
available?
Sales Cloud Logic Extensions
Key Capabilities
Server Side scripting (Groovy)
Data
Model
Script Editor
Full Event Lifecycle
Webservice
Triggers
Pages
Reporting
Validations
Object Workflow (ECA)
Conditional required/Update
Benefits
Designed for System Integrators to
Security
Logic
Customize/extend to meet different business

needs
Standards based architecture means you
probably have the skills on your team
Topics
Get Oracle
Sales Cloud

Initial Setup
Learn Core
SFA + SPM
Learn about
Data
Shapes
Configure &
Customize
the
Application
Administer
Key Areas
Integrate
with Other
Systems
Scripting
Groovy
Groovy Builder
Types of Scripts
White List
Runtime Messages
Scripting
Used to add business logic to an application:
Calculate or validate values for fields

Make a field conditionally Required or Updateable
For example, configure a Status field such that only a Manager can set Status = Closed
Update field values based on events

Execute programmatic logic in response to a trigger
Extract transactional information from other related or unrelated objects
so on and so forth..
Written in Groovy for Oracle Sales Cloud applications
Groovy: Overview
Groovy is a standard, dynamic scripting language for the Java platform
Created as an alternative to Python, Lisp, etc. but designed to work

natively with Java
Avoids the issues of mapping other scripting frameworks syntax and

structures into Java
Version 1 was officially released in 2007
Version 2.3 is the current stable version, Version 3 is underway
Groovy: Introduction
Groovy Is Like Java, designed to
Run natively on the JVM
Groovy compiles to Java byte code
Very similar syntax and structure
Experience with Java is highly leveraged and portable
Allows you to import and implement java class and libraries
Extends the JDK, providing access to the binaries and features of the Java
language
Where and When to use Groovy

Feature
Common Use Case
Field Triggers
React to run-time data changes. Only fired when the field is changed and upon submit.
Object Triggers
To extend the standard processing logic for an object, based on record creation, updates and deletes. There is a split
between these firing events, with some related to UI/ADF actions and others originating in the database.
Field Validation
Displays a user entered error message based groovy logic validating the field value. The message is shown only when
the validation logic returns false, and the logic is triggered only when tabbing out of the field on the user interface.
Object Validation
Commonly used where validation is needed across multiple related fields on the object. Triggered on the submit UI
action.
Object Workflows
All Object Workflows are fired upon either record creation or update, along with the option of adding a custom groovy
firing condition.
Global Functions
Utility functions that can be called from any groovy code in Application Composer (across applications).
Object Functions
Utility functions that are local to the parent object. Usually triggered from within 'Buttons and Actions' definitions in
Application Composer, although can be called from other code for that object (e.g. from a trigger).
Add Custom Fields
When adding custom fields there are a few places you can include groovy logic.
Simplified UI Layouts Advanced Expression
Used for creating dynamic layouts for simplified UI pages where fields and regions show/hide based on run-time
context values and logic. Also includes support for the depends-on feature as a trigger.
Groovy Builder
Built-in Oracle Sales Cloud tool for writing Groovy scripts

Invoke a web service
Common Groovy
functions
Available objects
and fields
Keywords such as "oldValue"

and "newValue" for fields
Code validation tool tests for

undefined variables, incorrect
syntax, and more
Editing pane with line
numbers, color-coding, and
auto-indenting
Field: Conditional Properties

Scripts that affect a single field are typically created on the Edit page for that
field:

The script to calculate the value of a formula field

A script to make a field conditionally required or updateable
A script to calculate a default value for a field
Use Oracle
Application
Composer to
edit a field
Create scripts that

determine when the
field is required or
updateable
Create scripts
that calculate the
default value of a
field
Server Scripts
Scripts that affect objects are typically created under the "Server Scripts"
page for an object:

Object-level validation rules, triggers, or functions

Field-level validation rules
Scripts include validation

rules, scripts that run as a
result of a triggering event,
or reusable functions for
the object
Navigate to the Server

Scripts page of an
object to create or edit
object-level scripts
Trigger Scripts & Events

UI Trigger Points: Common use
After Create - fires when a new object record is created. Commonly used to
set default values for fields
Before Modify - Fires when the end-user tries to modify a field value. Could
be used for generic warnings or extra security logic
Before Invalidate - Fires on the parent object when one of its child object
records is created, updated, or deleted. For building in relationship logic
Before Remove - Fires when an attempt is made to delete an object record.

Can be used to create conditions that prevent deletes

DB Trigger Points: Common use
Before Insert in Database - Fires before a new object is inserted into the database. Can be used to ensure a dependent
record exists or check for duplicates
After Insert in Database - Fires after a new object is inserted into the database. Could be used to create a
complementary record
Before Update in Database -Fires before an existing object is modified in the database. Could be used to check
dependent record values
After Update in Database - Fires after an existing object is modified in the database. Could be used to update a
complementary record
Before Delete in Database - Fires before an existing object is deleted from the database. Could be used to check
dependent record values
After Delete in Database - Fires after an existing object is deleted from the database. Could be used to remove
dependent records
After Commit in Database - Fires after the change pending for the current object (insert, update, delete) is made
permanent in the current transaction. Could be used when committed data that has passed all validation is required
After Changes Posted to Database - Fires after all changes have been posted to the database, but before they are
permanently committed. Could be used to make additional changes that will be saved as part of the current
transaction

When Do They Fire Simple Model
When you click New
1. After Create
1.
2.
3.
4.
When you click Delete

1. Before Remove
When you Update a record

1. Before Invalidate
2. Before Modify
When you Confirm deletion

1. Before Delete in Database
2. After Delete in Database
3. After Commit in Database
When you click Save after

New
Before Insert in Database

After Insert in Database
After Changes Post to Database
After Commit in Database
When you click Save after

Update
1.
2.
3.
4.
Before Update in Database

After Update in Database
After Changes Post to Database

Scenario 1: Create a new Opportunity
Navigate to the Opportunity page, click New, populate the Opportunity header
values, and click Save
Trigger Events

After Create
Before Insert in Database
After Insert in Database
After Changes Posted in Database
After Update
After Changes Posted in Database

Scenario 2: Update An Opportunity
Navigate to the Opportunity page, drill into an Opportunity, change the Opty Name,
click Save
Trigger Events

Before Modify
Before Update in Database
After Update in Database
After Changes Post in Database

Scenario 3: Delete an Opportunity that has One Revenue Line
Navigate to the Opportunity page, drill into an Opportunity, Click Delete and then
Confirm the delete
Trigger Events

Before Remove (Revenue)

Before Invalidate (Opportunity)
Before Modify (Opportunity)
Before Remove (Opportunity)
Before Delete (Revenue)
After Delete (Revenue)

Before Delete (Opportunity)

After Delete (Opportunity)
Before Delete (Revenue)
After Delete (Revenue)
After Commit (Revenue)
After Commit (Opportunity)
Global Functions
Functions that are available to other scripts in the application
Can manipulate all available objects and fields in the application
Are created and managed using the Global Functions link in Oracle
Click Global Functions to create or edit

global functions
Groovy White List

For security reasons, Sales Cloud does not allow access to every possible
Groovy method or technique
Groovy functions listed as part of White list are ONLY allowed in scripting
Feature prevents use of unsafe groovy functions to ensure quality of the

custom logic written
Runtime validation will return error if functions outside of the White List are
used
Existing scripts will continue to be supported, migration safe
White List - All functions listed in Groovy Scripting Guide doc
Actions and Links

Allow to invoke a function or navigate to a URL from within an object's page

Actions have their behavior determined by what groovy returns
Script: Run a script when the action is selected

URL: Navigate to a URL when the action is selected
Actions open the URL in the current window; links open the URL in a separate window or
tab
Select Script or URL

Select Action or Link
Select or write the script to
take action and/or return a URL
Web Services Invocation From Groovy

Loosely typed
Synchronous
Consume client certificates
Create secure/unsecure
connections
None
User/Pass SSL
User/Pass Message Protection
Within Oracle Domain
SAML Token SSL
Additional Scripting Note

Formula fields are not recalculated automatically; you must set one or
more "Depends On" fields for them
The formula is recalculated every time a "Depends On" field is updated
The "Required" and "Updateable" scripts also have a "Depends On"

setting
Allows recalculating whether a field is required or updateable when the
value of another field changes
Modularity Consolidation
Cross-web application customization

is now fully supported
Bi-directional extensibility across

application boundaries, capabilities
including
Dynamic Choice Lists

Reference Relationships
Subtabs/Tree Nodes
Groovy (newView())
Shared Custom/Standard Objects
In-Context Objects vs newView()

The majority of the Groovy scripts you can write in Application

Composer will run in the context of a specific record e.g. the account
Acme Widgets or the opportunity Server Refresh for Pinnacle
Systems
Application Composer makes it easy to write scripts for in-context

objects by providing an implicit constructor for the record
But you are not limited to only scripting in-context records
You can use the newView() method to programmatically interact with

almost every object in Application Composer, regardless of its
relationship to the in-context data

Accomplishing a simple update with in-context vs newView()
An in-context script on an Opportunity trigger could be as simple as:

setAttribute('CloseDate',(today() + 14));
A newView() based script to accomplish the same goal is more complex:

def iOptyId = 10002100303;
def myOptyVO = newView('OpportunityVO');
def theOptyRows = myOptyVO.findByKey(key(iOptyId),1);
def theOptyRow = theOptyRows.size()==1 ? theOptyRows[0] : null;
if(theOptyRow !=null){
theOptyRow.setAttribute('CloseDate',(today() + 14));

Why newView()
Powerful
Cross-object scripting
Complex logic that involves multiple objects
Operate on record sets (iterate, sort, etc..)
Create, Read, Update
Only way to access VOs in Global Functions
But
Limited Application Composer help during script authoring
Fetch limit of 500 records

Use the Groovy builder to see a list of available newView() objects
Step 2: Click
Insert
Step 1:
Functions->
Other->
newView
Step 3: view
and select
from the
entire list of
available
newView()
Objects
Exceptions
Use ADF exceptions to:
Prevent a script from completing
To generate an exception and immediately stop processing in a script, use
adf.error.raise(null)
Prevents the script from completing its task
Displays the error message to the user
Display error or warning messages to end users

Use adf.error.warn(null) to present a warning dialog to the user without stopping
processing
This is particularly useful in validation scripts where you do not want to prevent the
record from being saved
Runtime Messages

Informative messages added to scripts that can be reviewed by

developers to monitor script behavior
Enabled on an application-by-application basis
Reviewed in Oracle Application Composer
Generated using println() function calls and/or through any system/user
generated exceptions raised in the application
Enable Runtime Messages

Each application has its own set of runtime messages

Select Enable Application Script Logging to enable runtime messages
specific to an application
Runtime messages support sandboxes
The enable setting is user-specific
Practices: Groovy
Practice 06C covers:
Calling Web services using Groovy
Object Workflow
Automatically triggers asynchronous actions when a transaction record is
created or updated at runtime while certain criteria are met
An object workflow improves efficiency by automating business processes
Examples:
Adjust opportunity close date when customer budget available date is changed
Notify Sales VP when an opportunity of 50K or more is lost
Create a task for the opportunity owner 5 days before the close date
Send a completed order to a shipping partner through web service to start fulfilling the order
Design an Object Workflow

Begin the design by first asking the following questions:
1.
Which business object does

the process monitor?
2.
What is the transactional event

we want to monitor? (support
2 event points):
3.
When a record is created
When a record is updated
What is the raise condition of

the selected event?
Groovy expression that

returns true or false
Object Workflow
Update 1 or more fields on the same
record
4.
What actions do we want to trigger

when the event is raised? (support 5
action types, 1 action per type)
Field Updates
E-Mail Notification
Task Creation
Outbound Message
Send an e-mail to multiple recipients

Create and assign a task related to the
object
Make an outbound web service call with

the entire object
Invoke a SOA process
Business Process Invocation
Process Composer
Offers robust event criteria action based workflow
Custom approvals
Standard/Custom Objects
Pass parameters (Object

Workflow)
Business Catalog contains

12 Human Tasks Patterns
SaaS Deployment Pages
Process Composer Flow

This configuration task is not available within an active sandbox. Perform this task when
working directly against the main line.
Click
Business
Process
Create
Process
Create or
Edit to
Invoke
Process
Composer
Configure
Approval
Deploy
Approval
Call
Approval
via Object
Workflow
Process Composer
Create and edit approval processes

for custom and standard child
objects
Configure title for approval

notifications to Improved readability
of approval notifications
Practices: Object workflow

Practice 06D (Take Home)covers:
Object workflow
Process composer
Sales Cloud Security Extensions

Key Capabilities
Data
Grant/Revoke Privileges
Model
Functional Security
View/Insert/Update/Delete
Data Security
Pages
Reporting
View All/Update All

Instance Level
Owner
Benefits
Designed for Sales Operations and System
Security
Logic
Integrators to customize and extend to meet

different business needs
Fine tune your security model so that people
see only what they need to see
Securing Custom Objects with Application Composer

Key Capabilities
Grant/Revoke Privileges
Functional Security
View/Insert/Update/
Delete
Data Security
View All/Update All
Security Patterns

Visibility of custom UI pages and buttons by

granting privileges to Roles
Object Level Security Management Manage grant
per object basis
Grant/Revoke CRUD privileges to Roles for a specific

object
Role (Profile) Level Security Management

Manage grant per role basis
Grant/Revoke CRUD privileges on multiple objects to

a specific role
Instance Level Security Management Manage

grant per record basis
Grant/Revoke CRUD Privilege on a specific record to a
list of users
Access Control for Custom Objects
Functional Privileges:
Create
View
Update
Delete
Data Security:
View All
Update All
Data Security: By Role

To all custom objects in
a container
Sales Cloud Data Extensions (covered extensively in Data shapes)

Key Capabilities
Data
Import/Export (Custom/Standard objects)
Model
Webservices (Custom/Standard objects)

XSD schema
Outbound Message action
Pages
Reporting
Event Lifecycle
Approval Orchestration
Groovy Outbound Webservice
Customization Set Manager for Migration
Benefits
Security
Logic
Designed for Sales Operations

Allows for integration with your legacy
systems
Practices: Web services

Practice 06E covers:

Web services Standard and custom objects

JWT Tokens
Cloud Sales Reporting Extensions

Data
Model
Pages
Reporting
Key Capabilities
Custom Subject Areas
Custom Objects
Standard Objects
Relationships
Aggregates (sum, min, max)
Date Level
Marketing segmentation
Audit Trail
Integration with Simplified Pages
Security
Logic
Benefits
Designed for Sales Operations to Built
custom reports
Based upon OBI standards
Multiple Child Objects for Custom Subject Areas

Add multiple child objects

to custom subject areas
Broader reporting options

for the entire object model
(More details in Reports and Analytics
presentation)
Lab Exercise in the Analytics Lab Document: Illustrates how to create a Custom Subject Area
Simplified Pages Sub tabs - Embedded Analytics

SUI Pages Analytics Page
Page composer on SUI Pages
Add content
Change layout configuration

Provides display options

Allows Resize
Allows to show/hide components
Provides option to set content style
Simplified Pages Sub tabs - Embedded Analytics

SUI Pages List Page
3 Sub tabs (Hidden OOTB)

Use settings to show the hidden sub tabs
Use Page Composer to add content to sub tabs
OSC Supported Objects

Opportunities
Leads
Accounts
Contacts
Households
Page Composer
Page Composer Topics

Get Oracle
Sales Cloud

Initial Setup
Learn Core
SFA + SPM
Learn about
Data
Shapes
Configure &
Customize
the
Application
Administer
Key Areas
Integrate
with Other
Systems
Page Composer
Levels of configurations
Modes of operation
Page Composer vs. Application Composer
Page Composer
Page Composer is a page editor that can be used to edit the user interface
composition at run time
Access
Via menu from user login name drop down
Sandboxes
Create a sandbox before making your changes using page composer
Editable in Page Composer

Page Composer allows you to affect:

Fields: Hide or show, rename, read-only
Tabs: Reorder, hide or show
Change page layout
Add content to tabs (analytics, external web
content)
Things that are NOT editable

adding new components, adding new pages,
etc.
Reorganizing content within functional areas
Set the Configuration Level / Context

Levels
Site All users
External or Internal Vary for

company resources vs. partners
Job Role Configure for a specific

role
Mode: Running Page Composer

Design mode for navigation - the default page view that provides a
WYSIWYG rendering of the page and its content
Customizations can be done only in this mode
Select mode for editing selectable component properties
Mode: Select Field to Configure

Select Component to edit

Edit Component
Change field properties
Edit Parent Component

Show/hide and reorder fields
Example: Simplified Pages Analytics

To Add BI Report into this side tab, click on

Design button in composer toolbar, click
on Add Content button inside the tab
region to open Resource Catalog popup
window
Select the BI report to be included in Fuse
page and click + Add from resource
catalog to add the report to Fuse page
Report width can be adjusted to avoid
scrollbars
Click on the wrench icon (outlined in
screenshot above) to open component
properties window
Enable Allow Resize checkbox
Simplified Pages Customization and Configuration

Leverages both Application Composer and Page Composer
Use the Application Composer to:
Hide or show custom fields
Hide or show standard fields
Extend form regions
Extend table regions
Reorder fields (tables and forms)
Change field labels
Use Page Composer to:

Make customizations based on selected layer
Hide or show fields
Change field labels (String Editor Preferred)
Change rollover/hover text
Change text for screen readers
Mark fields required
Show required icon
Add links
Make fields read-only
And much more
Reorder select elements

Add BI related content to the pages
Strategy: Layered Customizations

Upgrade-Proof with Metadata Services Repository
Key Capabilities:
Common metadata store
Set up personalized content and services

for users
1. Base Application
Deployed
2. On-Site Branding
3. LOB Branding
Stored as layers on top of base application
Benefits:
Insulates users from updates and patches
Used throughout Oracle stack business

processes, business intelligence and
applications
4. User Personalization
and more
Layered customization
Page Composer
Runtime Client
Page Composer vs Dynamic Layout

Page Composer modifications

happen at the Role level
Application Composer (dynamic

layout included) modifications
happen at the Site level
The application will always run

through Site level modifications
(pick a dynamic layout) first and
then apply Role level modifications
Upgrade Considerations Release 8 to Release 9
Important
Use the steps in document highlighted below if:
You used Application Composer to customize the application prior to upgrading to

Release 9
&
You want to update metadata so your customizations are consistent with the
enhanced functionality in R9
Oracle Sales Cloud Release 9 - Steps to Update Application Composer Customizations to the
Latest Enhanced Behavior (MOS Doc ID 1947081.1)
Practices: Page Composer

Practice 06F covers:
Add a field to the Opportunity Summary Table and hide for Sales Reps
Reorder fields on the Opportunity Summary Table for Sales Reps
Make a field read-only on the Opportunity Summary Form for Sales Reps
Hide a choice list field on the Opportunity Summary Form for Sales Reps
Migrating Setup and Customizations
How do you migrate setup and

customization data from one
environment to an other?
Migration Feedback
Partners and customers told us
They said too much of overlap between CSM and Extension manager, can
these tools be consolidated?
We listened
CSM encompasses all the customization migration, no more extension
manager.
Migration Feedback
Partners and customers told us...
They said it is difficult to migrate reports, analytics, dashboards without
migration tool
We listened
CSM takes care of migration of reports, analytics and custom subject areas
Lifecycle Management
Test/Stage
FSM-CFG-PKG
CSM
Setup Metadata
Setup Metadata
Customization
Metadata
Master Data
Historic
Transactions
Transactions
Customization
Metadata
Production
FSM-CFG-PKG
CSM
Legend
FSM-CFG-PKG Setup and Maintenance Configuration Package Export/Import
CSM Customization Set Manager Export/Import
Setup Metadata
Customization
Metadata
Master Data
Historic
Transactions
Transactions
Go-live
Implementation Project
General Implementation Process

Initial Setup
Tasks
Setup Tasks for

Specific
Modules
Extend and
Customize
Export and import setup data and

customizations across Oracle Sales
Validate Cloud
Setup
Create
Import Data
and .
environments
on Territories
the same release.
release
Customizations
Migrate Setup
Data
Migrate
Customizations
Deploy Mobile
& Desktop
Clients
The Tools
Setup and Maintenance (FSM) used to migrate setup data
Application that helps you organize, manage, and perform Oracle Sales Cloud
application setup tasks
Customization Set Migration (CSM) used to migrate:

All Sales Cloud customizations

Customizations for other Fusion Applications (not just Sales and Marketing)
Setup and Maintenance Setup Data Migration

Lookups/Profile
Options
Product Group
Promotion
Sales Stage
Sales Method
Sales Status
Sales Lead
Assignment Rule
Opportunity
Assignment Rule
Contract Type
Geography
Structure and
Data
Resource Roles
& Hierarchy
Rule-based
assignment
rules
Territories
Migration Services
Setup and Maintenance supported
Need manual re-configuration

Set and Maintenance: Migration Services

Use Set and Maintenance (Manage
Configuration Packages task) to:

Export and import implementation

projects (task lists)
Export setup metadata from one
environment and import it to
another environment
Process indicators

Completed successfully
Manual Export Pending
Completed with errors
Customization Migration
Migrate most customizations and extensions made using:

Page Composer
Setup and Maintenance (certain tasks):
Manage Menu Customizations

Manage Standard Lookups
Manage Common Lookups
Security
Security privileges associated only to custom objects are migrated

Any changes to APM like duty roles, hierarchy changes, privileges and security policies
are NOT migrated
Customization Migration
But you must manually recreate:

Web service credential information

Customizations for Incentive Compensation
Security changes in APM made outside of App Composer
Import / export artifacts These are generated with a click of a button
Customizations on following objects are also migrated by CSM:

Email templates
Custom subject areas
Reports (BI Custom Reports), analytics, and dashboards
How Does Customization Migration Work?

You need an Application Administrator role to use Customization
Migration
Use the Customization Migration page to export and import
customizations
Customizations created in a source environment are exported in the form of

a Customization Set
A Customization Set is then applied to a target environment
In the application, customization set includes all customizations

identified for the following types
Application artifacts
CRM e-mail templates
CRM common components
How Does Customization Migration Work?

Use the Outgoing tab to:
Create customization sets

Download customization sets to a compressed folder
Use the Incoming tab to:
Import the extracted customization set to the target environment

Apply and restore customization sets
Only the last imported customization set can be restored
Navigator > Customization Migration

CSM is accessed as a submenu item Migration

under the Customization
menu in the Navigator
Use Outgoing Tab to

Create Customization Set
Monitor Progress of the Export Request

User can click Log to monitor export progress

of the customization set
Individual status for each of the following 3
sections are reported

Application Artifacts
CRM e-mail templates
CRM common components
Possible statuses on each of the sections are

In Progress
Error
Succeeded
Overall status is Succeeded only when all of

the 3 sections report Success
Ready for Download
Download the Migration Set; Then Compact

On Download
Customization Migration set with a
.jar file extension
On Delete
Download button is disabled
Customization set is compacted
Use Incoming Tab to Upload Customization Set

Incoming tab - Enables customers to upload, apply and restore
customization sets
Upload
Upload Customization Set is enabled only when an upload isn't in process and all
preexisting customization sets are compacted
Apply
When the user clicks Apply, Restore is disabled and remains disabled until the apply
completes
Restore
Restore previous customization set
Apply the Customization Set or Compact to Remove

On errors during the

import, all changes
are automatically
rolled back, reverting
target to the state
prior to import
If you discover
something wrong
after import, you can
restore the previous
customization set
Restore the Last Applied Customization Set

When the user restores, that

customization set becomes
the last applied, and the last
applied moves down with the
Restore button
Like the Create, the Restore is
a long-running operation and
may be in an in-process state
for a while.
Restore also has an Abort
button while in process
User personalization performed after a customization set is applied are lost if you restore
that customization set.
Before you begin migrating with Customization Migration

Make sure:

Users are logged off during import

No one is publishing customizations in the source environment during the
export process
Tips for Success

Both environments MUST be on same release, not necessarily on the same
patch
CSM will only work across same releases

One can migrate across patches of a same release
Patches should involve no data model changes or import may fail
Recommend that target and source are same release prior to using CSM
Make all customizations and extensions in test environment

Use Customization Migration to move changes to production
Make all new customizations and extensions in a sandbox
An exported customization set does not include customizations that are in

sandboxes
This prevents you from including in-progress customizations in a customization
set
Tips for Success

Commit or delete any sandboxes before you use it to import new

customizations
Do not modify the exported customization files
Use the most recent exported files to import customizations to the
target environment
Perform your Customization Set import at a time when there are no
users logged into the system
The import process may disrupt some user activities
Demo
Play demonstration section from the video link below:
http://download.oracle.com/ocomdocs/global/fusion_r8/sales/Customizatio
n_Migration_Enhancements/index.html
The Guides Youll Want to Have

Documentation, including videos and tutorials are available at
http://docs.oracle.com/cloud/latest/salescs_gs/index.html
Customizing Sales
Oracle Sales Cloud: Getting Started with Customizations
Oracle Sales Cloud Release 9 Customize
More information on client and browser settings for Oracle Sales Cloud is
located at http://www.oracle.com/us/products/systemrequirements/overview/index.html
CSM
http://docs.oracle.com/cloud/latest/salescs_gs/OACEX/F1607004AN123
1A.htm#F1606990AN12CC8
Backup Slides
PaaS
PaaS Topics
Get Oracle
Sales Cloud

Initial Setup
Learn Core
SFA + SPM
Learn about
Data
Shapes
Configure &
Customize
the
Application
Administer
Key Areas
Integrate
with Other
Systems
Overview What is PaaS?

Tailor Sales Cloud through Extensibility and Customization
Enrich Sales Cloud through Platform Services
Manage PaaS
Activate PaaS
Demonstrated Business Agility through Sample Use Cases
Modern Cloud
Connected
Personalized
Applications tailored to
business with the speed and
simplicity of SaaS
Seamless integration
of data and processes
across cloud, on
premise and third
party
Modern CX Cloud
Secure
Defense in Depth security from
the industry leader
Personalized Cloud
Why?
your users have
CHANGED
Social | Mobile | Y-gen | Self Discovery | Learning

| Choice | Innovation | Expectation | Information
An Agile Sales Cloud
SaaS
Tailor Sales Cloud
Do More Within Your Cloud..
PaaS
Enrich Sales Cloud

Create New Features & New
Applications.
Tailor Sales Cloud within Oracle Applications
Tailor Your CX Cloud

Benefits:
Included in Oracle Applications:
Tailoring done by Business Users
Improve user experience
Increase user satisfaction
Configure dashboards based on individual

preferences and place data fields on the
screen with validation on the fly
Change built-in workflow processes
Modify reporting
Apply UI changes to all devices
Protect tailored changes
Create contextual social conversations
across software updates
Tailor Dashboards and Data

Users are empowered to tailor
their views of data but can only see
data relevant their role
Users expect flexibility to define
and add fields as they need
Leads to discovery and new ways
to improve the business
Tailor Workflow Processes

Workflow processes often vary
depending on business conditions
Easily modify built-in workflows

to make changes to:
a sales approval process

contract signoffs
special order process
approve product availability by country
Tailor Display Across Any Device

Users expect a simplified, tailored
experience
Users expect to access information
from any device
Quickly select fields to have data
display on any device:
Web
Mobile
Outlook pages
SaaS Configuration and Customization

Oracle Sales Cloud Extensibility
Common metadata store
Setup personalized content and
services for users
Stored as layers on top of base
application
Leverages Sales Cloud user and
role model
Tailored to your business or
industry
Enrich CX Cloud with Oracle Cloud PaaS
Enrich Your CX Cloud with Oracle Cloud PaaS

Benefits:
Oracle Cloud PaaS:
Extend capabilities to
create new features and new
applications
One cloud platform

Across SaaS and PaaS
Build seamless extensions to enrich CX
Create custom mobile applications

Share documents externally
Develop apps, access data & test quickly
Simplify and unify BI across business
Modernize legacy Apps
Streamlined development
with industry leading tools
Create a Custom Mobile Application

App assists sales reps in lead
follow-up process:
Salesperson scans a business card with
phone
Saves as a Contact to Oracle Sales
Cloud
Salesperson is alerted on a specific
date to follow-up with contact
Share Documents Externally

Collaborate on a sales opportunity
with partners
Create a shared folder for a specific
partner / opportunity
Embedded folder in the Sales Cloud UI
Users can leverage all Document

Cloud functionality for managing
shared folder content
Across web, mobile, desktop and
offline
Develop Applications & Access External Data

Custom User Interface to access
onPremise Trade Promotion
Application
Modern and open web

technologies,
Easy to build and use, and Rich UX
Developer Cloud
Users Results pushed back to

Sales Cloud as an Opportunity
Siebel
(DCS)
Browse
r
Create
Promotion
s
Document
attachment
s
Java
Cloud
Sales
Clou
Create
d
Oppty
& Line
Items
Documen
t Cloud
What Do We Say When Custom Requirements are

Identified?
Yes, We Can Do That!
Oracle PaaS and SaaS provides
TAILOR: Meet diverse needs of every organization.
Empower the sales organization
ENRICH: Add industry standard, open, unconstrained
applications to increase breadth of solution
Oracle Platform and Infrastructure Services

A Complete Portfolio of Services
Process
Services
Documents
Services
Social Network
Services
Business Intelligence
Services
Big Data Services
Database
Services
Java
Services
Developer Services
Mobile
Services
Integration
Services
Compute Service
Storage Service
Messaging Service
Identity Service
Systems Monitoring &

Analytics Services
List of PaaS Services

Today
Java Cloud
WebLogic as a Service
Database Cloud
Storage Cloud
Database Backup Cloud
Developer Cloud
Document Cloud
BI Cloud
Later This Year

Compute Cloud
Messaging Cloud
Next Year
Identity Cloud
Process Cloud Service
Mobile Cloud
Integration Cloud
Big Data Cloud
Systems Monitoring and
Analytics Cloud
Web Service Catalog for Cloud Applications

Available for PaaS
Over 1000 Assets
Web Services
File Based Import
Technical Reference Documentation
Look-ups
Roles and Reports
Available by:
Product Line Product Family Product
Business Object
Integration Scenario
Database Cloud Service

Overview
Dedicated 11gR2 or 12c schema and tablespace
Rapid web application development with
Oracle Application Express (APEX)
Full support for SQL and PL/SQL
Access data via RESTful Web services, SQL
Developer, JDBC (Java Cloud Service)
Migrate from on-prem to the cloud easily
Oracle Java Cloud Service

Application Standards Support
Java EE & Web
Apps
Database
Interaction
EJBs (Local Only)
Java Persistence
JSF
JSP
Web Services
(JAX-WS)
API (JPA)
JDBC to Database
Service
Oracle ADF Apps

ADF Faces
ADF Business
Components
ADF Web Service
Data Control
REST Service
(JAX-RS)
Sample Code Library

Includes examples of:

Dynamic web service handlers using JAX-WS
Data sync connectors
Rich UI data visualization components
Mobile App REST faade on Oracle Sales Cloud
web services
A healthcare provider sample application
Demonstrates the integration of Database Cloud
Service and Java Cloud Service
Available on the Oracle Technology Network
Oracle Developer Cloud Service

Dev, Test or
Production
Commit
Deploy
Java Cloud
Service
Developers
Track & Monitor
Developer
Services
Cloud or
On-Premise
Social Network
Extension Framework and REST APIs
Platform Site for Developers
Embeddable Social Plugins
Oracle Social Network Extension Framework & REST API
Oracle Social Network

Conversations
Social Objects
Content
People
Oracle Document Cloud Service

Modern and fast web UI with drag and drop

File changes tracked through automatic
versioning
Delete and restore items moved to the trash
File sharing and collaboration with users
outside and inside the organization
Online and offline user access
Web based file previewing for over 400+ file
types
Keyword search across folders and files
Use Explorer/Finder with Windows and Mac
OS clients
Access to all of your data, right from your
smartphone or tablet
Oracle BI Cloud Service

Multi-tenant Oracle Business Intelligence
Answers and dashboards, thin-client data loader
and modeler, BI Mobile HD
Simple administration and integrated IdM
Ideal for
- Departmental and personal data mash-ups
- Prototyping / sandboxing / temporary project
environments
- Adding new features like BI Mobile
Managing PaaS Services
My Accounts
Subscribed Services
All service types
View services across
datacenters
Check service uptime
Manage account
administrators
Console for account
administrators
Cloud Services
Metrics and Monitoring the System
Performance
Data Sources
Applications
Resources
Service Jobs
Governance Provides IT Friendly Platform

Secure data centers, owned and controlled by Oracle, ensure secure
solutions and high performance
Applications remain portable due to open, standards-based architecture
No limiters prohibiting well-behaved customizations
Common identity architecture simplifies user management across
applications
Simplified support through a single vendor.
Getting Started with PaaS
Activate your Subscription

eMail
Notification
Go to
cloud.oracle.com
Provide details
on languages,
notifications, etc.
Subscribe
Sign-on
Credentials
Access
Service
Activate
Notification of instructions
User initiated configuration
Capture preferences
Manage and
administer users
Use
Environment provisioned
User sign-on credentials
Self-managed
Home Page
This area directs developers

to content for use cases,
security, and web services.
The doc page for the Oracle

Sales service will include
new topic-based tabs for
customization, integration,
and web services.
Developers Corner
Start Building with Oracle Cloud Services
Code Samples provide access to downloadable

code samples for the use cases
Use Cases provide access to topics for the use
cases
Security provides access to key security topics
Developers Annex details on business object
services owned by a particular family, as well as
all Fusion Application services
Cloud Marketplace Registration

Become a Publisher
Access for Partners

Partner Landing Page
Submit Application Form
An Agile Modern Cloud

SaaS
Tailor User Experience
PaaS
Enrich CX Cloud
Tailor the delivered UI
Trade Promotion Application
Change existing business

processes and workflows
Travel Authorization
Application
Add new data objects and

associated business processes
Call Report Application
Mashups to other applications
Subcontractor Bidding
Application
PaaS Sample Use Cases

(Stop here if out of time and move on to Smartphones/Tablets/Outlook)
New Account
Origination Demo
Extending a Vertical New Account Origination

ORACLE CLOUD PaaS SERVICES
INDUSTRY OVERVIEW
Banking (Retail and Commercial and Wealth
Uses 75% out of the box functionality

Extended for specialized industry
Management), Loan Origination, Credit Card and

Insurance
requirements
THE SOLUTION
KEY CHALLENGES
Build business by building deeper customer
relationships and increasing wallet share
Optimize time selling by leveraging customer financial
history to recommend best set of financial offerings
Manage risk by staying on top of client interactions
and visibility into big ticket transactions, performance,
and market news
Reduce costs of doing business by focusing on the
business rather than IT requirements
Customer express interest in home loan through

social marketing channel

Lead captured and nurtured through account
application using Oracle Policy Automation
Banker access to customer credit history with
embedded BI dashboards
Recommended options for loan interest rates and
cross-sells home insurance policy
Optimized user interface for tablet view with
custom branding
New Account Origination

Increase Banker Visibility
New customer contacts
Leads from social channels
Opportunities with intelligent scoring
Company branding across all
applications
Extends simple, easy to use view to
tablets

Review Customer Profile and Credit History
Changed labels
Added custom tab
Embedded OBIEE report shows

revenue and heat map overview

Product History
Product assets pulled from core
banking and summarized on
profile
Existing assets displayed in new
form with details

Need Analysis and Product Recommendations
Oracle Process Automation flow
embedded inside opportunity
Detailed analysis steps through
required details
Product choices are
recommended
Product selection progresses to
application

New Account Application
OPA updates opportunity and
revenue lines
Sales stage and win probability
updated
Inline link to view pending
application available on Bankers
Desktop
Bankers Desktop
Custom UI
View of bankers upcoming
appointments and existing leads
Complete new UI using Oracle
Sales Cloud web services
Available on iPad
Summary View for Bankers

Customer 360
360 degree view highlights key
information
Consolidated data from multiple
sources
Heat map report generated via
OBIEE and consumed RESTfully
via API
Summary View for Bankers

Customer Opportunity combined with Customer Information
All customer opportunities
Access to home loan application
Customer Contact
Center Demo
Compose email
Custom UI
Select recipients
Use templates
Send email
Create Alert
Custom UI
Select from Contacts
Set-up alert to remind you of next
scheduled action
Confirmation of alert
Notifications and Approvals

Custom UI
Leverage contacts within Sales Cloud
Using events and triggers
Create notifications and approvals
Card Scan Demo
Creating Custom Apps Card Scan

CUSTOMER OVERVIEW
Luxury wine and spirit distributor located in France

Database Service
Java Cloud Services
Developer Services
who attends and hosts trade shows
KEY CHALLENGES
THE SOLUTION
Using a smart phone or tablet away from the office to
Turn business cards from tradeshow into scanned
interact with customers

Wants to capture the interaction with
customers/contact/account at the trade show

digital contacts on mobile

Snap a picture and include it in the digital business
card
Define company/contact information (update or
create in Sales Cloud)
Enrich contact information from DaaS or social
profile (i.e. linked-in)
Present information to edit, prompt/capture
interaction and save image as an attachment
Card Scan
Captures Business Card Information
Select information from existing gallery of
scanned business cards
Use camera to capture business card
Scan a business card with smartphone
camera
Optical Character Recognition through
integration to cloud service
Edit and update card
Save as a Contact to Oracle Sales Cloud
Card Scan
Converts Image to Sales Cloud Contacts
Browse contracts
Edit an update
Automotive Offline iPad

Application
Creating Custom Apps

Offline Automotive iPad Application
CUSTOMER OVERVIEW
Automobile and Automobile Parts sales company
located in the US.
KEY CHALLENGES
Using a tablet away from the office to
Have sales managers manage sales teams,
territories and priorities
Have sales representatives act on those
priorities and sales calls
Needs to be able to work even when there is no
network connection

Oracle Mobile Application Framework
Database Service
Java Cloud Services
Developer Services
THE SOLUTION

Oracle Mobile Application Framework

Database Service
Java Cloud Services
Developer Services
Sales Rep Dealer List

Managed By Territory
Allows the sales rep to see
dealerships by interactive
territory map
Can see a quick history of
who last visited the
dealership and when
All works offline
Sales Rep Dealer Detail

At a Glance
View contact, opportunity
and pipeline information in
one glance
Understand pipeline and
what needs to be done
quickly.
All without a network
connection
Sales Rep Priority Responses

No Network Needed
View priorities set up by the
sales manager
Easily fill in responses to
those priorities and submit
them

Oracle Sales Cloud

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Sales Cloud

Uploaded by

Copyright:

Available Formats

Safe Harbor Statement

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Oracle Confidential Internal/Restricted/Highly Restricted