Información complementaria

 

¿Qué objetos están disponibles como listas relacionadas?

Sólo los objetos con una relación campo de búsqueda están disponibles como listas relacionadas.

Así que si usted desea hacer un objeto disponible como una lista relacionada, crear un nuevo campo de búsqueda personalizado que se relaciona con el otro objeto. Si el objeto A tiene una relación campo de búsqueda para objetar B, entonces A puede ser incluido en una lista relacionada en la página de detalles del objeto B.
El mismo campo de búsqueda no tiene que hacerse visible en el diseño de página de ese objeto para la lista relacionada a estar disponible.
Relación individual versus relaciones muchos a muchos:
Cuando existe una relación de búsqueda de b / w 2 objetos, la lista correspondiente en un objeto pueden sólo campos de visualización del objeto al que está directamente relacionada. No puede extenderse a otros objetos de la manera fórmulas puede.
Exp: Solicitud de empleo lista relacionada con el registro de candidato puede mostrar cualquier campo de solicitud de empleo, pero no puede mostrar los campos de Posición de objeto a pesar de Solicitud de Empleo tiene levantó la relación con ambos objetos candidatos y de posición.
Pero a muchos a muchas relaciones ofrecen más flexibilidad:
Lista de objetos relacionados Junction ‘en un objeto maestro puede mostrar otro maestro objetos campos.
Exp: Llame campos de sitios web de empleo en el formato original de la posición porque están conectados por el objeto de unión – oferta de empleo. (Hazlo haciendo clic en el 0- en diseño de página.)
Y viceversa: llamar a campos de posición bajo el Empleo Sitio web obj diseño de página. Bajo ningún registro posición, Empleo sitio web mostrará con detalle.

¿Qué es un ID externo?

Al importar objetos, soluciones, o cuentas de personas personalizados, puede utilizar los identificadores externos para evitar los registros duplicados que se creen como consecuencia de la operación de importación.
Un ID externo es un campo personalizado que tiene el atributo «External ID», lo que significa que contiene identificadores de registro único de un sistema fuera de Salesforce. Al seleccionar esta opción, el asistente de importación detecta registros existentes en Salesforce que tienen el mismo ID externo. Tenga en cuenta que esta operación no distingue entre mayúsculas y minúsculas – por ejemplo, «ABC» será comparado con el «abc». Esta opción también permite que los valores de estos campos a ser indexados para búsqueda desde la barra lateral de la aplicación. Si no se marca usted será solamente capaz de buscar registros basados ??en el campo del número de candidatos. También el establecimiento de campo de correo electrónico como un identificador externo también nos va a ayudar con la importación de datos.
En la interfaz de usuario de Salesforce CRM, puede identificar hasta tres campos (3) personalizados en un objeto como un campo de ID externo. El tipo de campo tiene que ser un texto, un número o campo de correo electrónico.
Si el campo no tiene la propiedad «Unique», varios registros con el mismo valor de la identificación externa pueden ser creado por Insertar operación. Cargador de datos no admite autonumber como un campo id externa, aunque se puede utilizar autonumber como un campo id externo.
Cuando se utiliza un Asistente de importación para importar objetos personalizados, soluciones, o cuentas de persona, puede utilizar los ID externos para evitar los registros duplicados que se creen como consecuencia de la operación de importación.
La opción de utilizar un ID externo para la coincidencia no está disponible para el Asistente para importación de plomo, ni las cuentas y contactos Asistente de importación.

Límites Custom objeto:
* Hasta 200 en Enterprise Edition
* Hasta 400 en Developer Edition
* Hasta el 50 de Professional Edition
* Hasta el 50 de Group Edition

Límites ficha personalizada:
* Hasta 25 en Enterprise Edition
* Hasta 100 en Developer Edition
* Hasta 10 en Professional Edition
* Hasta 5 en Group Edition
20 campos se pueden habilitar para el seguimiento de un objeto personalizado
5 campos personalizados Resumen Fórmula se permiten en un solo informe
Área de texto permite – 255 ch – en líneas separadas
Campo de texto permite – 255 ch
Campo de texto largo permite – 32768 ch, en líneas separadas

Aplicaciones de Salesforce:
Data-centric (app se centra en un DB, estructurado información consistente)
Colaboración (muchos usuarios pueden compartir datos y servicios, fácil de acceder de forma remota)
Modelo de seguridad y recursos compartidos (finamente controlar el acceso de un usuario a diferentes datos)
Reglas del flujo de trabajo (se utiliza para asignar automáticamente tareas, actualizar datos, enviar correo electrónico de acuerdo a un evento de negocios, la creación o modificación de un registro de negocios)
Los procesos de aprobación (Configura una secuencia de pasos necesarios para un registro para ser aprobada y por quién)

Tecnología detrás de Salesforce:
Arquitectura multi – Todos los usuarios comparten una única infraestructura común
Los metadatos modelo de desarrollo impulsado – Modelos, obj, formas definidas por metadatos
Interfaz de programación de aplicaciones de acceso directo – Acceso a la API
APEX – Lenguaje de programación, se ejecuta en la nube en los servidores de Salesforce.com
Visualforce – Marco para la creación de características ricas interfaces de usuario para aplicaciones en servicios en la nube o mezcla web en la aplicación
Salesforce Mobile – IOS, Android, cliente nativo blackberry
Sitios – Sitios web Públicas y aplicaciones que se integran directamente con Salesforce sin que los usuarios que requieren compartir datos y la funcionalidad con la gente fuera de la organización, las aplicaciones que se integran directamente con SFDC entrada
AppExchange – Directorio web con aplicaciones Force.com disponibles para los clientes.

App es un contenedor para todos los objetos, tabs / colección ordenada de pestañas
Etiqueta App – es el nombre que representa la aplicación en Force.com menú de aplicaciones (arriba / derecha)
Nombre de la App: ¿Cómo los desarrolladores a identificar esta aplicación cuando se escribe código, nombre único utilizados por API
Etiqueta Plural – ¿Qué está escrito en la pestaña
Listas relacionadas – (en el rubro) lista de registros u otros componentes que están asociados con lo que estamos viendo.
Objetos – Etiqueta y etiqueta plural son lo que ven los usuarios.
Nombre del objeto – se utiliza para API (object__c) – API de objeto personalizado
Tipo de datos de campo – controla la forma en que el campo se muestra en última instancia en la interfaz de usuario y cómo introducir datos en el campo se almacena en la plataforma
Líneas visibles – nos permite especificar el tamaño aparecerá nuestra caja de texto en la página
Campo de moneda – una vez establecido, no vamos a ser capaces de cambiar a otro tipo de datos. Moneda (7,2) ? 1.000.000,00
Se requiere ficha Inicio en cada aplicación y siempre debe estar en la primera posición en las fichas. Al crear una aplicación personalizada, puede utilizar la opción «página de destino predeterminado» para establecer la ficha que se muestra cuando se abre la aplicación.
El último paso en la creación de una aplicación es la configuración de la visibilidad de la aplicación personalizada de perfiles.
En desarrollo – oculta la aplicación de los usuarios, excepto a partir de los que tiene permiso personalizar la aplicación (que es todo el mundo, pero el administrador del sistema)
¿Qué debo saber antes de habilitar Advanced Currency Gestora Histórico Cambio de divisas?
o tipos de cambio fechados se utilizan para las oportunidades, oportunidad productos, horarios de productos oportunidad, los campos de oportunidad campaña e informes relacionados con estos objetos y campos. Tipos de cambio de fecha no se utilizan actualmente en la predicción, campos de moneda en otros objetos o campos de moneda en otros tipos de informes.
o conversión de valores de cambio en las oportunidades utilizando tipos de cambio de fecha siempre se basará en la fecha de cierre de oportunidad del registro en cuestión. Fechas estructura de materiales Opportunity sólo se pueden utilizar para la conversión de divisas en una oportunidad con productos y horarios informe.
o Si se habilita la gestión de divisas avanzado, no se puede crear campos de resumen del roll-up que calculan la moneda en el objeto de oportunidad. Si usted hubiera establecido ningún campo de resumen del roll-up relacionadas con la moneda en el objeto oportunidad, éstos se desactivarán y se calcularán ya no sus valores.
o campos de oportunidad Campaña utilizan tipos de cambio de fecha para el cálculo del importe en la moneda de la campaña, pero no se utilizan al convertir dichos montos a la moneda de usuario.
o Cuando la gestión de divisas avanzado se habilita por primera vez, los tipos de cambio existentes se convierten automáticamente en el primer conjunto de tipos de cambio de fecha. Estas tarifas serán válidos para todos los tiempos, hasta que defina otro conjunto de tipos de cambio

Data.com (contactos, clientes potenciales, cuentas)
Jigsaw – Contactos (más de 30 millones de contactos de negocios) (comprar)
D & B (Dun & Bradstreet) – informes de crédito de negocios

Importar estos campos a Salesforce e incluso comparar los datos actuales de Salesforce para actualizar
Inactivo – Número de teléfono Bad, dirección de correo electrónico o que ya no está con la sociedad cotizada son
Por defecto – 300 sumas por licencia de usuario / por mes, pero la limpieza no afecta a sus límites.
Visualforce:
Tecnología de interfaz de usuario, páginas Visualforce también pueden ser editados por force.com IDE

2 tecnologías de interfaz de usuario:
1. diseño de la página: (UI genera automáticamente, Limited / n control de la conducta de IU, un control limitado sobre apariencia pero todas las interfaces de usuario son compatibles)
2. Visualforce: (UI generada por el desarrollador, el control total del comportamiento de la IU, el control «a nivel de píxel» total sobre la interfaz de usuario)
Páginas Visualforce en última instancia se representan en HTML

MVC – Modelo, Vista, Controlador (índices capas separadas se pueden establecer en la base de datos sin tener en cuenta la lógica de negocio o mantenimiento se puede realizar de forma individual)
Modelo: Object (maestro), objeto (detalle) {objetos personalizados se acumulan dentro de la aplicación de la herramienta gráfica}
Página Object visión general, páginas vistas de lista, la página de detalles} todas las marcas de la interfaz de usuario: View. Páginas y componentes FV se realizan por el editor de VF en línea o Force.com IDE. (HTML, Ajax, Javascript, Flex)
Controlador: (Estándar, personalizados, extensiones de controlador) ¿Qué sucede cuando un usuario hace clic botón delete = Borrar acción {controlador Apex o Force.com IDE}

Top barra de búsqueda – «Búsqueda Global» (devolverá todos los registros de varios tipos)
Side barra de búsqueda utiliza la lógica difusa para buscar
(Ce *) – marcador de posición / valor comodín

artículos recientes: últimos 10 artículos
hogar y Chatter tabs – No mostrar la vista / Crear nueva vista. No estándar de diseño de página de inicio
Una caja de arena es una copia de su organización que puede utilizar para probar configuraciones y formación de los usuarios, sin comprometer los datos de la organización de la producción. Salesforce Empresa e ilimitadas ediciones vienen con una caja de arena libre

Developer Force es una comunidad de desarrolladores que construyen y personalizan las aplicaciones que se ejecutan en la nube y se construyen con la plataforma Force.com. Miembros de la Fuerza desarrollador tienen acceso a una amplia gama de recursos, incluyendo código de ejemplo, kits de herramientas, una comunidad de desarrolladores en línea, y los entornos de prueba necesarios para la creación de aplicaciones

En una aplicación de la plataforma Force.com, el formulario utilizado para introducir información se conoce como una página de edición y la vista de sólo lectura de esa información se refiere como una página de detalles. Debido Force.com aplicaciones de plataforma se entregan en un navegador Web, utilizan enlaces para proporcionar la navegación a los datos relacionados.

Dos enormes beneficios comienzan a entrar en foco cuando se mira a Force.com aplicaciones de plataforma: están centrados en datos (Debido a que la plataforma se centra en torno a una base de datos, que le permite escribir aplicaciones que son los datos centrados en un data-centric. App es una aplicación que se basa en la estructura, información consistente como usted encuentra en una base de datos o un archivo XML) y de colaboración (Debido a que la plataforma se puede acceder por varios usuarios al mismo tiempo, le permite escribir aplicaciones que son de colaboración. una aplicación de colaboración es una aplicación con datos y servicios que son compartidos por varios usuarios en diferentes ubicaciones. diferencia de las formas más tradicionales de software que se instalan en un solo equipo y de difícil acceso desde la distancia, se puede acceder a aplicaciones de colaboración en la plataforma desde cualquier parte del mundo con sólo un explorador web.) (Seguridad y modelo de intercambio, las reglas de flujo de trabajo, los procesos de aprobación también proporcionan un marco para compartir aplicaciones sin renunciar a los datos sensibles) arquitectura multiusuario (un modelo de aplicación en el que todos los usuarios y aplicaciones comparten una sola , infraestructura común y base de código.) modelo de desarrollo basado en metadatos (Un modelo de desarrollo de aplicaciones que permite a las aplicaciones que se definen como declarativas «planos», sin código necesario. Los modelos de datos, objetos, formas, flujos de trabajo, y más están definidos por metadatos)

Apex: lenguaje de programación (como Ruby)
Visualforce (como Ruby on Rails) es un marco completo para la creación de este tipo de interfaces de usuario, lo que permite cualquier tipo de diseño de interfaz e interacción para ser construido y entregado completamente en la nube. Las interfaces de usuario que usted construye con Visualforce pueden extender la mirada plataforma Force.com estándar y sentir, o lo reemplazará con un estilo totalmente único y un conjunto de interacciones complejas. Debido Visualforce marcado se representa en última instancia, en HTML, los diseñadores pueden utilizar etiquetas Visualforce junto HTML estándar, JavaScript, Flash o cualquier otro código que se puede ejecutar dentro de una página HTML en la plataforma. Y eso es sólo el comienzo: también puede utilizar las páginas Visualforce para combinar datos de varios objetos de la plataforma Force.com, o combinar los datos de los servicios Web en sus aplicaciones

Sitios le permite crear sitios web públicos y aplicaciones que se integran directamente con su Salesforce organización-sin que los usuarios iniciar sesión con un nombre de usuario y contraseña. Puede exponer públicamente cualquier información almacenada en su organización a través de las páginas que coinciden con el aspecto y la sensación de marca de su empresa. Debido a que estos sitios se construyen y se alojan en los servidores de la plataforma Force.com, no hay problemas de integración de datos. Y porque los sitios se construyen con páginas Visualforce en la plataforma, la validación de datos en la información recogida se realiza automáticamente.

Los usuarios con el permiso «Administrar usuarios» habilitado en su perfil (bajo permisos administrativos) se consideran administradores.
Logo de imágenes y debe haber en la pestaña Documentos requeridos.
Creación de objetos personalizado:
Label: (Posición, Case)
Plural Label: El nombre que aparece en las pestañas, (Posiciones, Cases)
Nombre del objeto: se utiliza cuando se hace referencia al objeto a través de la API o (App Nombre)
Nombre de la grabación y el formato (tipo de datos): Es el nombre que aparece en los diseños de página, listas, listas de claves relacionados, búsquedas, y los resultados de búsqueda. (Posición Título, Nombre del caso) (o bien: Texto o número automático)

Elija los perfiles de usuario para que esta aplicación personalizado estará visible en el menú Force.com AppExchange. Usted puede especificar esta aplicación personalizada como la aplicación personalizada predeterminada de un perfil, lo que significa que los nuevos usuarios que tengan el perfil verán esta aplicación personalizada cuando inician sesión por primera vez.
Permitir informes
Al seleccionar esta opción hace que los datos de los registros de posición disponibles para los informes. La plataforma viene con un gran número de informes estándar, y los usuarios también pueden crear informes personalizados utilizando una sencilla pero potente generador de informes.
Permitir Actividades
Al seleccionar esta opción permite a los usuarios asociar tareas y calendario de eventos programados con una posición particular. Por ejemplo, un usuario puede crear una tarea, como «rango de salario de actualización de posición Sr. Developer,» y especificar atributos como la prioridad, fecha de vencimiento y estado. El usuario puede manejar la tarea o asignar a otra persona.
Track Historia Campo
Al seleccionar esta opción permite que la plataforma para rastrear automáticamente las modificaciones realizadas en los registros de posición, por ejemplo, que cambiaron el valor de un campo, cuando fue cambiado, y lo que el valor del campo era antes y después de la edición. Historia datos está disponible para la presentación de informes, por lo que los usuarios pueden crear fácilmente informes de seguimiento de auditoría, cuando esta función está activada. Seguimiento de los cambios de campo sobre obj personalizado.
En general, seleccione estas opciones si hay alguna posibilidad de que pudieran ser de utilidad para cualquier encargo objeto que se está definiendo.

A continuación dos opciones sólo están disponibles cuando se está creando un nuevo objeto personalizado. Si más adelante decide volver atrás y editar algunos de los detalles sobre su objeto personalizado, usted no los verá. Pero ¿qué hacen?
1. Habilitación de notas y archivos adjuntos de un objeto significa que usted puede adjuntar documentos externos a cualquier registro de la posición, de la misma manera que usted puede añadir una foto PDF o como un archivo adjunto a un correo electrónico. Es una funcionalidad muy útil, por lo que seleccionarlo.
2. Inicio del asistente Nueva pestaña personalizada hace exactamente lo que dice-que es un acceso directo para iniciar el asistente de tabulación después hemos guardado nuestra posición de objeto, y nos salvará unos pocos clics si sabemos que necesitamos una ficha. (Cada objeto que aparece como una ficha debe tener un esquema de color único y el icono. Esta combinación de colores es lo que identifica el objeto, no sólo de su ficha, sino también en diferentes partes de la interfaz de usuario, como en las listas relacionadas y resultados de búsqueda. )

Seleccione la pestaña Anexar al casilla personalizaciones personal existente de los usuarios.
Si no selecciona esta opción, los usuarios que hayan personalizado su pantalla de la ficha no verán inmediatamente la pestaña Posiciones. Además, si ya has creado una nueva pestaña y qué no activa esta opción, tendrá que eliminar primero la pestaña existente y luego vuelva a crearlo con esta opción activada para empujar de forma automática en la ficha para los usuarios existentes.

Menú de acceso rápido lateral puede ser visto porque usted tiene el permiso «Personalizar aplicación», lo que le permite crear aplicaciones, objetos, pestañas y campos. Los usuarios que no construyen aplicaciones, como los que tienen el perfil de usuario estándar, no verán este menú.
Hasta 2 relaciones maestro detalle y 25 relaciones totales

Una lista relacionado es una lista de los registros u otros componentes que están asociados con lo que estamos viendo. Listas relacionadas aparecen tanto en la aplicación principal y en las áreas de configuración y representan una relación entre los elementos que aparecen en la lista relacionada y el objeto o registro que estamos viendo en el área de detalle. Todo lo que aparece en la lista relacionada de un objeto está directamente relacionado con ese objeto.
Moneda: Longitud = # de dígitos a la izquierda del punto decimal, decimales = # de dígitos a la derecha.
100,000.00 = (6,2)
Al igual que en los campos de moneda, una vez que se define un campo como una casilla de verificación, no se puede cambiar a cualquier otro tipo
Los campos de fecha son grandes porque incluyen automáticamente una interfaz de calendario emergente desde la que los usuarios pueden seleccionar un día sin tener que escribir nada-otra característica incorporada

Dependencias de campo (picklists dependido) son filtros que nos permiten cambiar el contenido de una lista de selección basados ??en el valor de otro campo. Por ejemplo, en lugar de mostrar todos los valores de campo en una única lista de selección, podemos limitar los valores que se muestran en base a un valor de otro campo, como Continente. De esta manera nuestros usuarios pueden encontrar el país adecuado con mayor rapidez y facilidad.
Campos de lista pueden ser campos o bien controlan o dependientes. Un campo de control controla los valores disponibles en uno o más campos dependientes correspondientes. Un campo dependiente muestra los valores basados ??en el valor seleccionado en el campo de control correspondiente. En el ejemplo anterior, la lista de selección Continente es el campo de control, mientras que la lista de selección País es el campo dependiente.
Continente ? Estados Unidos, Asia, Antártida, Australia … (País)

Object | Custom Fields y Relaciones | Dependencias de Campos | Nuevo | Área funcional (Controlling) y Nivel de empleo (Dependiente) {grises de área dependientes a cabo hasta que se elija un campo de control, y me muestra depende de área funcional}

Campos de fórmula personalizados: podríamos definir un campo que miró a la información que ya se ha introducido en el sistema y luego nos dijeron algo nuevo al respecto? Piense en una fórmula personalizada como una fórmula de hoja de cálculo que puede hacer referencia a otros valores en el mismo registro de datos, realizar cálculos con ellos, y devolver un resultado. Sin embargo, en lugar de utilizar referencias de celda, utiliza campos de fusión, que sirven como marcadores de posición para los datos que serán reemplazadas con la información de sus registros, la información del usuario o información de la compañía. Y, en lugar de escribir los campos, operadores y funciones, puede hacer clic para seleccionarlos. Combinar field name = nombre de API

cuántos días a la posición ha sido abierto (Open Days) = HOY () – Open_Date__c (Pero ¿y si la posición se cierra entonces días a la posición está abierta todos los días va a crecer Cuando hay un Closed_Date__c queremos usarlo en lugar del Open_Date__c. . Así, necesitará una prueba lógica:. la función SI () nos permite realizar una prueba y luego devolver valores diferentes en función de si el resultado de la prueba es verdadera o falsa Esto no muestra en la nueva creación posición porque no lo hace requiere ninguna intervención del usuario.
IF (prueba_lógica,
valor_si_verdadero,
valor_si_falso)

IF (ESBLANCO (Close_Date__c),
HOY () – Open_Date__c,
Close_Date__c – Open_Date__c)

ESBLANCO () toma un único campo y devuelve true si no contiene un valor y falso si no lo hace
Dar campos dinámicos Valores predeterminados: coches By = Hoy () + 90 (definir una fórmula personalizada que toma la fecha de creación de la posición y añade 90 días)

Las reglas de validación verifica que los datos que un usuario introduce en su aplicación cumple con las normas que se especifican. Si no es así, la regla de validación evita que el registro está guardado, y el usuario ve un mensaje de error que se define ya sea junto al campo problemático o en la parte superior de la página de edición
Si la condición de error evalúa como True, la regla de validación evita que el registro está guardado
Para nuestra próxima regla de validación, vamos a garantizar que Cerrar Date tiene un valor cada vez que el campo Estado está establecido en Cerrado – Lleno o Cerrado – No Aprobado.
Respuesta:
Nuestra condición de error está presente siempre que:
Cerrar la fecha no se ha especificado y el estado es «Cerrado – Lleno» o «cerrada – No Aprobado»

ESBLANCO () toma un único campo o expresión y devuelve true si no contiene un valor.
Fecha de cierre no se especifica se traduce en:
ESBLANCO (Close_Date__c)

ISPICKVAL () toma un nombre de campo de lista y valor, y devuelve true siempre que se seleccione ese valor
«Estado está» Cerrado – Lleno ‘»se traduce en:
ISPICKVAL (Status__c, «Cerrado – Llenado») o puede ser TEXTO (Status__c) = «Cerrado – Rellenos»

&& Devuelve true si todas las expresiones son verdaderas, mientras que
|| Devuelve verdadero si cualquiera de las expresiones son verdaderas
exp1 && exp2 && exp3
devuelve true cuando exp1, exp2 y exp3 son todas verdaderas.
exp1 || exp2 || exp3
devuelve verdadero cuando cualquiera de exp1, exp2 o exp3 son verdaderas.

ESBLANCO (Close_Date__c) &&
(ISPICKVAL (Status__c, «Cerrado – Llenado») ||
ISPICKVAL (Status__c, «Cerrado – No Aprobado»))

Un diseño de página controla la posición y la organización de los campos y las listas relacionadas que son visibles para los usuarios cuando se visualiza un registro. Los diseños de página también nos ayudan a controlar la visibilidad y la capacidad de edición de los campos de un registro. Podemos establecer campos como sólo lectura y oculto, y también podemos controlar qué campos requieren que los usuarios introduzcan un valor y que no lo hacen.
Los diseños de página nunca deben utilizarse para restringir el acceso a datos confidenciales que un usuario no debe ver o editar. Aunque podemos ocultar un campo de un diseño de página, los usuarios pueden acceder a ese campo a través de otras partes de la aplicación, como en los informes oa través de la API. También podemos determinar qué campos necesarios en el diseño de la página.

Nombre, Apellido y Email-tienen la opción ID externo seleccionado. Esta opción permite que los valores de estos campos a ser indexados para búsqueda desde la barra lateral de la aplicación. Si no seleccionamos estos valores como ID externos, sólo seríamos capaces de buscar registros basados ??en el campo Número de Candidato. Ajuste el campo Correo electrónico como un ID externo también nos va a ayudar con la importación de datos un poco más adelante en este capítulo.
Creación del objeto de unión – solicitud de empleo:
Aunque estos campos son casi idénticos a los que hemos creado antes, te darás cuenta cuando se está definiendo los campos de relación de búsqueda que hay un nuevo paso en el asistente de campo personalizado Paso 6: Agregar Listas relacionadas personalizada. Este paso del asistente es donde podemos especificar un título para la lista relacionada con solicitudes de empleo que se mostrará en ambas las páginas de detalles candidatos y Posición.
¿Por qué no vimos este paso antes, cuando creamos nuestro campo de búsqueda Gerente de reclutamiento? Resulta que usuario es un objeto estándar único: no tiene una ficha, y no se puede agregar listas afines a ella. La plataforma lo sabe, así que deja fuera el paso de lista relacionada cada vez que alguien agrega un campo de relación de búsqueda que hace referencia al objeto de usuario. Ahora, la lista de aplicaciones relacionadas con empleo se muestra en ambas posiciones y Candidatos.
Predeterminado de búsqueda de candidatos en la solicitud de empleo de objetos (búsqueda Diseños)
Del mismo modo, las solicitudes de empleo de listas relacionadas en las páginas de Posiciones y de detalle Candidato sólo muestran un número de solicitud de empleo. Es mucho más útil si estas listas relacionadas también incluyen el nombre del candidato asociado o posición.
Para solucionar estos problemas, podemos agregar campos a los diseños de la búsqueda de los objetos que hemos definido. Buscar diseños están ordenados grupos de campos que se muestran cuando se presenta un registro en un contexto particular, como en los resultados de búsqueda, un cuadro de diálogo de búsqueda o una lista relacionada. Por la adición de campos, podemos dar a los usuarios más información y ayuda a localizar los registros con mayor rapidez.
Los diseños de la búsqueda lista relacionados en la página de detalles del objeto personalizado es el lugar de modificar estos conjuntos de campos. Ir a Su Nombre | Configuración | Crear | Objetos y seleccione el objeto Candidato. Vas a ver que los diseños de búsqueda disponibles son las siguientes: (Bajo la listas parte relacionada del objeto – Candidato)

? Resultados de búsqueda: Invalidar las personalizaciones de columna de resultados de búsqueda para todos los usuarios

La página Editar búsqueda Layout incluye una lista de campos disponibles en el objeto Candidato. Usted puede elegir un máximo de diez campos a incluir en el cuadro de diálogo de búsqueda, y ordenarlos de la forma que elija, salvo que el nombre o el número de campo único del objeto (por ejemplo, número de candidato) debe aparecer en primer lugar.

Para objeto de la opinión que se conecta a la solicitud de empleo, no creamos una ficha en la parte de creación del objeto, porque no necesitamos que sea investigable o en reciente artículo en la barra lateral. También estamos utilizando Maser relación detalle para establecer revisiones a solicitud de empleo.
Nótese que no lanzó el asistente pestaña este momento. Comentarios no necesitan una ficha de su propia, ya que se puede acceder a través de una lista relacionada en la página de detalles de solicitud de empleo. Cuando se crea un objeto con una pestaña, la plataforma ofrece acceso a los registros de ese objeto en varios lugares que no sean sólo la ficha, como en los resultados de búsqueda y la lista de artículos recientes en el área de la barra lateral de cada página. Porque la mayoría de los usuarios de aplicaciones de reclutamiento no necesitarán ver revisiones a menos que sea en el contexto de una solicitud de empleo, que no necesitamos para crear una ficha independiente para ellos.

Ahora que su relación maestro-detalle está en su lugar, vamos a pensar en los otros tipos de campos que podrían ser útiles para la gente que busca en un récord de opinión.
Lo más probable, los usuarios querrán ver el nombre del candidato y el puesto para el que se están revisando. Podríamos crear una relación de consulta a la posición de los candidatos y de los objetos, y luego exigir que los revisores escriban esos campos cuando se crea un registro de revisión, pero lo que si se selecciona el valor incorrecto? Además, ¿no sería mejor si estos campos se rellenan automáticamente de alguna manera?
Para solucionar esto, vamos a aprovechar la sinergia de fórmulas y relaciones para crear fórmulas cruz a objetos. Fórmulas Cruz-objeto son fórmulas que abarcan dos o más objetos haciendo referencia a campos de combinación de los registros relacionados. Esto significa que las fórmulas en nuestro objeto de recurso puedan acceder a los campos en el objeto de solicitud de empleo, y las fórmulas en el objeto de solicitud de empleo pueden acceder a los campos tanto de la posición y los objetos candidatos. Vamos a tomarlo incluso un paso más allá mediante la creación de campos de fórmula en nuestro objeto Review que abarcan el objeto de solicitud de empleo a los campos de referencia sobre los objetos candidatos y Posición.

Seleccione Revisión de la primera columna.
Cuando usted elige Review, la segunda columna muestra todos los campos del objeto de revisión, así como sus objetos relacionados, que están indicados por un signo de mayor que (>). Observe que el Creado por y Modificado por Última campos también tienen signos de mayor que. Esto se debe a que estos son los campos de búsqueda en el objeto de usuario.
Seleccione Solicitud de Empleo> en la segunda columna. La tercera columna muestra los campos del objeto de solicitud de empleo.
Seleccione Posición> en la tercera columna. La cuarta columna muestra los campos del objeto de posición.
Asegúrese de que selecciona Posición> (con el signo mayor que) y no de posición. El uno con el signo mayor que es el objeto de posición, mientras que el uno sin el signo mayor que es el campo de búsqueda de posición en el objeto de solicitud de empleo. En la mayoría de los casos, las fórmulas que tienen acceso a los campos de búsqueda devuelven un ID de registro críptico. En cambio, queremos que nuestra fórmula para regresar el título de la posición.
Elija Título del puesto en la cuarta columna.
Haga clic en Insertar.
Su fórmula ahora se ve así:
Job_Application__r.Position__r.Name
La fórmula se extiende a la aplicación relacionada con el trabajo de la revisión (Job_Application__r), a continuación, a la posición relacionada de la solicitud de empleo (Position__r), y por último hace referencia el título de la posición (Nombre). Observe que cada parte de la fórmula está separada por un período, y que los nombres de relación consiste en el objeto relacionado seguido por __r.
Haga clic en Siguiente.
Acepte todos los valores predeterminados de seguridad sobre el terreno y diseño de páginas restantes.
Haga clic en Guardar.

La función HYPERLINK le permite crear un hipervínculo a una URL o registro en Salesforce. El texto del hipervínculo puede diferir de la dirección URL en sí, que es útil aquí porque queremos que nuestro hipervínculo para mostrar los nombres y apellidos de los candidatos, mientras que la dirección URL señala al candidato propio registro. Queremos ser capaces de ir al perfil del candidato y por eso utilizamos hipervínculo.
Eliminar url de la función HYPERLINK que acaba de insertar, pero dejar el cursor allí.
Haga clic en el botón Insertar campo y seleccione Revisar>, Solicitud de empleo>, Candidato>, número de registro, y haga clic en Insertar.
Salesforce genera un identificador único para cada registro. Al insertar el ID de registro del candidato en nuestra función HYPERLINK, estamos permitiendo a nuestro campo de fórmula para localizar y enlazar con el expediente del candidato.
Eliminar nombre_descriptivo de la función HYPERLINK, pero dejar el cursor allí.
Haga clic en el botón Insertar campo y seleccione Revisar>, Solicitud de empleo>, Candidato>, Nombre, a continuación, haga clic en Insertar.
Ingrese un espacio, a continuación, haga clic en el botón Insertar y seleccione Operador Concatenate.
El operador Concatenar inserta un signo (&) en su fórmula, y se une a los valores a cada lado de la y comercial. Aquí vamos a utilizar el operador de concatenación para unir los nombres y apellidos de los candidatos en un solo campo, a pesar de que se almacenan en campos separados en el objeto Candidato. El operador Concatenar también nos permite insertar un espacio entre los dos nombres, como se verá en el siguiente paso.
Introduzca otro espacio, a continuación, escriba un espacio en blanco entre comillas, así:
«»
Esto añade un espacio en blanco después del nombre del candidato.
Ingrese un espacio, a continuación, haga clic en el botón Insertar y seleccione Operador Concatenate una vez más que añadir un segundo signo en su fórmula.
Haga clic en el botón Insertar campo y seleccione Revisar>, Solicitud de empleo>, Candidato>, Apellido, a continuación, haga clic en Insertar.
Eliminar [target] de la función HYPERLINK. Este es un parámetro opcional que no es necesario para nuestro campo de fórmula.
Haga clic en Comprobar sintaxis para revisar su fórmula para errores. Su fórmula final debe ser similar a esto:
HYPERLINK
(Job_Application__r.Candidate__r.Id,
Job_Application__r.Candidate__r.First_Name__c
y
«»
y
Job_Application__r.Candidate__r.Last_Name__c)

(Rating__c <1 || Rating__c> 5)
Esta fórmula evita que el registro está guardado si el valor del campo Rating es menor que uno o mayor que cinco.

La buena noticia es que se puede! Un campo de resumen del roll-up simple en el objeto de solicitud de empleo puede resumir los datos de un conjunto de registros de detalle relacionados y mostrar automáticamente la salida en un registro maestro. Utilice los campos de resumen del roll-up para mostrar la suma, mínimo o máximo valor de un campo en una lista relacionada, o el número de registro de todos los registros que figuran en una lista relacionada.

When creating a field on an object that is not the master in a master-detail relationship, the Roll-Up Summary data type is not available. This is because roll-up summary fields are only available on the master object in a master-detail relationship. (Roll-up type : COUNT, SUM, MIN, MAX)

Roll-up summary fields themselves don’t allow you to average values together, but you can use them in formulas that do. Let’s create a second roll-up summary field on the Job Application object, and then build a simple formula field that uses both roll-up summary fields to find the average rating.
Number of reviews field: Under Select Roll-Up Type, select COUNT.
We don’t need to specify a Field to Aggregate this time since we’re just counting the number of related detail records and are not interested in any specific field.

Average Rating:
Choose Job Application >, then Number of Reviews, and click Insert. Your formula should look like this:
Total_Rating__c / Number_of_Reviews__c

To update the Reviews related list that appears on the Job Application detail page, we’ll have to edit the related list directly on the Job Application page layout. This is different from how we added fields to the Job Application related list on the position and candidate detail pages because the Review object doesn’t have an associated tab, and therefore, doesn’t have a tab search layout. Remember—the tab search layout is responsible for both the fields that appear in the list on the tab home page and the default fields that appear in related lists on other object detail pages.

The tab search layout is responsible for the fields in the related list layout only if the related list properties have not been modified on other objects’ page layouts. For example, if you modify the properties of the Job Application related list on the Position page layout, those changes will always override the field specifications of the Job Application tab search layout.

Because the Review object doesn’t have a tab search layout, we have to set those fields another way.
Click Your Name | Setup | Create | Objects.
Click Job Application.
In the Page Layouts related list, click Edit next to Job Application Layout.
On the Job Application page layout, locate the Reviews related list and click the wrench icon () to edit its properties.
On the Related List Properties dialog box, add the following fields to the Selected Fields box:
Review Number
Rating
Candidate
posición
Created Date
From the Sort By drop-down list, choose Review Number.
Haga clic en Aceptar.
Click Save on the page layout edit page.
Salesforce CRM fuctions:
Campaigns ? Leads ? Accounts, contacts, opportunities ? Sales (won deals) ? Cases

Web to case ( up to 500), Email to case
Marketing Administration – leads -> Salesforce Automation -> Customer service and support automation.

Campaign – allows users to manage and track outbound mARKETING ACTIVITIES: DIRECT MAIL, ROADSHOW, ONLINE ADVERTISING…
STEPS:
1) planning 2) setup 3) Creation 4) Execution 5) Responses 6) Effectiveness

Campaign responses: web to lead, import a list of leads or contacts, manual response recorded

Lead management: lead owner, last name, company, lead status ( open, working, closed), lead source (web, phone…)
Lead process: Agreeing and implementing the steps and field values that are to be recorded by the sales and marketing teams during the lead lifecycle)
Web to lead – up to 500 leads a day
Lead queue: storage location to group leads together untul they are assigned or accepted by users or transferred to another queue.
Lead conversion – object account, contact, opportunity record

Converted leads no longer be viewed in Leads tab, only way to view them is to create a lead report. Use filter in report “Converted equals true”

The Recycle Bin link in the sidebar lets you view and restore recently deleted records for 15 days before they are permanently deleted. Your recycle bin record limit is 25 times the Megabytes (MBs) in your storage. For example, if your organization has 1 GB of storage then your limit is 25 times 1000 MB or 25,000 records. If your organization reaches its Recycle Bin limit, Salesforce automatically removes the oldest records if they have been in the Recycle Bin for at least two hours.

You have the ability to attach files up to a maximum of 10MB per e-mail.
Product, as its name implies, is a product or service that you sell to customers. Products are the individual line items that make up an opportunity.

Products: Individual items that you sell on your opportunities. All prod- ucts belong to one universal product catalog. After you create a product, you can associate it to one or multiple price books with identical or dif- ferent prices. For example, you may use multiple price books if you use one set of prices when selling to qualified non-profit agencies and a dif- ferent price list for companies in the private sector.
A product can have an associated schedule based on quantity, revenue, or both. If you currently sell products and break out schedules to fore- cast revenue recognition or for planning, you can use Salesforce to reflect important schedules for products linked to opportunities.
Price book: A collection of products and their associated prices. A product with its associated price is called a price book entry. You can also create custom price books based on your unique sales model.
You can associate a price book, add products, and build schedules on an opportunity through the Products related list on an Opportunity detail page.

If your company wants to track shipping dates with Salesforce, you need to enable quantity scheduling. If your company wants to measure revenue recognition or anticipate upcoming payments, be sure to enable revenue scheduling.
Go to Setup ? Customize ? Products ? Schedule Setup

Forecasts are generated from opportunities that all members of sales teams manage. And because Salesforce understands that reps and managers sometimes need flexibility to make judgment calls on fore- casts, Salesforce allows for overrides on totals so that submitted forecast numbers are as accurate as possible.

Your organization must have customizable forecasting enabled before territory management can be turned on
Records are the high-level data elements (such as accounts, contacts, and opportunities) that are stored in the Salesforce database. Each of the tabs corresponds to a type of record. Records consist of fields.
???? Page layouts is a feature that allows you to control the way a page is dis- played to users.
???? Search layouts is a feature that allows you to control the way search results are displayed to users. Search layouts correspond to the organi- zation of columns that are displayed on a search results page, lookup dialog page, or record home page in Salesforce.

Processes is an option that allows you to build various sales, marketing, and service processes in Salesforce that you want your reps to follow. Certain records (namely leads, opportunities, cases, solutions, con- tracts, and activities) each have a standard drop-down list used for defining processes.
???? Record Types are a feature that allow you to offer certain business processes and subsets of drop-down lists to users based on their profiles. Not to be confused with a type of record (such as an account or contact), a record type when used with page layouts and profiles can make only some of the drop-down list values available to users within a profile.

 

Try adding a filter when editing the dashboard by clicking Add Filter. A filter lets you see different views of dashboard data based on filter conditions. You can add up to three filters per dashboard with up to 10 conditions on a filter. For example, you can filter the entire dashboard by the Invoice Statement: Status field. This will show you total and daily merchandise sold for each invoice status. Instead of filtering at the report level, you directly manipulate dashboard data.

Consider the following information when planning and implementing data categories for your organization:
You can create up to three category groups with a maximum of five hierarchy levels in each group. Cada grupo de categorías puede contener un total de 100 categorías.
If you want to use data categories in an answers community, after creating your category group you must assign it to a community at Your Name | Setup | Customize | Answers | Data Category Assignments. You can only assign one category group to an answers community. Salesforce Knowledge supports multiple category groups.
Even though you can create up to five hierarchy levels of categories in a category group, only the first level of categories is supported in your answers community. Child categories below the first level are not displayed in the community, and community members can’t assign these child categories to questions. Salesforce Knowledge supports a hierarchy of data categories.

Custom formula fields are not tied to any particular currency. Si el resultado de un campo de fórmula es una cantidad de moneda, muestra en la moneda del registro asociado. Esto también es cierto para las fórmulas cruz a objetos que hacen referencia a los campos de combinación con diferentes monedas, y las fórmulas en las reglas de flujo de trabajo y procesos de aprobación.However, note that workflow rules and approval processes that use filters instead of formulas convert all currency values to the corporate currency.

By default, all lookups behave as standard lookups. When searching for records with a standard lookup, only the fields listed in Lookup Search Fields are queried. Standard lookups return up to 50 records at a time in alphabetical order and don’t allow for sorting, filtering, or customizable columns.

Now joint reports can be printed and exported up to 2000 records in excel

Tags are words or short phrases that you can associate with most Salesforce records to describe and organize their data in a personalized way. Use tags to group records from various objects by a common topic or use, and then use those tags in search to make finding information fast and intuitive.
For example, if you met a number of contacts and leads at a conference, you might tag them all with the phrase User Conference 2011. You could then search for the User Conference 2011 tag and click that tag in search results to retrieve those records.
Salesforce supports two types of tags.
Personal tags are private. Only you can view any personal tags that you add to a record.
Public tags are shared among all users in an organization. Any user with access to the record can view the public tags that you add.
Administrators can enable personal and public tags for accounts, activities, assets, campaigns, cases, contacts, contracts, dashboards, documents, events, leads, notes, opportunities, reports, solutions, tasks, and any custom objects (except relationship group members), allowing you to:
Tag records
Remove tags from a record
Browse, search, and manage tags

When you enable tags, you can also add them to a page layout by editing the page layout directly. See Customizing Page Layouts.
Search results and the Tags page don’t display custom objects that don’t have an associated tab, even if tags are enabled for the custom object. If you want custom object records to appear in search results or on the Tags page, you must create an associated tab. The tab doesn’t have to be visible to users.
Customer Portal users can’t view the tags section of a page, even if it is included in a page layout.

Is it possible for an Account to be part of multiple Territories?
Yes, Account can but opportunity can not. A territory is a flexible collection of accounts and users where the users have at least read access to the accounts, regardless of who owns the account. When you enable territory management for your organization, your forecast data is derived from the opportunities that are associated with the accounts in your territories. Users will have a different forecast for each territory to which they are assigned. For example, if you are assigned to both “California” and “Arizona,” you will have one forecast for the opportunities you have in “California,” and another forecast for the opportunities you have in “Arizona”

Manually transferring records will not trigger Assignment or Escalation Rules.

Descripción
Why are Escalation Rules not triggering?

Resolución
Often times, when setting up escalation rules you will want to include an ownership field within that rule. When doing so you will need to keep some potential issues in mind.

1. Assignment Rules that transfer inbound cases from your web to case to a queue or a potential owner will evaluate the escalation rule and then assign the case.

ejemplo:
Once a case is submitted, it will move through the escalation rules and trigger if it meets a criteria. Afterward, the case will be evaluated by the Assignment Rules and be redirected accordingly. If the escalation rule included a filter that referenced ownership after the assignment, the escalation will not be triggered.

2. Manually transferring records will not trigger Assignment or Escalation Rules.

ejemplo:
An escalation rule dictates that any cases owned by User 2 will be escalated after 30 minutes.

A case is owned by User 1. The case is then manually transferred from User 1 to User 2. This does not modify the record and does not change the last modified date. Hence, the escalation rules are not triggered.
If you opt to have Ownership involved with your escalation rules, you will need to include any users that may transfer these records to another user.

Connection Finder (Salesforce to Salesforce) allows you to email surveys to find out if your partners are Salesforce customer

Opportunity is included in territory management but not lead and activity.

If a user accesses a login URL that does not contain a unique identifier of a specific Customer Portal, then they are automatically directed to the login URL of the first Customer Portal you created – True

Division on individual records—Division is a field on individual records which marks the record as belonging to a particular division. A record can belong to a division that the administrator creates, or it can belong to the standard “global” division which is created automatically when your organization enables divisions.
Default division for a user—Users are assigned to a default division that applies to their newly created accounts, leads, and custom objects that are enabled for divisions.
Working division—If you have the “Affected by Divisions” permission, you set the division in which you want to work using a drop-down list in the sidebar. Then, searches will show only the data for your working division. You can change your working division at any time. If you do not have the “Affected by Divisions” permission, you do not have a working division; you always see records in all divisions.

The organization IDs of your sandboxes differ from your production organization ID, and will change each time your sandbox is refreshed.
Salesforce stores sandbox organizations on several instances. When a sandbox is created or refreshed, an instance is selected for your sandbox, so your sandbox may appear on different instances and have different URLs.
When data that contains object IDs is copied from your production instance into your sandbox, the object IDs in your sandbox match the object IDs in your production instance. However, data created in your production instance or sandbox will not contain matching object IDs.

Full copy sandboxes have the same storage limit as your production organization.
Configuration-only sandboxes have a 500 MB storage limit.
Developer sandboxes have a 10 MB storage limit.
Sandboxes don’t send email notifications when storage limits are reached. However, if you reach the storage limit of your sandbox, you cannot save new data in your sandbox.

External users cannot follow records!!
Permissions are to access objects and fields, and settings are to specify which record types, page layouts, and tabs are visible.
Object permissions control create, edit, delete data.

Role hierarchies don’t necessarily need to match your org chart exactly. Instead, each role in the hierarchy should just represent a level of data access that a user or group of users needs. For example, suppose your organization employs a corporate lawyer who needs to access all of the records in the app. One easy way to accomplish this is by assigning the lawyer to the CEO role in your organization’s role hierarchy. Since the CEO role is placed at the top of the hierarchy, anyone assigned to that role automatically gets full access to any record in the organization. It doesn’t matter that technically the lawyer appears below the CEO in the regular org chart.

Profile you do
Role you see

How can a system admin grant user access to dashboards?
1. Share folders with public groups, roles
2. Choose running user: run as logged-in user

Tipos de informes personalizados le permiten construir un marco en el asistente de informes, a partir del cual los usuarios pueden crear y personalizar los informes. Usted construye tipos de informes personalizados fuera de las relaciones (maestro-detalle y de búsqueda) entre los objetos, para que pueda:
o Choose which standard and custom objects to display to users creating and customizing reports
o Define the relationships between objects displayed to users creating and customizing reports
o Select which objects’ fields can be used as columns in reports
Each value in the opportunity Stage picklist is automatically mapped to a Probability and value in the Forecast Category picklist. Change the Stage of an opportunity and the Probability as well as the Forecast Category changes with it.

Schedule Type: Defines whether the product revenue or quantity will be divided into multiple installments or repeated for multiple installments.
Installment Period: Sets the interval for installments; for example, Weekly, Monthly.
Number of Installments: Number of installments in the schedule.

Mass Transfer Accounts

Help for this Page
This screen allows you to transfer an account from one user to another. When you transfer ownership of an account, the new owner will also gain ownership of the following records related to the transferred account:
o Any notes that belong to the existing owner.
o All contacts that belong to the existing owner.
o All opportunities (including closed opportunities if you select the Transfer closed opportunities checkbox below) that belong to the existing owner.
o All open activities assigned to the existing owner. Note that completed activities will not be transferred.
o The new owner might need to edit sharing.
o All open and closed cases

Delegated administrators can perform the following tasks:
o Creating and editing users and resetting passwords for users in specified roles and all subordinate roles, including setting quotas, creating default opportunity teams, and creating personal groups for those users
o Unlocking non-portal users
o Assigning users to specified profiles
o Logging in as a user who has granted login access to their administrator
o Managing custom objects created by an administrator

Default lead owner: The user or queue to which leads will be assigned if the active assignment rule fails to locate an owner.

Match the automation rules with the order in which they are processed:
1. Validation Rules
2. reglas de asignación
3. Workflow rules
4. Escalation rules

You can create criteria based sharing rules for accounts, opportunities, cases, contacts, and custom objects.

http://salesforce-certification-notes.blogspot.com.es/2013/01/extra-info.html

 


 

Extra Info

Which objects are available as related lists?Only objects with a Lookup field relationship are available as related lists.So if you want to make an object available as a related list, create a new custom Lookup field that relates to the other object. If object A has a Lookup field relationship to object B, then A can be included as a related list on the detail page of object B.
The Lookup field itself does not have to be made visible on that object’s page layout for the related list to be made available.
Single relationship vs. many to many relationships:
When there is a lookup relationship b/w 2 objects, the related list on one object can only display fields from the object to which it is directly related. It cannot span to other objects the way formulas can.
Exp: Job application related list on candidate record can display any job application field but can’t display any fields from Position object even though Job Application has look up relationship with both Candidate and position objects.
But many to many relationships offer more flexibility:
Junction objects’ related list on one master object can display other master objects fields.
Exp: Call Employment website fields under position’s page layout because they are connected by the junction object – job posting. (Do it by clicking the 0- on page layout.)
And vice versa: call position fields under Employment Website obj page layout. Under any position record, Employment Website will show with detail.

What is an external ID?

When importing custom objects, solutions, or person accounts, you can use external IDs to prevent duplicate records from being created as a result of the import operation.
An external ID is a custom field that has the “External ID” attribute, meaning that it contains unique record identifiers from a system outside of Salesforce. When you select this option, the import wizard will detect existing records in Salesforce that have the same external ID. Note that this operation is not case-sensitive – for example, “ABC” will be matched with “abc”. This option also allows the values in these fields to be indexed for search from the sidebar of the application. If not checked you will be only able to search for records based on the candidate number field. Also setting email field as an external id is also going to help us with importing data.
In the Salesforce CRM user interface, you can identify up to three (3) custom fields on an object as being an external ID field. The field type must be a text, number, or email field.
If the field does not have «Unique» property, multiple records with same External ID value can be created by Insert operation. Data Loader does not support autonumber as an external id field, although you can use autonumber as an external id field.
When using an Import Wizard to import custom objects, solutions, or person accounts, you can use external IDs to prevent duplicate records from being created as a result of the import operation.
The option to use an External Id for matching is not available for the Lead Import Wizard, nor the Accounts & Contacts Import Wizard.

Custom Object Limits:
* Up to 200 in Enterprise Edition
* Up to 400 in Developer Edition
* Up to 50 in Professional Edition
* Up to 50 in Group Edition

Custom Tab Limits:
* Up to 25 in Enterprise Edition
* Up to 100 in Developer Edition
* Up to 10 in Professional Edition
* Up to 5 in Group Edition
20 fields can be enabled for tracking on a custom object
5 Custom Summary Formula Fields are allowed on a single report
Text Area allows – 255 ch – on separate lines
Text field allows – 255 ch
Long text field allows – 32768 ch, on separate lines

Salesforce apps:
Data-centric (app is centered around a DB, structured consistent info)
Collaborative (many users can share data and services, easy to access remotely)
Security & Sharing model (finely control a user’s access to different data)
Workflow rules (Used to auto assign tasks, update data, send email according to a business event, creation or change of a business record)
Approval processes (Sets up a sequence of steps necessary for a record to be approved and by whom)

Technology behind Salesforce:
Multitenant architecture – All users share a single common infrastructure
Meta-data driven development model – Models, obj, forms defined by metadata
API Access – Application programming interface direct access
APEX – Programming language, runs on cloud on Salesforce.com servers
Visualforce – Framework for creating feature rich user interfaces for apps in cloud or blend web services into the application
Salesforce Mobile – IOS, Android, blackberry native client
Sites – Public websites and apps that are directly integrated with Salesforce without users requiring to share data and functionality with people outside your organization, apps that directly integrate with SFDC login
AppExchange – web directory with Force.com apps available to customers.

App is a container for all objects, tabs / ordered collection of tabs
App label – is the name that represents app in Force.com app menu (up/right)
App name: How developers identify this app when writing code, unique name used by API
Plural label – What is written in tab
Related lists – (under object) list of records or other components that are associated with whatever we are viewing.
Objects – Label and plural label are what users see.
Object name – used for API (object__c) – API for custom object
Data type of field – controls the way the field is ultimately displayed in the user interface and how data entered into the field is stored in the platform
Visible lines – Allows us to specify how large our text box will appear on the page
Currency field – once set, we won’t be able to change it to another data type. Currency (7,2) ? 1000000.00
Home tab is required in every App and must always be in the first position on the tabs. When creating a custom app, can use” Default landing page” option to set which tab is displayed when app opens.
Last step in creating an App is the setting of the visibility of custom app to profiles.
In development – hides the app from users except from those who has customize application permission (which is everyone but the system administrator)
What should I know before enabling Advanced Currency Management with Historical Currency Exchange?
oDated exchange rates are used for opportunities, opportunity products, opportunity product schedules, campaign opportunity fields, and reports related to these objects and fields. Dated exchange rates are not currently used in forecasting, currency fields in other objects, or currency fields in other types of reports.
oConversion of currency values on opportunities using dated exchange rates will always be based on the opportunity close date of the record in question. Opportunity product schedule dates can only be used for currency conversion in an opportunity with products and schedules report.
oIf you enable advanced currency management, you cannot create roll-up summary fields that calculate currency on the opportunity object. If you had set up any currency-related roll-up summary fields on the opportunity object, these will be disabled and their values will no longer be calculated.
oCampaign opportunity fields use dated exchange rates when calculating the amount in the campaign currency, but are not used when converting those amounts to the user currency.
oWhen advanced currency management is first enabled, your existing exchange rates automatically become the first set of dated exchange rates. These rates will be valid for all time, until you define another set of exchange rates

Data.com (contacts, leads, Accounts)
Jigsaw – Contacts (over 30M business contacts) (to buy)
D & B (Dun and bradstreet) – Business credit reports

Import these fields to Salesforce and even compare current Salesforce data to update
Inactive – Bad phone Number, email address or they are no longer with the company listed
By default – 300 additions per user license / per month but cleaning does not effect your limits.

Visualforce:
User interface technology, Visualforce pages can also be edited by force.com IDE

2 user interface technologies:
1.Page layout: (UI generated automatically, Limited / No control of UI behavior, limited control over look and feel but all UIs are consistent)
2.Visualforce: (UI generated by developer, full control of UI behavior, full “pixel level” control over UI)
Visualforce pages ultimately are rendered into HTML

MVC – Model, View, Controller (Separate layers indexes can be set on database without regard to business logic or maintenance can be performed individually)
Model: Object (master), Object (detail) {custom objects build inside the app by graphical tool}
View: Object overview page, List views page, detail page } all makes the UI. VF pages and components are done by VF editor online or Force.com IDE. (HTML, Ajax, Javascript, Flex)
Controller: (Standard, Custom, Controller extensions) What happens when a user clicks delete button = delete action {Apex controller or Force.com IDE}

Top Search bar – “Global Search” (will return all records from various types)
Side search bar uses fuzzy logic to search
(Ce*) – placeholder/wildcard value

recent items: last 10 items
home and Chatter tabs – Do not show view / Create new view. Not standard home page layout
A sandbox is a copy of your organization that you can use for testing configurations and training users without compromising the data in your production organization. Salesforce Enterprise and Unlimited Editions come with one free sandbox

Developer Force is a community of developers who customize and build applications that run in the cloud and are built with the Force.com platform. Developer Force members have access to a full range of resources, including sample code, toolkits, an online developer community, and the test environments necessary for building apps

In a Force.com platform app, the form used to enter information is referred to as an edit page and the read-only view of that information is referred to as a detail page. Because Force.com platform apps are delivered in a Web browser, they use links to provide navigation to related data.

Two huge benefits start to come into focus when you look at Force.com platform apps: they’re data-centric (Because the platform is centered around a database, it allows you to write apps that are data-centric. A data-centric app is an application that is based on structured, consistent information such as you find in a database or XML file) and collaborative (Because the platform can be accessed by multiple users at the same time, it allows you to write apps that are collaborative. A collaborative app is an application with data and services that are shared by multiple users in different locations. Unlike more traditional forms of software that are installed on a single machine and are hard to access from a distance, collaborative apps on the platform can be accessed from anywhere in the world with only a Web browser.) (Security and sharing model, Workflow rules, approval processes also provide a framework for sharing apps without relinquishing sensitive data) Multitenant architecture (An application model in which all users and apps share a single, common infrastructure and code base.) Metadata-driven development model (An app development model that allows apps to be defined as declarative “blueprints,” with no code required. Data models, objects, forms, workflows, and more are defined by metadata)

Apex: programming language (like ruby)
Visualforce (like Ruby on Rails) is a complete framework for creating such user interfaces, enabling any kind of interface design and interaction to be built and delivered entirely in the cloud. The user interfaces you build with Visualforce can extend the standard Force.com platform look and feel, or replace it with a completely unique style and set of sophisticated interactions. Because Visualforce markup is ultimately rendered into HTML, designers can use Visualforce tags alongside standard HTML, JavaScript, Flash, or any other code that can execute within an HTML page on the platform. And that’s only the beginning: you can also use Visualforce pages to combine data from multiple Force.com platform objects, or blend data from Web services into your applications

Sites enables you to create public websites and applications that are directly integrated with your Salesforce organization—without requiring users to log in with a username and password. You can publicly expose any information stored in your organization through pages that match the look and feel of your company’s brand. Because these sites are built and hosted on the Force.com platform servers, there are no data integration issues. And because sites are built with Visualforce pages on the platform, data validation on collected information is performed automatically.

Users with the «Manage Users» permission enabled on their profile (under Administrative permissions) are considered administrators.
Logo’s and pictures must be under Documents tab to be uploaded.
Custom Object Creation:
Label: (Position, Case)
Plural Label: The name shown in tabs, (Positions, Cases)
Object name: is used when referencing the object via the API or (App Name)
Record Name and Format (Data Type): It is the name that appears in page layouts, key lists, related lists, lookups, and search results.  (Position Title, Case Name) (either: Text or Auto number)

Choose the user profiles for which this custom app will be visible in the Force.com AppExchange menu. You may specify this custom app as the default custom app of a profile, meaning that new users who have the profile will see this custom app when they log in for the first time.
Allow Reports
Selecting this option makes the data in the position records available for reporting purposes. The platform comes with a large number of standard reports, and users can also create custom reports by using a simple yet powerful report builder.
Allow Activities
Selecting this option allows users to associate tasks and scheduled calendar events with a particular position. For example, a user can create a task, such as “Update salary range for Sr. Developer position,” and specify attributes such as priority, due date, and status. The user can then handle the task or assign it to someone else.
Track Field History
Selecting this option allows the platform to automatically track edits to position records, such as who changed the value of a field, when it was changed, and what the value of the field was before and after the edit. History data is available for reporting, so users can easily create audit trail reports when this feature is enabled. Tracks field changes on custom obj.
In general, select these options if there’s any chance that they might be useful for whatever custom object you’re defining.

Below two options are available only when you’re creating a new custom object. If you later decide to go back and edit some of the details about your custom object, you won’t see them. But what do they do?
1.Enabling notes and attachments for an object means you can attach external documents to any position record, in much the same way that you can add a PDF or photo as an attachment to an email. It’s handy functionality, so select it.
2.Launching the New Custom Tab wizard does exactly what it says—it’s a shortcut to launching the tab wizard after we’ve saved our Position object, and will save us a few clicks if we know that we need a tab. (Every object that appears as a tab must have a unique color scheme and icon. This color scheme is what identifies the object, not only on its tab but also in different places in the user interface, such as in related lists and search results.)

Select the Append tab to users’ existing personal customizations checkbox.
If you don’t select this option, any users who have personalized their tab display will not immediately see the Positions tab. Also, if you’ve already created a new tab and didn’t turn this option on, you have to first delete the existing tab and then recreate it with this option turned on to automatically push the tab to existing users.

Side quick access menu can be seen because you have the “Customize Application” permission, which allows you to create apps, objects, tabs, and fields. Users who don’t build apps, like those with the Standard User profile, won’t see this menu.
Up to 2 Master detail relationships and 25 total relationships

A related list is a list of records or other components that are associated with whatever we’re viewing. Related lists appear in both the main application and in the Setup areas and represent a relationship between the items that appear in the related list and the object or record that we’re viewing in the detail area. Anything that appears in an object’s related list is directly related to that object.
Currency: Length=# of digits to the left of the decimal point, decimal places=# of digits to the right.
100,000.00 = (6,2)
Similar to currency fields, once you define a field as a checkbox, you can’t change it to any other type
Date fields are great because they automatically include a popup calendar interface from which users can select a day without any typing—yet another built-in feature

Field dependencies  (depended picklists) are filters that allow us to change the contents of a picklist based on the value of another field. For example, rather than displaying every value for Country in a single picklist, we can limit the values that are displayed based on a value for another field, like Continent. That way our users can find the appropriate country more quickly and easily.
Picklist fields can be either controlling or dependent fields. A controlling field controls the available values in one or more corresponding dependent fields. A dependent field displays values based on the value selected in its corresponding controlling field. In the previous example, the Continent picklist is the controlling field, while the Country picklist is the dependent field.
Continent ? US, Asia, Antarctica, Australia… (Country)

Object | Custom Fields & Relationships | Field Dependencies | New | Functional Area (Controlling) and Job Level (Dependent) {Dependent area grays out until a controlling field is chosen, and i shows dependent on functional area}

Custom formula fields: we could define a field that looked at information that was already entered into the system and then told us something new about it? Think of a custom formula like a spreadsheet formula that can reference other values in the same data record, perform calculations on them, and return a result. However, instead of using cell references, you use merge fields, which serve as placeholders for data that will be replaced with information from your records, user information, or company information. And, instead of typing fields, operators, and functions, you can click to select them. Merge field name = API name

how many days a position has been open (Open Days) = TODAY() – Open_Date__c (But what if the position is closed then days a position is open will grow everyday. When there is a Closed_Date__c we want to use it instead of the Open_Date__c. So, need a logic test: The IF() function allows us to perform a test and then return different values depending on whether the result of the test is true or false. This does not show in the new position creation because it does not require any input from the user.
IF (logical_test,
value_if_true,
value_if_false)

IF (ISBLANK (Close_Date__c) ,
TODAY ()  – Open_Date__c ,
Close_Date__c  – Open_Date__c)

ISBLANK () takes a single field and returns true if it does not contain a value and false if it does
Giving Fields Dynamic Default Values: Hire By = Today() + 90 (define a custom formula that takes the date the position is created and adds 90 days)

Validation rules verify that the data a user enters in your app meets the standards that you specify. If it doesn’t, the validation rule prevents the record from being saved, and the user sees an error message that you define either next to the problematic field or at the top of the edit page
If the error condition evaluates to True, the validation rule prevents the record from being saved
For our next validation rule, let’s ensure that Close Date has a value whenever the Status field is set to Closed – Filled or Closed – Not Approved.
Ans:
Our error condition is true whenever:
Close date is not specified AND Status is “Closed – Filled” OR “Closed – Not Approved”

ISBLANK() takes a single field or expression and returns true if it doesn’t contain a value.
Close Date is Not Specified translates to:
ISBLANK( Close_Date__c )

ISPICKVAL() takes a picklist field name and value, and returns true whenever that value is selected
“Status is ‘Closed – Filled’” translates to:
ISPICKVAL( Status__c , «Closed – Filled»)   or it can be TEXT(Status__c) = “Closed – Filled”

&& returns true if all of the expressions are true while
|| returns true if any of the expressions are true
exp1 && exp2 && exp3
returns true when exp1, exp2, and exp3 are all true.
exp1 || exp2 || exp3
returns true when any one of exp1, exp2, or exp3 are true.

ISBLANK(Close_Date__c) &&
(ISPICKVAL(Status__c , «Closed – Filled») ||
ISPICKVAL(Status__c , «Closed – Not Approved»))

A page layout controls the position and organization of the fields and related lists that are visible to users when viewing a record. Page layouts also help us control the visibility and editability of the fields on a record. We can set fields as read-only or hidden, and we can also control which fields require users to enter a value and which don’t.
Page layouts should never be used to restrict access to sensitive data that a user shouldn’t view or edit. Although we can hide a field from a page layout, users can still access that field through other parts of the app, such as in reports or via the API. We can also determine which fields are required on the page layout.

First Name, Last Name, and Email—have the External ID option selected. This option allows the values in these fields to be indexed for search from the sidebar of the application. If we didn’t select these values as external IDs, we’d only be able to search for records based on the Candidate Number field. Setting the Email field as an external ID is also going to help us with importing data a little later in this chapter.
Creating the junction object – job application:
Although these fields are almost identical to the ones we created earlier, you’ll notice when you’re defining the lookup relationship fields that there’s a new step in the custom field wizard Step 6: Add Custom Related Lists. This step of the wizard is where we can specify a heading for the Job Applications related list that will show up on both the Candidate and Position detail pages.
Why didn’t we see this step earlier when we created our Hiring Manager lookup field? It turns out that User is a unique standard object: it doesn’t have a tab, and you cannot add related lists to it. The platform knows this, so it leaves out the related list step whenever someone adds a lookup relationship field that references the User object. Now, Job application related list is shown under both Positions and Candidates.
Default Candidate Lookup on the Job Application Object (Search Layouts)
Likewise, the Job Applications related lists on the Position and Candidate detail pages only display a job application number. It is much more useful if these related lists also include the associated candidate’s name or position.
To fix these issues, we can add fields to the search layouts for the objects that we’ve defined. Search layouts are ordered groups of fields that are displayed when a record is presented in a particular context, such as in search results, a lookup dialog, or a related list. By adding fields, we can give users more information and help them locate records more quickly.
The Search Layouts related list on the custom object detail page is the place to modify these sets of fields. Go to Your Name | Setup | Create | Objects and select the Candidate object. You’ll see that the available search layouts include the following:  (Under the related lists part of the object – Candidate)

?Search results: Override the search result column customizations for all users

The Edit Search Layout page includes a list of available fields from the Candidate object. You can choose up to ten fields to include in the lookup dialog, and order them in any way you choose, except that the object’s unique name or number field (such as Candidate Number) must be listed first.

For Review object that connects to Job Application, we do not create a tab at the object creation part because we do not need it to be searchable or in recent items side bar. We are also using Maser detail relationship to set reviews to job application.
Notice that we didn’t launch the tab wizard this time. Reviews don’t need a tab of their own because they can be accessed via a related list on the Job Application detail page. When you create an object with a tab, the platform provides access to that object’s records in various places other than just the tab, such as in search results and the Recent Items list in the sidebar area of every page. Because most Recruiting app users won’t need to see reviews unless it’s in the context of a job application, we don’t need to create a separate tab for them.

Now that your master-detail relationship is in place, let’s think about the other types of fields that would be useful to people looking at a review record.
Most likely, users will want to see the name of the candidate and the position for which they are being reviewed. We could create a lookup relationship to the Position and Candidate objects, and then require reviewers to enter those fields when creating a review record, but what if they select the wrong value? Besides, wouldn’t it be better if these fields were somehow automatically populated?
To solve this, we’ll tap into the synergy of formulas and relationships to create cross-object formulas. Cross-object formulas are formulas that span two or more objects by referencing merge fields from related records. This means that formulas on our Review object can access fields on the Job Application object, and formulas on the Job Application object can access fields on both the Position and Candidate objects. We’re going to take it even one step further by creating formula fields on our Review object that span the Job Application object to reference fields on the Candidate and Position objects.

Select Review in the first column.
When you choose Review, the second column displays all of the Review object’s fields as well as its related objects, which are denoted by a greater-than sign (>). Notice that the Created By and Last Modified By fields also have greater-than signs. This is because these are lookup fields to the User object.
Select Job Application > in the second column. The third column displays the fields of the Job Application object.
Select Position > in the third column. The fourth column displays the fields of the Position object.
Be sure that you select Position > (with the greater than sign) and not Position. The one with the greater-than sign is the Position object, while the one without the greater than sign is the Position lookup field on the Job Application object. In most cases, formulas that access lookup fields return a cryptic record ID. Instead, we want our formula to return the position’s title.
Choose Position Title in the fourth column.
Click Insert.
Your formula now looks like this:
Job_Application__r.Position__r.Name
The formula spans to the review’s related job application (Job_Application__r), then to the job application’s related position (Position__r), and finally references the position’s title (Name). Notice that each part of the formula is separated by a period, and that the relationship names consist of the related object followed by __r.
Click Next.
Accept all remaining field-level security and page layout defaults.
Click Save.

The HYPERLINK function lets you create a hyperlink to any URL or record in Salesforce. The text of the hyperlink can differ from the URL itself, which is useful here because we want our hyperlink to display the first and last names of the candidate while the URL points to the candidate record itself. We want to be able to go to candidate’s profile so that’s why we use hyperlink.
Delete url from the HYPERLINK function you just inserted, but leave your cursor there.
Click the Insert Field button, and select Review >, Job Application >, Candidate >, Record ID, and click Insert.
Salesforce generates a unique ID for every record. By inserting the record ID of the candidate in our HYPERLINK function, we’re enabling our formula field to locate and link to the candidate’s record.
Delete friendly_name from the HYPERLINK function, but leave your cursor there.
Click the Insert Field button, and select Review >, Job Application >, Candidate >, First Name, then click Insert.
Enter a space, then click the Insert Operator button and choose Concatenate.
The Concatenate operator inserts an ampersand (&) in your formula, and joins the values on either side of the ampersand. Here we’re going to use the Concatenate operator to join the first and last names of the candidate in a single field, even though they are stored in separate fields on the Candidate object. The Concatenate operator also lets us insert a space between the two names, as you’ll see in the next step.
Enter another space, then type a blank space enclosed in quotes, like this:
» »
This appends a blank space after the first name of the candidate.
Enter a space, then click the Insert Operator button and choose Concatenate once more to add a second ampersand in your formula.
Click the Insert Field button, and select Review >, Job Application >, Candidate >, Last Name, then click Insert.
Delete [ target ] from the HYPERLINK function. This is an optional parameter that isn’t necessary for our formula field.
Click Check Syntax to check your formula for errors. Your finished formula should look like this:
HYPERLINK
( Job_Application__r.Candidate__r.Id ,
Job_Application__r.Candidate__r.First_Name__c
&
» »
&
Job_Application__r.Candidate__r.Last_Name__c )

(Rating__c <1 || Rating__c > 5)
This formula prevents the record from being saved if the value of the Rating field is less than one or greater than five.

The good news is that we can! A simple roll-up summary field on the Job Application object can summarize data from a set of related detail records and automatically display the output on a master record. Use roll-up summary fields to display the sum, minimum, or maximum value of a field in a related list, or the record count of all records listed in a related list.

When creating a field on an object that is not the master in a master-detail relationship, the Roll-Up Summary data type is not available. This is because roll-up summary fields are only available on the master object in a master-detail relationship. (Roll-up type : COUNT, SUM, MIN, MAX)

Roll-up summary fields themselves don’t allow you to average values together, but you can use them in formulas that do. Let’s create a second roll-up summary field on the Job Application object, and then build a simple formula field that uses both roll-up summary fields to find the average rating.
Number of reviews field: Under Select Roll-Up Type, select COUNT.
We don’t need to specify a Field to Aggregate this time since we’re just counting the number of related detail records and are not interested in any specific field.

Average Rating:
Choose Job Application >, then Number of Reviews, and click Insert. Your formula should look like this:
Total_Rating__c / Number_of_Reviews__c

To update the Reviews related list that appears on the Job Application detail page, we’ll have to edit the related list directly on the Job Application page layout. This is different from how we added fields to the Job Application related list on the position and candidate detail pages because the Review object doesn’t have an associated tab, and therefore, doesn’t have a tab search layout. Remember—the tab search layout is responsible for both the fields that appear in the list on the tab home page and the default fields that appear in related lists on other object detail pages.

The tab search layout is responsible for the fields in the related list layout only if the related list properties have not been modified on other objects’ page layouts. For example, if you modify the properties of the Job Application related list on the Position page layout, those changes will always override the field specifications of the Job Application tab search layout.

Because the Review object doesn’t have a tab search layout, we have to set those fields another way.
Click Your Name | Setup | Create | Objects.
Click Job Application.
In the Page Layouts related list, click Edit next to Job Application Layout.
On the Job Application page layout, locate the Reviews related list and click the wrench icon () to edit its properties.
On the Related List Properties dialog box, add the following fields to the Selected Fields box:
Review Number
Rating
Candidate
Position
Created Date
From the Sort By drop-down list, choose Review Number.
Click OK.
Click Save on the page layout edit page.

Salesforce CRM fuctions:
Campaigns ? Leads ? Accounts, contacts, opportunities ? Sales (won deals) ? Cases

Web to case ( up to 500), Email to case
Marketing Administration – leads -> Salesforce Automation -> Customer service and support automation.

Campaign – allows users to manage and track outbound mARKETING ACTIVITIES: DIRECT MAIL, ROADSHOW, ONLINE ADVERTISING…
STEPS:
1)planning 2) setup 3) Creation 4) Execution 5) Responses 6) Effectiveness

Campaign responses: web to lead, import a list of leads or contacts, manual response recorded

Lead management:  lead owner, last name, company, lead status ( open, working, closed), lead source (web, phone…)
Lead process: Agreeing and implementing the steps and field values that are to be recorded by the sales and marketing teams during the lead lifecycle)
Web to lead – up to 500 leads a day
Lead queue: storage location to group leads together untul they are assigned or accepted by users or transferred to another queue.
Lead conversion – object account, contact, opportunity record

Converted leads no longer be viewed in Leads tab, only way to view them is to create a lead report. Use filter in report “Converted equals true”

The Recycle Bin link in the sidebar lets you view and restore recently deleted records for 15 days before they are permanently deleted. Your recycle bin record limit is 25 times the Megabytes (MBs) in your storage. For example, if your organization has 1 GB of storage then your limit is 25 times 1000 MB or 25,000 records. If your organization reaches its Recycle Bin limit, Salesforce automatically removes the oldest records if they have been in the Recycle Bin for at least two hours.

You have the ability to attach files up to a maximum of 10MB per e-mail.
Product, as its name implies, is a product or service that you sell to customers. Products are the individual line items that make up an opportunity.

Products: Individual items that you sell on your opportunities. All prod- ucts belong to one universal product catalog. After you create a product, you can associate it to one or multiple price books with identical or dif- ferent prices. For example, you may use multiple price books if you use one set of prices when selling to qualified non-profit agencies and a dif- ferent price list for companies in the private sector.
A product can have an associated schedule based on quantity, revenue, or both. If you currently sell products and break out schedules to fore- cast revenue recognition or for planning, you can use Salesforce to reflect important schedules for products linked to opportunities.
Price book: A collection of products and their associated prices. A product with its associated price is called a price book entry. You can also create custom price books based on your unique sales model.
You can associate a price book, add products, and build schedules on an opportunity through the Products related list on an Opportunity detail page.

If your company wants to track shipping dates with Salesforce, you need to enable quantity scheduling. If your company wants to measure revenue recognition or anticipate upcoming payments, be sure to enable revenue scheduling.
Go to Setup ? Customize ? Products ? Schedule Setup

Forecasts are generated from opportunities that all members of sales teams manage. And because Salesforce understands that reps and managers sometimes need flexibility to make judgment calls on fore- casts, Salesforce allows for overrides on totals so that submitted forecast numbers are as accurate as possible.

Your organization must have customizable forecasting enabled before territory management can be turned on
Records are the high-level data elements (such as accounts, contacts, and opportunities) that are stored in the Salesforce database. Each of the tabs corresponds to a type of record. Records consist of fields.
???? Page layouts is a feature that allows you to control the way a page is dis- played to users.
???? Search layouts is a feature that allows you to control the way search results are displayed to users. Search layouts correspond to the organi- zation of columns that are displayed on a search results page, lookup dialog page, or record home page in Salesforce.

Processes is an option that allows you to build various sales, marketing, and service processes in Salesforce that you want your reps to follow. Certain records (namely leads, opportunities, cases, solutions, con- tracts, and activities) each have a standard drop-down list used for defining processes.
???? Record Types are a feature that allow you to offer certain business processes and subsets of drop-down lists to users based on their profiles. Not to be confused with a type of record (such as an account or contact), a record type when used with page layouts and profiles can make only some of the drop-down list values available to users within a profile.

Try adding a filter when editing the dashboard by clicking Add Filter. A filter lets you see different views of dashboard data based on filter conditions. You can add up to three filters per dashboard with up to 10 conditions on a filter. For example, you can filter the entire dashboard by the Invoice Statement: Status field. This will show you total and daily merchandise sold for each invoice status. Instead of filtering at the report level, you directly manipulate dashboard data.

Consider the following information when planning and implementing data categories for your organization:
You can create up to three category groups with a maximum of five hierarchy levels in each group. Each category group can contain a total of 100 categories.
If you want to use data categories in an answers community, after creating your category group you must assign it to a community at Your Name | Setup | Customize | Answers | Data Category Assignments. You can only assign one category group to an answers community. Salesforce Knowledge supports multiple category groups.
Even though you can create up to five hierarchy levels of categories in a category group, only the first level of categories is supported in your answers community. Child categories below the first level are not displayed in the community, and community members can’t assign these child categories to questions. Salesforce Knowledge supports a hierarchy of data categories.

Custom formula fields are not tied to any particular currency. If the result of a formula field is a currency amount, it displays in the currency of the associated record. This is also true for cross-object formulas that reference merge fields with different currencies, and formulas in workflow rules and approval processes. However, note that workflow rules and approval processes that use filters instead of formulas convert all currency values to the corporate currency.

By default, all lookups behave as standard lookups. When searching for records with a standard lookup, only the fields listed in Lookup Search Fields are queried. Standard lookups return up to 50 records at a time in alphabetical order and don’t allow for sorting, filtering, or customizable columns.

Now joint reports can be printed and exported up to 2000 records in excel

Tags are words or short phrases that you can associate with most Salesforce records to describe and organize their data in a personalized way. Use tags to group records from various objects by a common topic or use, and then use those tags in search to make finding information fast and intuitive.
For example, if you met a number of contacts and leads at a conference, you might tag them all with the phrase User Conference 2011. You could then search for the User Conference 2011 tag and click that tag in search results to retrieve those records.
Salesforce supports two types of tags.
Personal tags are private. Only you can view any personal tags that you add to a record.
Public tags are shared among all users in an organization. Any user with access to the record can view the public tags that you add.
Administrators can enable personal and public tags for accounts, activities, assets, campaigns, cases, contacts, contracts, dashboards, documents, events, leads, notes, opportunities, reports, solutions, tasks, and any custom objects (except relationship group members), allowing you to:
Tag records
Remove tags from a record
Browse, search, and manage tags

When you enable tags, you can also add them to a page layout by editing the page layout directly. See Customizing Page Layouts.
Search results and the Tags page don’t display custom objects that don’t have an associated tab, even if tags are enabled for the custom object. If you want custom object records to appear in search results or on the Tags page, you must create an associated tab. The tab doesn’t have to be visible to users.
Customer Portal users can’t view the tags section of a page, even if it is included in a page layout.

Is it possible for an Account to be part of multiple Territories?
Yes, Account can but opportunity can not. A territory is a flexible collection of accounts and users where the users have at least read access to the accounts, regardless of who owns the account. When you enable territory management for your organization, your forecast data is derived from the opportunities that are associated with the accounts in your territories. Users will have a different forecast for each territory to which they are assigned. For example, if you are assigned to both “California” and “Arizona,” you will have one forecast for the opportunities you have in “California,” and another forecast for the opportunities you have in “Arizona”

Manually transferring records will not trigger Assignment or Escalation Rules.

Description
Why are Escalation Rules not triggering?

Resolution
Often times, when setting up escalation rules you will want to include an ownership field within that rule. When doing so you will need to keep some potential issues in mind.

1. Assignment Rules that transfer inbound cases from your web to case to a queue or a potential owner will evaluate the escalation rule and then assign the case.

Example:
Once a case is submitted, it will move through the escalation rules and trigger if it meets a criteria. Afterward, the case will be evaluated by the Assignment Rules and be redirected accordingly. If the escalation rule included a filter that referenced ownership after the assignment, the escalation will not be triggered.

2. Manually transferring records will not trigger Assignment or Escalation Rules.

Example:
An escalation rule dictates that any cases owned by User 2 will be escalated after 30 minutes.

A case is owned by User 1. The case is then manually transferred from User 1 to User 2. This does not modify the record and does not change the last modified date. Hence, the escalation rules are not triggered.

If you opt to have Ownership involved with your escalation rules, you will need to include any users that may transfer these records to another user.

Connection Finder (Salesforce to Salesforce) allows you to email surveys to find out if your partners are Salesforce customer

Opportunity is included in territory management but not lead and activity.

If a user accesses a login URL that does not contain a unique identifier of a specific Customer Portal, then they are automatically directed to the login URL of the first Customer Portal you created – True

Division on individual records—Division is a field on individual records which marks the record as belonging to a particular division. A record can belong to a division that the administrator creates, or it can belong to the standard “global” division which is created automatically when your organization enables divisions.
Default division for a user—Users are assigned to a default division that applies to their newly created accounts, leads, and custom objects that are enabled for divisions.
Working division—If you have the “Affected by Divisions” permission, you set the division in which you want to work using a drop-down list in the sidebar. Then, searches will show only the data for your working division. You can change your working division at any time. If you do not have the “Affected by Divisions” permission, you do not have a working division; you always see records in all divisions.

The organization IDs of your sandboxes differ from your production organization ID, and will change each time your sandbox is refreshed.
Salesforce stores sandbox organizations on several instances. When a sandbox is created or refreshed, an instance is selected for your sandbox, so your sandbox may appear on different instances and have different URLs.
When data that contains object IDs is copied from your production instance into your sandbox, the object IDs in your sandbox match the object IDs in your production instance. However, data created in your production instance or sandbox will not contain matching object IDs.

Full copy sandboxes have the same storage limit as your production organization.
Configuration-only sandboxes have a 500 MB storage limit.
Developer sandboxes have a 10 MB storage limit.
Sandboxes don’t send email notifications when storage limits are reached. However, if you reach the storage limit of your sandbox, you cannot save new data in your sandbox.

External users cannot follow records!!
Permissions are to access objects and fields, and settings are to specify which record types, page layouts, and tabs are visible.
Object permissions control create, edit, delete data.

Role hierarchies don’t necessarily need to match your org chart exactly. Instead, each role in the hierarchy should just represent a level of data access that a user or group of users needs. For example, suppose your organization employs a corporate lawyer who needs to access all of the records in the app. One easy way to accomplish this is by assigning the lawyer to the CEO role in your organization’s role hierarchy. Since the CEO role is placed at the top of the hierarchy, anyone assigned to that role automatically gets full access to any record in the organization. It doesn’t matter that technically the lawyer appears below the CEO in the regular org chart.

Profile you do
Role you see

How can a system admin grant user access to dashboards?
1.Share folders with public groups, roles
2.Choose running user: run as logged-in user

Custom report types allow you to build a framework in the report wizard, from which users can create and customize reports. You build custom report types off of the relationships (master-detail and lookup) between objects so that you can:
oChoose which standard and custom objects to display to users creating and customizing reports
oDefine the relationships between objects displayed to users creating and customizing reports
oSelect which objects’ fields can be used as columns in reports

Each value in the opportunity Stage picklist is automatically mapped to a Probability and value in the Forecast Category picklist. Change the Stage of an opportunity and the Probability as well as the Forecast Category changes with it.

Schedule Type: Defines whether the product revenue or quantity will be divided into multiple installments or repeated for multiple installments.
Installment Period: Sets the interval for installments; for example, Weekly, Monthly.
Number of Installments: Number of installments in the schedule.

Mass Transfer Accounts

Help for this Page
This screen allows you to transfer an account from one user to another. When you transfer ownership of an account, the new owner will also gain ownership of the following records related to the transferred account:
oAny notes that belong to the existing owner.
oAll contacts that belong to the existing owner.
oAll opportunities (including closed opportunities if you select the Transfer closed opportunities checkbox below) that belong to the existing owner.
oAll open activities assigned to the existing owner. Note that completed activities will not be transferred.
oThe new owner might need to edit sharing.
oAll open and closed cases

Delegated administrators can perform the following tasks:
oCreating and editing users and resetting passwords for users in specified roles and all subordinate roles, including setting quotas, creating default opportunity teams, and creating personal groups for those users
oUnlocking non-portal users
oAssigning users to specified profiles
oLogging in as a user who has granted login access to their administrator
oManaging custom objects created by an administrator

Default lead owner: The user or queue to which leads will be assigned if the active assignment rule fails to locate an owner.

Match the automation rules with the order in which they are processed:
1.Validation Rules
2.Assignment rules
3.Workflow rules
4.Escalation rules

You can create criteria based sharing rules for accounts, opportunities, cases, contacts, and custom objects.