The document provides an overview of deploying the Salesforce connector in Coveo, including creating a Salesforce user identity, getting Salesforce client ID and secret values, configuring an ObjectsToGet file to specify what content to retrieve, configuring a mapping file to map fields to the index, and configuring a Salesforce source. It also discusses indexing standard and custom objects, knowledge base articles, Chatter, and CRM content from Salesforce.
Elements_Architecture_and_Technology.pdfJeff Smith
The document discusses the architecture and technology of Alfresco's enterprise content management system. It describes Alfresco's layered architecture with separate storage, repository, and client layers. The repository layer provides various protocols and APIs for client applications to connect. Key points include that Alfresco uses a database for metadata and file system for content storage, and supports various operating systems, databases, application servers and other technologies.
This document provides an overview of the security measures used in ShareFile Enterprise, an enterprise file sync and sharing solution. It describes the three main components: 1) the SaaS application tier which includes web, API and database servers, 2) StorageZones which store customer data either in Citrix-managed cloud storage or customer-managed storage, and 3) clients which access ShareFile across various devices. It then details how each component uses encryption, hashing, access controls and other methods to securely transmit and store customer data and metadata.
This document provides a step-by-step guide to configure identity federation between Moodle, Active Directory Federation Services 2.0 (AD FS 2.0), and Windows Azure Active Directory. This setup enables single sign-on access to Moodle and Office 365 using federated identities. It also supports user autoprovisioning in Moodle and automatic course enrollment based on Active Directory group membership. The guide outlines prerequisites, requirements, and configuration instructions for AD FS 2.0, Moodle, SimpleSAMLPHP, and relevant Moodle plugins to enable the federated identity and access management capabilities.
The document summarizes new security features in Oracle Advanced Security for Oracle8i Release 8.1.6, including enhancements to encryption, authentication, authorization, and single sign-on. It provides stronger encryption algorithms, secures additional protocols like IIOP and JDBC, and adds support for SSL-based single sign-on and integration with directory services and PKI solutions like Entrust for centralized user management across databases.
#Epicor #ERP 10 Architected for EfficiencyIndex InfoTech
Epicor ERP 10 has been built from the ground up to comprehensively respond to these needs and provide the support organizations require to thrive in today’s competitive global business landscape. Guided by the needs of today’s organizations, Epicor ERP 10 streamlines the use of ERP across multiple devices while providing greater deployment choices, reduced complexity, and remarkable ease-of-use. Built on agile technology to provide rich, global functionality, we believe it is a truly inspired ERP solution, one that not only unleashes the full potential of ERP, but also changes its role from necessary infrastructure to active facilitator of business growth and sustainability.
This document introduces Alfresco, an open source enterprise content management system. It discusses Alfresco's functionality for document management, collaboration, and business processes. It describes the different user experiences and editions of Alfresco, including Community for non-critical use and Enterprise for production environments. The document provides examples of organizations using Alfresco and concludes with a summary of the key points covered.
Oracle Forms 11g Release 2 includes new features to improve integration with Oracle Access Manager for authentication and authorization, reduce the installation footprint for development, and improve performance monitoring. It also adds support for new platforms including Windows 64-bit and allows more granular monitoring of user interactions through Real User Experience Interaction.
This document provides an overview of the key changes and new features in SharePoint 2010 compared to SharePoint 2007. It discusses the new service application architecture in SharePoint 2010 and how services like search, user profiles, and business data are now decoupled from SharePoint. It also provides guidance on hardware requirements, software prerequisites, and steps for installing and configuring SharePoint 2010.
Elements_Architecture_and_Technology.pdfJeff Smith
The document discusses the architecture and technology of Alfresco's enterprise content management system. It describes Alfresco's layered architecture with separate storage, repository, and client layers. The repository layer provides various protocols and APIs for client applications to connect. Key points include that Alfresco uses a database for metadata and file system for content storage, and supports various operating systems, databases, application servers and other technologies.
This document provides an overview of the security measures used in ShareFile Enterprise, an enterprise file sync and sharing solution. It describes the three main components: 1) the SaaS application tier which includes web, API and database servers, 2) StorageZones which store customer data either in Citrix-managed cloud storage or customer-managed storage, and 3) clients which access ShareFile across various devices. It then details how each component uses encryption, hashing, access controls and other methods to securely transmit and store customer data and metadata.
This document provides a step-by-step guide to configure identity federation between Moodle, Active Directory Federation Services 2.0 (AD FS 2.0), and Windows Azure Active Directory. This setup enables single sign-on access to Moodle and Office 365 using federated identities. It also supports user autoprovisioning in Moodle and automatic course enrollment based on Active Directory group membership. The guide outlines prerequisites, requirements, and configuration instructions for AD FS 2.0, Moodle, SimpleSAMLPHP, and relevant Moodle plugins to enable the federated identity and access management capabilities.
The document summarizes new security features in Oracle Advanced Security for Oracle8i Release 8.1.6, including enhancements to encryption, authentication, authorization, and single sign-on. It provides stronger encryption algorithms, secures additional protocols like IIOP and JDBC, and adds support for SSL-based single sign-on and integration with directory services and PKI solutions like Entrust for centralized user management across databases.
#Epicor #ERP 10 Architected for EfficiencyIndex InfoTech
Epicor ERP 10 has been built from the ground up to comprehensively respond to these needs and provide the support organizations require to thrive in today’s competitive global business landscape. Guided by the needs of today’s organizations, Epicor ERP 10 streamlines the use of ERP across multiple devices while providing greater deployment choices, reduced complexity, and remarkable ease-of-use. Built on agile technology to provide rich, global functionality, we believe it is a truly inspired ERP solution, one that not only unleashes the full potential of ERP, but also changes its role from necessary infrastructure to active facilitator of business growth and sustainability.
This document introduces Alfresco, an open source enterprise content management system. It discusses Alfresco's functionality for document management, collaboration, and business processes. It describes the different user experiences and editions of Alfresco, including Community for non-critical use and Enterprise for production environments. The document provides examples of organizations using Alfresco and concludes with a summary of the key points covered.
Oracle Forms 11g Release 2 includes new features to improve integration with Oracle Access Manager for authentication and authorization, reduce the installation footprint for development, and improve performance monitoring. It also adds support for new platforms including Windows 64-bit and allows more granular monitoring of user interactions through Real User Experience Interaction.
This document provides an overview of the key changes and new features in SharePoint 2010 compared to SharePoint 2007. It discusses the new service application architecture in SharePoint 2010 and how services like search, user profiles, and business data are now decoupled from SharePoint. It also provides guidance on hardware requirements, software prerequisites, and steps for installing and configuring SharePoint 2010.
SharePoint 2010 includes new developer tools and features. It focuses on social networking capabilities, improved workflows, and connectivity to external systems and data. Developers can now create SharePoint applications using Microsoft Visual Studio 2010 or SharePoint Designer 2010 on client operating systems. The platform investments in SharePoint 2010 include LINQ, REST APIs, and enhancements to workflows, external lists, and client APIs.
Oracle8i Release 8.1.6 includes several new security features including data encryption capabilities, enhancements to virtual private databases, and enterprise user management. It allows encryption of sensitive data in the database, improves access controls in virtual private databases, and introduces centralized management of users and authorization across multiple databases through integration with Oracle Internet Directory.
Using oracle-erp-cloud-adapter-oracle-integrationSwapnil Khoke
The document provides information about using the Oracle ERP Cloud Adapter with Oracle Integration. It discusses the adapter's capabilities including supported business events for SCM, procurement, financials, and project portfolio management applications. It also describes restrictions, supported application versions, and the typical workflow for creating an adapter connection and adding it to an integration. Common integration patterns using the adapter are demonstrated, such as configuring callbacks, uploading files, invoking endpoints dynamically, and invoking import jobs. Troubleshooting tips are also provided.
WebSphere Application Server V8.5 introduces the Liberty profile which provides a simpler and more dynamic runtime for web applications compared to the traditional static profile. It also includes enhancements to developer experience such as support for Java SE 7, OSGi Blueprint for EJBs, and improved application migration and IDE tools. New features for application resiliency include Intelligent Management which provides capabilities for intelligent routing, dynamic clustering, and health management to improve application performance and availability.
The document provides an overview of the key features and capabilities of IIS 7.0 compared to Apache, including its extensible modular architecture, enhanced security features, improved management tools, strong support for web applications, and flexible extensibility model. It also describes IIS 7.0's integrated request pipeline, configuration and management options, and diagnostic and troubleshooting features.
Storage Made Easy’s Enterprise File Fabric, and Memset's secure Cloud IaaS -powered by OpenStack- provides a simple, fast, and secure way to achieve GDPR compliance for UK and European companies.
SharePoint 2010,Claims-Based Identity, Facebook, and the CloudDanny Jessee
The document discusses integrating Facebook authentication with SharePoint 2010. It covers:
1. Configuring an app in Facebook and Azure ACS to enable Facebook login and pass claims to SharePoint.
2. Configuring SharePoint to trust tokens from ACS and map claims to SharePoint properties.
3. Using the Facebook access token to call the Facebook API and retrieve user data to display in SharePoint.
Biz Talk Adapter Pack 2 0 Oracle Ebs Adapter Data Sheetkaushiksin
The Oracle E-Business Suite Adapter allows connectivity between Oracle E-Business Suite and other applications. It exposes Oracle E-Business Suite artifacts as web services and supports interfaces, APIs, datatypes and multi-language features. The adapter will be included in the upcoming BizTalk Adapter Pack 2.0 alongside a SQL Server adapter.
This document provides instructions for installing and configuring a plugin that integrates Moodle with Microsoft Office 365. The plugin allows teachers to create courses and assignments in Moodle that can be accessed and submitted by students through SharePoint. The document outlines system requirements, provides step-by-step instructions for installing the plugin modules in both Moodle and SharePoint, and describes how to configure authentication and permissions. It also explains how students and teachers can use features enabled by the integration such as viewing courses, submitting assignments, and managing user accounts from both Moodle and Office 365.
Internet Explorer 8 Deployment - IE8 FirestarterMithun T. Dhar
Video recordings of this session can be found here:
1. http://channel9.msdn.com/tags/IE%208%20Firestarter - (Developer)
2. http://edge.technet.com/Tags/IE+8+Firestarter/ - (IT Pro's)
If you need to download this file, or need more infomation contact Mithun Dhar via http://blogs.msdn.com/mithund
Top 5 Share Point 2010 Questions Answeredimason Inc.
The document discusses the top 5 questions about SharePoint 2010:
1. The release date is May 12, 2010 and will be available on retail shelves in June.
2. Licensing is expected to be similar to previous versions with Foundation being free and Standard/Enterprise requiring server and CAL licenses.
3. Deploying new functionality should wait for SP1, but existing features can be deployed on launch. Migration from 2007 allows controlling the timing and previewing upgrades.
4. Migration from 2007 or 2003 requires recompiling and testing code, adjusting as needed, and upgrading all data (no direct path from 2003). Effort ranges from 50k-250k depending on size.
5
Planning for clients and devices lync server 2010 (rc)Daniel Ullmark
A guide to the variety of unified communications clients and devices you can deploy for your users. (Planning for Clients and Devices Lync Server 2010 (RC).doc)
The Enterprise File Fabric for Vecima MediaScaleXHybrid Cloud
The Enterprise File Fabric™ platform is a comprehensive multi-cloud data security solution built on top of the SME ‘Cloud Control’ Gateway. The SME Cloud Control Gateway allows IT to control and set policies on Vecima data in addition to providing a simplified access mechanism to Vecima data.
The document summarizes the key features and enhancements in the Winter 15 release of Salesforce. Some of the major enhancements include improved Visualforce and Apex functionality, new capabilities for Salesforce1 mobile app development like adding charts from reports to flexible pages, and enhancements to Salesforce1 mobile app features such as viewing events in a weekly view and cloning contact records. It also provides details on new capabilities for administrators, developers and users across areas like user interface, app logic, integration, tools and more.
This document summarizes new features and changes in Salesforce, including:
- The ability to create multiple calendars from different fields in Lightning Experience.
- Allowing contacts to be related to multiple accounts by enabling the "Allow users to relate a contact to multiple accounts" setting.
- Enhancements to Email Studio like the built-in preview feature and Content Builder for customizing emails.
- The Salesforce Marketing Cloud mobile app providing access to key features from a mobile device like scheduled activities and campaign tracking.
Your data is one of your biggest assets and protecting it is paramount. Xoomworks BI have found that many organisations have inefficient security models that lead to costly overheads and potential security breaches. Designing a flexible, legally compliant Security model to safeguard your data, which has the capacity for easy maintenance and expansion is a must.
This presentation covers how to build and maintain a flexible Security Model, the problems that could arise from improper management, as well as the different types of Authentication in an Enterprise Environment, including using the Security Token service to your benefit
The document provides an overview of new features and enhancements in Salesforce across various areas including the user interface, development tools, security, mobile, communities, sales, service, and more. Key updates include improved duplicate record management, the ability to create or edit records owned by inactive users, adding rich text notes to records, and delegated administrators now able to create public groups. The release includes over 250 new features across the Salesforce platform.
Alfresco Summit 2013 Presentation by Jared Ottley and Will Abson. Discuss how the Alfresco for Salesforce Integration works; How to get and install the integration; Challenges; ideas for for future releases.
CSE681 – Software Modeling and Analysis Fall 2013 Project .docxfaithxdunce63732
CSE681 – Software Modeling and Analysis Fall 2013
Project #5 – Source Code Repository Architecture Document
due Monday, Dec 9th
Version 2.2
Purpose:
This project develops an Operational Concept Document (OCD) for a Source Code Repository client and server. The
purpose of the Repository is to enable insertion and extraction of source code files into a project’s baseline and to
display information about their properties and relationships. Authenticated check-in and versioning are required.
The Repository client displays information about Repository files in a Graphical User Interface (GUI) with several
panes used to display some metadata properties and text of the current file and panes to show the child and parent
dependencies. Clicking on a child or parent makes that file the current file. File caching on Repository and its clients
is required to avoid unnecessary file transfers.
Context:
This Repository is one member of a server federation, illustrated in Figure 1., designed to support software
development. Other members of the federation are a Test server, providing a test harness supporting continuous
integration, and a Project server that stores and publishes project management information and supports
collaborative communication through virtual meetings1 and shared document resources.
All of the federated servers are designed as distributed virtual servers. This means that: they can be run in virtual
environments, server contents can be distributed across several server instances, and that they provide a cloning
facility that will allow any authenticated user to create an instance on a local desktop with a specified subset of the
source server contents, and that new and modified contents can be checked into the source server. This allows local
use of the development environment for initial creation and testing before inserting the new products into the
project’s baseline.
In Figure 1, below, we show the Federated Server context in which the Repository server must operate. We see that
all the servers collaborate through message-passing communication to provide a powerful software development
environment. The Repository’s role is to manage a project’s current baseline, e.g., the collection of its
documentation and source code.
The Project server manages all of the data required to manage a large project, e.g., definition of work packages and
their schedules and assigned responsible individuals, and means to support collaboration between project teams,
some of which may be in remote locations. As an example, Figure 2 shows a hypothetical package structure for the
Project server. This illustrates the level of detail needed to capture the concept for a large federated system. The
Repository server will need a similar, though not identical, package structure.
The Test server supports continuous test and integration. Whenever a new package is inserted or an existing
pa.
bfx and studio server - Bluebeam eXtreme Conference 2014bluebeamslides
Bluebeam develops advanced technologies to seamlessly work with your enterprise systems. Bluebeam’s bFX protocol enables Revu to open PDF files from a remote location, such as a website, add markups and post them back to the remote location. Studio Server allows you to host collaboration sessions behind your own firewall for enhanced security.
ESM Asset Model FlexConnector Developer's Guide for ESM 6.8cProtect724v3
The document provides instructions on installing and configuring the Asset Model Import FlexConnector to import asset model data from CSV files into the ArcSight ESM network model. It describes prerequisites, supported platforms, installing the connector, configuring it with CSV file locations and parsers, and setting the model import user. An example CSV format and default parser template are also provided.
SharePoint 2010 includes new developer tools and features. It focuses on social networking capabilities, improved workflows, and connectivity to external systems and data. Developers can now create SharePoint applications using Microsoft Visual Studio 2010 or SharePoint Designer 2010 on client operating systems. The platform investments in SharePoint 2010 include LINQ, REST APIs, and enhancements to workflows, external lists, and client APIs.
Oracle8i Release 8.1.6 includes several new security features including data encryption capabilities, enhancements to virtual private databases, and enterprise user management. It allows encryption of sensitive data in the database, improves access controls in virtual private databases, and introduces centralized management of users and authorization across multiple databases through integration with Oracle Internet Directory.
Using oracle-erp-cloud-adapter-oracle-integrationSwapnil Khoke
The document provides information about using the Oracle ERP Cloud Adapter with Oracle Integration. It discusses the adapter's capabilities including supported business events for SCM, procurement, financials, and project portfolio management applications. It also describes restrictions, supported application versions, and the typical workflow for creating an adapter connection and adding it to an integration. Common integration patterns using the adapter are demonstrated, such as configuring callbacks, uploading files, invoking endpoints dynamically, and invoking import jobs. Troubleshooting tips are also provided.
WebSphere Application Server V8.5 introduces the Liberty profile which provides a simpler and more dynamic runtime for web applications compared to the traditional static profile. It also includes enhancements to developer experience such as support for Java SE 7, OSGi Blueprint for EJBs, and improved application migration and IDE tools. New features for application resiliency include Intelligent Management which provides capabilities for intelligent routing, dynamic clustering, and health management to improve application performance and availability.
The document provides an overview of the key features and capabilities of IIS 7.0 compared to Apache, including its extensible modular architecture, enhanced security features, improved management tools, strong support for web applications, and flexible extensibility model. It also describes IIS 7.0's integrated request pipeline, configuration and management options, and diagnostic and troubleshooting features.
Storage Made Easy’s Enterprise File Fabric, and Memset's secure Cloud IaaS -powered by OpenStack- provides a simple, fast, and secure way to achieve GDPR compliance for UK and European companies.
SharePoint 2010,Claims-Based Identity, Facebook, and the CloudDanny Jessee
The document discusses integrating Facebook authentication with SharePoint 2010. It covers:
1. Configuring an app in Facebook and Azure ACS to enable Facebook login and pass claims to SharePoint.
2. Configuring SharePoint to trust tokens from ACS and map claims to SharePoint properties.
3. Using the Facebook access token to call the Facebook API and retrieve user data to display in SharePoint.
Biz Talk Adapter Pack 2 0 Oracle Ebs Adapter Data Sheetkaushiksin
The Oracle E-Business Suite Adapter allows connectivity between Oracle E-Business Suite and other applications. It exposes Oracle E-Business Suite artifacts as web services and supports interfaces, APIs, datatypes and multi-language features. The adapter will be included in the upcoming BizTalk Adapter Pack 2.0 alongside a SQL Server adapter.
This document provides instructions for installing and configuring a plugin that integrates Moodle with Microsoft Office 365. The plugin allows teachers to create courses and assignments in Moodle that can be accessed and submitted by students through SharePoint. The document outlines system requirements, provides step-by-step instructions for installing the plugin modules in both Moodle and SharePoint, and describes how to configure authentication and permissions. It also explains how students and teachers can use features enabled by the integration such as viewing courses, submitting assignments, and managing user accounts from both Moodle and Office 365.
Internet Explorer 8 Deployment - IE8 FirestarterMithun T. Dhar
Video recordings of this session can be found here:
1. http://channel9.msdn.com/tags/IE%208%20Firestarter - (Developer)
2. http://edge.technet.com/Tags/IE+8+Firestarter/ - (IT Pro's)
If you need to download this file, or need more infomation contact Mithun Dhar via http://blogs.msdn.com/mithund
Top 5 Share Point 2010 Questions Answeredimason Inc.
The document discusses the top 5 questions about SharePoint 2010:
1. The release date is May 12, 2010 and will be available on retail shelves in June.
2. Licensing is expected to be similar to previous versions with Foundation being free and Standard/Enterprise requiring server and CAL licenses.
3. Deploying new functionality should wait for SP1, but existing features can be deployed on launch. Migration from 2007 allows controlling the timing and previewing upgrades.
4. Migration from 2007 or 2003 requires recompiling and testing code, adjusting as needed, and upgrading all data (no direct path from 2003). Effort ranges from 50k-250k depending on size.
5
Planning for clients and devices lync server 2010 (rc)Daniel Ullmark
A guide to the variety of unified communications clients and devices you can deploy for your users. (Planning for Clients and Devices Lync Server 2010 (RC).doc)
The Enterprise File Fabric for Vecima MediaScaleXHybrid Cloud
The Enterprise File Fabric™ platform is a comprehensive multi-cloud data security solution built on top of the SME ‘Cloud Control’ Gateway. The SME Cloud Control Gateway allows IT to control and set policies on Vecima data in addition to providing a simplified access mechanism to Vecima data.
The document summarizes the key features and enhancements in the Winter 15 release of Salesforce. Some of the major enhancements include improved Visualforce and Apex functionality, new capabilities for Salesforce1 mobile app development like adding charts from reports to flexible pages, and enhancements to Salesforce1 mobile app features such as viewing events in a weekly view and cloning contact records. It also provides details on new capabilities for administrators, developers and users across areas like user interface, app logic, integration, tools and more.
This document summarizes new features and changes in Salesforce, including:
- The ability to create multiple calendars from different fields in Lightning Experience.
- Allowing contacts to be related to multiple accounts by enabling the "Allow users to relate a contact to multiple accounts" setting.
- Enhancements to Email Studio like the built-in preview feature and Content Builder for customizing emails.
- The Salesforce Marketing Cloud mobile app providing access to key features from a mobile device like scheduled activities and campaign tracking.
Your data is one of your biggest assets and protecting it is paramount. Xoomworks BI have found that many organisations have inefficient security models that lead to costly overheads and potential security breaches. Designing a flexible, legally compliant Security model to safeguard your data, which has the capacity for easy maintenance and expansion is a must.
This presentation covers how to build and maintain a flexible Security Model, the problems that could arise from improper management, as well as the different types of Authentication in an Enterprise Environment, including using the Security Token service to your benefit
The document provides an overview of new features and enhancements in Salesforce across various areas including the user interface, development tools, security, mobile, communities, sales, service, and more. Key updates include improved duplicate record management, the ability to create or edit records owned by inactive users, adding rich text notes to records, and delegated administrators now able to create public groups. The release includes over 250 new features across the Salesforce platform.
Alfresco Summit 2013 Presentation by Jared Ottley and Will Abson. Discuss how the Alfresco for Salesforce Integration works; How to get and install the integration; Challenges; ideas for for future releases.
CSE681 – Software Modeling and Analysis Fall 2013 Project .docxfaithxdunce63732
CSE681 – Software Modeling and Analysis Fall 2013
Project #5 – Source Code Repository Architecture Document
due Monday, Dec 9th
Version 2.2
Purpose:
This project develops an Operational Concept Document (OCD) for a Source Code Repository client and server. The
purpose of the Repository is to enable insertion and extraction of source code files into a project’s baseline and to
display information about their properties and relationships. Authenticated check-in and versioning are required.
The Repository client displays information about Repository files in a Graphical User Interface (GUI) with several
panes used to display some metadata properties and text of the current file and panes to show the child and parent
dependencies. Clicking on a child or parent makes that file the current file. File caching on Repository and its clients
is required to avoid unnecessary file transfers.
Context:
This Repository is one member of a server federation, illustrated in Figure 1., designed to support software
development. Other members of the federation are a Test server, providing a test harness supporting continuous
integration, and a Project server that stores and publishes project management information and supports
collaborative communication through virtual meetings1 and shared document resources.
All of the federated servers are designed as distributed virtual servers. This means that: they can be run in virtual
environments, server contents can be distributed across several server instances, and that they provide a cloning
facility that will allow any authenticated user to create an instance on a local desktop with a specified subset of the
source server contents, and that new and modified contents can be checked into the source server. This allows local
use of the development environment for initial creation and testing before inserting the new products into the
project’s baseline.
In Figure 1, below, we show the Federated Server context in which the Repository server must operate. We see that
all the servers collaborate through message-passing communication to provide a powerful software development
environment. The Repository’s role is to manage a project’s current baseline, e.g., the collection of its
documentation and source code.
The Project server manages all of the data required to manage a large project, e.g., definition of work packages and
their schedules and assigned responsible individuals, and means to support collaboration between project teams,
some of which may be in remote locations. As an example, Figure 2 shows a hypothetical package structure for the
Project server. This illustrates the level of detail needed to capture the concept for a large federated system. The
Repository server will need a similar, though not identical, package structure.
The Test server supports continuous test and integration. Whenever a new package is inserted or an existing
pa.
bfx and studio server - Bluebeam eXtreme Conference 2014bluebeamslides
Bluebeam develops advanced technologies to seamlessly work with your enterprise systems. Bluebeam’s bFX protocol enables Revu to open PDF files from a remote location, such as a website, add markups and post them back to the remote location. Studio Server allows you to host collaboration sessions behind your own firewall for enhanced security.
ESM Asset Model FlexConnector Developer's Guide for ESM 6.8cProtect724v3
The document provides instructions on installing and configuring the Asset Model Import FlexConnector to import asset model data from CSV files into the ArcSight ESM network model. It describes prerequisites, supported platforms, installing the connector, configuring it with CSV file locations and parsers, and setting the model import user. An example CSV format and default parser template are also provided.
Have you been hacking some JavaScript to enable your users to do more, directly in the Chatter feed? Hack no more! in Winter '15 you can define, invoke, and debug Action Links in Force.com. If you are familiar with our REST APIs and Chatter, join the engineers who delivered this feature for a walkthrough of tools, code samples, and resources. You'll come away ready to create your own action links.Have you been hacking some JavaScript to enable your users to do more, directly in the Chatter feed? Hack no more! in Winter '15 you can define, invoke, and debug Action Links in Force.com. If you are familiar with our REST APIs and Chatter, join the engineers who delivered this feature for a walkthrough of tools, code samples, and resources. You'll come away ready to create your own action links.
These are the slides of the Paris Salesforce Developer Group Meetup that took place on the 16th of September. The topic was Salesforce.com Summer '14 release.
Elements_Architecture_and_Technology.pdfJeff Smith
The document discusses the architecture and technology of Alfresco's enterprise content management system. It has a layered architecture with separate storage, repository, and client layers that can be deployed independently. The repository layer provides various APIs and protocols for client applications to connect. It also uses a database to store metadata and the file system to store content directly for high performance. The system is designed to be scalable, technology agnostic, and to support a variety of operating systems, databases, servers, and third-party integrations.
Elements_Architecture_and_Technology.pdfJeff Smith
The document discusses the architecture and technology of the Alfresco enterprise content management system. It describes Alfresco's layered architecture with separate storage, repository, and client layers. The repository layer provides content services, control services, and collaboration services. Content is stored in a database for metadata and file system for content. Key architectural decisions for deploying Alfresco include separating the database, content server, and frontend onto different machines for performance and scalability.
Elements_Architecture_and_Technology.pdfJeff Smith
The document discusses the architecture and technology of the Alfresco enterprise content management system. It describes Alfresco's layered architecture with separate storage, repository, and client layers. The repository layer provides content services, control services, and collaboration services. Content is stored in a database for metadata and file system for content. Key architectural decisions for deploying Alfresco include separating the database, content server, and frontend onto different machines for performance and scalability.
Elements_Architecture_and_Technology.pdfJeff Smith
The document discusses the architecture and technology of the Alfresco enterprise content management system. It describes Alfresco's layered architecture with separate storage, repository, and client layers. The repository layer provides content services, control services, and collaboration services. Content is stored in a database for metadata and file system for content. Key architectural decisions for deploying Alfresco include separating the database, content server, and frontend onto different machines for performance and scalability.
This chapter describes how to construct SOAP messages to process transactions with CyberSource using PHP 5.2.1. It provides instructions for downloading required third-party software, extending the SoapClient class to add WS-Security headers, and testing transactions using sample code provided. Developers can then modify the script and client code to integrate it with their application.
HP ArcSight Asset Model Import FlexConnector Developer's GuideProtect724tk
The document provides information about installing and configuring the HP ArcSight Asset Model Import FlexConnector, which allows importing asset model data from a CSV file into the ArcSight ESM network model. It describes prerequisites, installing the FlexConnector, configuring it to point to the CSV files and associated parsers, and running the connector. It also provides a template for the required parser files to match the CSV file format.
This is an overview of the key developer changes that the Spring '14 release to the Salesforce.com platform is going to bring. From Salesforce 1 to the Developer Console.
The presentation was delivered at the South West UK Developer User Group on March 5th by Force.com MVP Chris Lewis and Community Organiser Simon Lawrence.
This document provides instructions for installing and configuring the Asset Model Import FlexConnector in ArcSight ESM. It discusses prerequisites, supported platforms, and the installation process. It also covers configuring the FlexConnector, including running SmartConnectors, setting the model import user, CSV file format and parsing examples, and reloading asset model data. The goal is to enable importing asset model data from files into the ESM network model and keeping the data synchronized.
This document provides instructions for installing and configuring the Asset Model Import FlexConnector in ArcSight ESM. It assumes familiarity with writing FlexConnectors. The FlexConnector imports asset data from CSV files into the ESM network model based on a configured parser. It supports initial import and ongoing detection of updates. The document describes prerequisites, supported platforms, installation steps, configuration options and reloading of asset data.
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. 🚀 This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. 💻
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. 🖥️
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. 🌟
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...alexjohnson7307
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
3. Coveo Platform 7.0 | Salesforce Connector Guide
Table of Contents
1. Salesforce Connector 1
1.1 Advantages Relative to the Legacy Connector 1
1.2 Connector Features Summary 1
1.3 Features 2
2. Salesforce Connector Deployment Overview 8
3. Salesforce Connector Requirements 10
4. Creating a Salesforce User Identity 11
4.1 Creating a Dedicated Salesforce Crawling Account 12
4.2 Getting the Security Token for Your Salesforce Account 14
5. Getting Salesforce Client_ID and Client_Secret Values 16
6. Salesforce ObjectsToGet Configuration File 21
6.1 Salesforce Object Definition 21
6.2 Configuration File Elements 22
6.3 XML Schema Definition 33
6.4 Creating a Salesforce ObjectsToGet Configuration File 35
6.5 Salesforce ObjectsToGet Configuration File Example for Standard Objects 36
6.6 Salesforce ObjectsToGet Configuration File Example for Knowledge Base 48
6.7 Salesforce ObjectsToGet Configuration File Example for CRM Content 51
6.8 Salesforce ObjectsToGet Configuration File Example for Chatter Objects 54
6.9 Salesforce Connector Configuration Recipes 57
6.9.1 Indexing all Knowledge Base Versions and States 57
6.9.2 Excluding Archived Knowledge Base Articles 60
6.9.3 Indexing Knowledge Base Attachments 61
6.9.4 Fetching Records With Parent Relationships That Must Be Incrementally Updated 61
6.9.5 Fetching Child Relationship to Use for Folding 63
6.9.6 Fetch Child Relationship to Use to Increase or Reduce Results From Queries 63
6.9.7 Minimizing API Calls and Object Description Prefetching 64
6.9.8 Fetching Records Faster Using the Turbo Mode Runner 64
6.9.9 Reducing the Metadata Package Size by Scoping Parents of ContentVersion and Attachment
Objects 66
4www.coveo.com iii
4. Coveo Platform 7.0 | Salesforce Connector Guide
6.9.10 Choosing the Optimal Record Modification Date Field 67
6.9.11 Removing Leading Zeroes of a Field 67
6.9.12 Using the Currency Field Converter 67
6.9.13 Using the FiscalYearResolver 67
6.9.14 Fixing the Feed Tracking Error 67
6.9.15 Indexing More Than the Built-in FeedItem Types 68
7. Creating a Salesforce Mapping File 69
7.1 Salesforce Mapping File Example for Standard Objects 70
7.2 Salesforce Mapping File Example for Knowledge Base 88
7.3 Salesforce Mapping File Example for CRM Content 92
7.4 Salesforce Mapping File Example for Chatter Objects 96
8. Configuring a Salesforce Security Provider 98
8.1 Configuring an Email Security Provider 100
8.2 Configuring an Active Directory Security Provider 102
9. Configuring and Indexing a Salesforce Source 105
9.1 Modifying Hidden Salesforce Source Parameters 111
9.2 Adding an Explicit Connector Parameter 114
10. Troubleshooting Salesforce Connector Issues 117
10.1 API Security Token Required 117
10.2 Expired Access/Refresh Token 117
10.3 Missing ionic.zip File 117
11. Refreshing Security Caches 118
4www.coveo.com iv
5. Coveo Platform 7.0 | Salesforce Connector Guide
1. Salesforce Connector
CES 7.0.5785+ (August 2013)
The on-premises Salesforce connector is part of the Coveo for Salesforce license and is therefore available only
with Coveo for Salesforce (see Coveo for Salesforce).
The Coveo Salesforce connector allows you to crawl Salesforce content and bring it into the unified index, making it
easily searchable by end-users.
Important: Salesforce no longer supports TLS 1.0 which is used by the Coveo connector for Salesforce in CES 7.0.8047– (December
to retrieve Salesforce content and content updates. In the CES Console, you will get errors such as:
Salesforce2 Error: Could not establish secure channel for SSL/TLS with authority
'domain.salesforce.com'
You must thus upgrade CES to CES 7.0.8225+ (March 2016). Otherwise, you will no longer be able to update
your Salesforce source content.
1.1 Advantages Relative to the Legacy Connector
This second generation Salesforce connector offers the following advantages over the Salesforce Legacy
connector:
l Indexing of Salesforce permissions rather than applying the same permission on all source items (see
"Indexed Salesforce Security" on page 2)
l Improved performance and reduced API calls
l Indexing of Knowledge Base articles and CRM content files
l Takes advantage of recent Salesforce API versions
1.2 Connector Features Summary
Features Supported Additional information
Salesforce versions API 30 to
API 34
Searchable content
types
Service Cloud standard/custom objects and fields, Chatter feed items and
files, multilingual Knowledge base articles and attachments, and CRM
content (binary files such as PDF).
4www.coveo.com 1
6. Coveo Platform 7.0 | Salesforce Connector Guide
Features Supported Additional information
Content
update
Incremental
refresh
Full refresh or rebuild needed to retrieve:
l Attached and detached KB articles from cases
l Deleted KB articles.
l Not replicable deleted objects such as deleted ContentVersion (CRM
Content and Chatter files) attachments and other items.
l Changes that occurred more than 30 days ago since the last refresh (a
scheduled refresh triggers a rescan).
l Permission changes for a profile, permission set, object sharing, or
object security level.
Full refresh
Rebuild
Document-level
security
Does not support the following security aspects: Apex managed sharing, IP
based permissions, field level security, shared personal groups (not
reported by the Salesforce API), frozen users, and KB articles item
permissions (see Unsupported Security Aspects).
1.3 Features
Indexed Salesforce Content
The connector can index the following Salesforce content:
l Service Cloud standard/custom objects and fields
l Multilingual Knowledge base articles
l Chatter feed items and files [more]
l CRM Content (binary files such as PDF)
l Sharing permissions
l Sandbox and production environments
l Inactive users
l User visibility
Note: The Salesforce connector does not support to rebuild only one KB or Chatter document or one whole
object as it appears to be possible from the index browser.
Indexed Salesforce Security
The connector can index the permissions of each Salesforce item allowing the index to only return Salesforce
search results that the user performing the query has the permissions to see.
The Coveo index replicates the Salesforce security model for:
4www.coveo.com 2
7. Coveo Platform 7.0 | Salesforce Connector Guide
l View All permissions
The Salesforce connector fully supports all View All permissions given through a user profile, more
explicitly View All Data which applies to every object, View All User which allows a view all on the user
object, and View All on specific objects such Accounts, Cases, Leads, and Contact.
Note: As Salesforce does not support View All Data on ContentVersion, the permission is replicated in
the connector.
l Sharing permissions
An administrator can secure private objects with the owner, collaboration group, group, user, bosses of a
given user, subordinates of a given user, or Community (also called Network) sharing permission types.
Note: CES 7.0.8225+ (March 2016) Portal Super User permissions are supported by the connector.
l Profile associated to the user
The profile specifies standard and custom object permissions for users associated to this profile.
Note: Any user which is granted Read access for an object by his profile is entitled to search for records of
the given type.
l Organization-wide defaults sharing settings
These settings specify the level of access your users have to each other's data.
Note: CES 7.0.8388+ (June 2016) The external sharing model (organization-wide defaults) is supported
by the connector.
l Shared content
A user can share private content with specific users or groups.
Note: File sharing settings applied to Chatter files and CRM Content documents are also supported. File
sharing settings are not the same as the sharing settings for private objects.
l CRM Content
CRM Content users have access to CRM Content Documents when they are entitled to read such
documents in the library to which the documents belong.
l Chatter
Chatter posts and comments inherit the permissions of the record onto which they are posted, no matter if
that record is public, private, a group or a user.
Note: Public and private CollaborationGroups are supported.
l Communities
Sharing sets are supported in Communities.
4www.coveo.com 3
8. Coveo Platform 7.0 | Salesforce Connector Guide
l Role hierarchy within the organization
With a role hierarchy, private documents are visible by the owner, but also by all parents of the owner in the
hierarchy.
l Permission sets
Permission sets given to individual users can extend (not restrict) their permissions beyond what is
specified in their profile.
l License type
A user license entitles a user to different functionality within Salesforce and determines which profiles and
permission sets are available to the user, so the Coveo index indirectly replicates user license type
permissions by indexing permissions from profiles and permission sets.
4www.coveo.com 4
9. Coveo Platform 7.0 | Salesforce Connector Guide
Note: The connector does not support the following security aspects:
l Apex managed sharing
l IP based permissions
The Coveo connector cannot index restrictions on login IP addresses or hours configured in Salesforce.
The consequence is that your Salesforce users can access Coveo search interfaces and review
Salesforce content from any IP address at any time.
l Field level security (FLS)
For Enterprise, Unlimited, and Developer Salesforce editions, visibility of individual fields can be granted
or denied to users or groups to fine-tune the access control in a permission set or a profile. The Coveo
connector cannot index these permissions. The consequence is that a user that is denied access to a field
could see the content of this field in Coveo search results. Note however that this is also the case for
Salesforce search results (see the Salesforce document Field-Level Security Overview).
l Permission changes replicated with re-indexing, not with incremental refreshes
When permissions change in Salesforce for a profile, permission set, object sharing, or object security
level (Public versus Private), the changes are not replicated in the index on the next incremental refresh.
You must refresh the source to capture permission changes.
l Shared personal groups
A user can share content with a personal group. These sharing permissions cannot be indexed because
they are currently not reported by the Salesforce API. The consequence is that members of the personal
group will not see the shared content in Coveo Organization results. This limitation is therefore not a
security hole.
l Frozen users are not supported
The user that are frozen using the Freeze button are not denied access to the search (see Freezing User
Accounts).
l Knowledge Base (KB) item permissions:
In Salesforce, you can map User Roles to KB data categories (e.g.: members of the Technical Agent
role can only see KB articles under the Technical data category). This mapping information is not
available from the Salesforce API and therefore cannot be indexed. Similarly, the permissions given
through permission sets to grant only some users access to only one Article Type cannot be retrieved
through the Salesforce API.
Consequently, in search results, all users can see all KB articles under all data categories.
l When the organization-wide default is set to Controlled by Parent, a maximum master-detail relationship
depth of two levels is supported (see Sharing Default Access Settings).
Example: When you index a subdetail object, the detail parents are correctly determined but the master
parents are considered public because there are three levels (master-detail-subdetail).
4www.coveo.com 5
10. Coveo Platform 7.0 | Salesforce Connector Guide
Incremental Refresh
The incremental refresh feature refreshes the content of the index based on the modification date of the objects
in the Salesforce environment. If an item is modified, the incremental refresh feature refreshes the item
automatically.
Notes:
l The incremental refresh feature limitations:
o Does not work when the last incremental refresh was performed more than 30 days ago. This will
trigger a full refresh of the content.
o Not supported for all not replicateable deleted objects such as deleted ContentVersion (CRM Content
and Chatter files) attachments and other items.
o CES 7.0.7914– (October 2015) A source full refresh or rebuild is needed to capture the deletion of
knowledge base articles and the attachment (or the contrary) of articles on a case.
l CES 7.0.8047+ (December 2015) After you upgrade CES, it is recommended to perform a full refresh of
your source(s) containing KB articles to take account of possible URI changes. You will also possibly
have to change the ObjectsToGet configuration file depending on your needs (see Salesforce Connector
Configuration Recipes). Theses modifications allow the connector to fully support the incremental refresh
as well as the publish status changes of KB articles using stable URIs now produced by default.
l CES 7.0.7914– (October 2015) Stable URIs can only be produced with the help of Coveo Support for the
latest version of online articles when draft and archived articles are not indexed.
Customizable ObjectsToGet Configuration File
You can customize items that the Coveo crawler retrieves from Salesforce (see "Creating a Salesforce
ObjectsToGet Configuration File" on page 35).
Customizable Mapping File
You can customize how the fields of Salesforce objects are mapped to searchable fields in the Coveo index
(see "Creating a Salesforce Mapping File" on page 69).
Feature History
Coveo Platform
version
Date Features
7.0.8047 December
2015
Full support of incremental refreshes on knowledge articles and indexing
their publish status
7.0.7183 November
2014
Support validating the ObjectsToGet with an XSD [more]
4www.coveo.com 6
11. Coveo Platform 7.0 | Salesforce Connector Guide
Coveo Platform
version
Date Features
7.0.6767 June 2014 l Support incremental modification of knowledge base articles versions
and states [more]
l Support incremental modification of user profiles
7.0.6424 February
2014
Knowledge content searchable by article number without inputting leading
zeroes
7.0.6339 January
2014
l Partial incremental refresh support on knowledge articles
l Support multilingual knowledge articles
7.0.6196 November
2013
Adding support to crawl Chatter feed items and files.
7.0.5785 August 2013 Introduction of this second generation Salesforce connector
What's Next?
Review the deployment process for the Salesforce connector (see "Salesforce Connector Deployment Overview"
on page 8).
4www.coveo.com 7
12. Coveo Platform 7.0 | Salesforce Connector Guide
2. Salesforce Connector Deployment Overview
The following procedure outlines the steps needed to index a Salesforce source. The steps indicate the order in
which you must perform configurations tasks. When needed, the steps refer to a detailed procedure.
The Salesforce connector can index various Salesforce content types:
l Service Cloud standard and custom objects and fields
l Knowledge base articles
l Chatter
l CRM Content
When you want to index more than one of these Salesforce content types, you must use the following procedure to
create a configuration (ObjectsToGet configuration file, mapping file, and source) for each of them because they
cannot share the same set of configuration parameters.
To deploy the Salesforce connector
1. Validate that your environment meets the requirements (see "Salesforce Connector Requirements" on page
10).
2. Configure the user identity
The Coveo connector needs an account to connect to your Salesforce organization and access the entire
content that you want to index. You must create a CES user identity to hold the credentials of this Salesforce
account (see "Creating a Salesforce User Identity" on page 11).
3. Get Salesforce Client_ID and Client_Secret values
The Coveo security provider and connector for Salesforce must know the Client_ID and Client_Secret
values for your Salesforce organization to be authorized to access its content (see "Getting Salesforce Client_
ID and Client_Secret Values" on page 16).
4. Create an ObjectsToGet configuration file
An ObjectsToGet XML configuration file tells the crawler which Salesforce items to retrieve (see "Salesforce
ObjectsToGet Configuration File" on page 21).
You must create your custom ObjectsToGet XML configuration file before configuring your source. You can
create the file based on examples that include standard objects and include your custom objects (see
"Creating a Salesforce ObjectsToGet Configuration File" on page 35).
5. Configure a mapping file
A Salesforce source needs a mapping file to know how to map retrieved Salesforce items to CES index fields.
You must create a mapping file before you configure your Salesforce source (see "Creating a Salesforce
Mapping File" on page 69).
6. Create a custom Salesforce field set CES 7.0.6607+ (April 2014)
4www.coveo.com 8
13. Coveo Platform 7.0 | Salesforce Connector Guide
a. The Salesforce source needs a field set matching the CES fields that are included in the mapping file. It is
recommended to start by importing the default Salesforce field set file ([CES_
Path]BinCoveo.CES.CustomCrawlers.Salesforce.FieldSet.xml) to create fields for all the
metadata available by default from Salesforce content.
b. When you created custom Salesforce object and fields, add corresponding fields to the field set.
7. Configure an Email security provider
Note: For a Salesforce Knowledge Base source, you do not need to perform this procedure. Knowledge Base
permissions cannot be indexed so no Email security provider is needed.
In Salesforce, users are identified by their email addresses. Consequently, permissions returned by the
Salesforce security provider for each document are email addresses. The Salesforce security provider then
requires another security provider to uniquely identify users from their email addresses.
The security provider type to use depends on how users are authenticated when they access the search
interface:
l When authenticated with their email address, use an Email security provider (see "Configuring an Email
Security Provider" on page 100).
l When authenticated with their Active Directory account, use an Active Directory security provider (see
"Configuring an Active Directory Security Provider" on page 102).
Note: An Active Directory security provider is appropriate only when the User Principal Name (UPN)
matches the email address for all users.
Note: You may require to also use a Regex Transform Member Name security provider in between the two
other security providers to map member types. Contact Coveo Support for assistance.
8. Configure a Salesforce security provider
Note: For a Salesforce Knowledge Base source, you do not need to perform this procedure. Knowledge Base
permissions cannot be indexed so no Email security provider is needed.
A Salesforce source needs a Salesforce security provider (see "Configuring a Salesforce Security Provider" on
page 98).
9. Configure and index the Salesforce source
The Coveo connector needs to know details about your Salesforce organization to be able to index the desired
content (see "Configuring and Indexing a Salesforce Source" on page 105).
10. If you encounter issues:
l Solve typical issues that return error messages (see "Troubleshooting Salesforce Connector Issues" on
page 117).
l Consider adding and modifying default values of hidden source parameters (see "Modifying Hidden
Salesforce Source Parameters" on page 111).
4www.coveo.com 9
14. Coveo Platform 7.0 | Salesforce Connector Guide
3. Salesforce Connector Requirements
Your environment must meet the following requirements to be able to use the Coveo connector for Salesforce
repositories:
l CES 7.0.5785+ (August 2013)
l Coveo for Salesforce license
The Salesforce connector is only available on-premises if you have acquired a suitable Coveo for Salesforce
license (see Coveo for Salesforce).
Note: You can see if the Salesforce connector is enabled in your CES 7.0 instance from the
CES Administration Tool.
l An active Salesforce account to a Salesforce organization
The crawling account must have permissions to read all the types of content that you want to index (see
"Creating a Salesforce User Identity" on page 11).
What's Next?
Create a user identity to be used by the Coveo connector to crawl your Salesforce content (see "Creating a
Salesforce User Identity" on page 11).
4www.coveo.com 10
15. Coveo Platform 7.0 | Salesforce Connector Guide
4. Creating a Salesforce User Identity
The Coveo connector and security provider for Salesforce must use a user account to connect to your Salesforce
organization.
When an application such as the Coveo connector accesses your Salesforce content through the API, it must
provide credentials where the Security Token associated to the account is appended to the password.
Important: Salesforce may regularly request a password change which will generate a new Security Token at the
same time. You must then each time update the user identity with the new password and Security Token.
To create a Salesforce user identity
1. In the Salesforce organization that you want to index:
a. Select or create an account to be used by the Coveo connector and security provider to access your
Salesforce content (see "Creating a Dedicated Salesforce Crawling Account" on page 12).
b. Find the Salesforce Security Token for this account (see "Getting the Security Token for Your Salesforce
Account" on page 14).
2. On the Coveo server, access the Administration Tool.
3. In the Administration Tool, select Configuration > Security.
4. In the navigation panel on the left, select User Identities.
5. In the User Identities page, click Add.
6. In the Modify User Identity page:
a. In the Name box, enter a name for this user identity.
Example: Salesforce Crawling Account
4www.coveo.com 11
16. Coveo Platform 7.0 | Salesforce Connector Guide
b. In the User box, enter the user name of the selected Salesforce account, typically the email address.
c. In the Password box, enter the password to which you append the Security Token for the selected
Salesforce account with no space in between.
Example: When the password is ThisIsMyPassword and the Security Token is
DU5PJU3GtHbQaX0zxiWoCMq8Z, then enter ThisIsMyPasswordDU5PJU3GtHbQaX0zxiWoCMq8Z.
d. Click Apply Changes.
What's Next?
Your Salesforce source and security provider will need to know the Client_ID and Client_Secret values for
your Salesforce organization (see "Getting Salesforce Client_ID and Client_Secret Values" on page 16).
4.1 Creating a Dedicated Salesforce Crawling Account
The Coveo connector can use a Salesforce administrator account to access and crawl your Salesforce content. It is
however a better practice to create dedicated Salesforce user, profile, and permission set for the Coveo crawling,
that specify minimal permissions and access.
Note: It is strongly recommended to have separate dedicated Salesforce crawling accounts for each Salesforce
source and security provider. When the Coveo crawler accesses Salesforce with the same user credentials too
many times, Salesforce returns INVALID_QUERY_LOCATOR error messages, such as the following:
Error with ID 'SALESFORCE_INVALID_QUERY': invalid query locator (INVALID_QUERY_LOCATOR)
- This error can occur if a user is used more than once for sources that run in
parallel. To avoid this error, make sure to use only one user per source or alternate
the refresh schedule of your sources.
To create a dedicated Salesforce crawling account
1. Using an administrator account, log in to your Salesforce organization.
2. In the user menu, select Setup.
3. Create a Salesforce profile dedicated to the Coveo crawler:
a. In the Setup page, select Manage Users > Profiles.
b. In the Profiles page, click New Profile.
c. In the Clone Profile page:
4www.coveo.com 12
17. Coveo Platform 7.0 | Salesforce Connector Guide
i. In the Existing Profile box, select an existing profile such as Read Only to be used as a template for
the new profile according to the permissions you want to grant to the crawler.
ii. In the Profile Name box, enter a name such as CoveoIndexer.
iii. Click Save.
d. In the page for your new profile, click Edit and in the Administrative Permissions section:
i. Ensure that the API Enabled option is selected.
ii. Optionally, select the API Only User option as an additional security measure.
iii. Select the Modify All Data option when any of the following situation applies:
l You are using CES 7.0.6225– (December 2013) or prior.
l You want to index the Salesforce item permissions.
Note:
l The Modify All Data permission is required because the Salesforce permissions can be
indexed only through the Salesforce Metadata API that is only accessible with the Modify All
Data permission.
l If you do not enable Modify All Data, be aware that the crawler will only index content to which it
has access, so set up read access to objects accordingly.
iv. When indexing Knowledge content, ensure that Knowledge User is checked.
v. Optionally, as an additional security measure, in the Login IP Ranges section, select or create a login
IP range to restrict the accessibility for this profile (see Coveo Platform IP address range).
4. Create a Salesforce user dedicated to the Coveo crawler:
4www.coveo.com 13
18. Coveo Platform 7.0 | Salesforce Connector Guide
a. In the Setup page, select Manage Users > Users.
b. In the All Users page, click New User.
c. In the New User page:
i. Fill the required fields.
ii. In the Profile box, select the profile you just created.
iii. Click Save.
4.2 Getting the Security Token for Your Salesforce Account
When you create a Salesforce account, Salesforce sends an email message from support@salesforce.com with
subject: salesforce.com security token confirmation to the email address associated with the account.
This email message contains the Security Token for the account and is the only place where you can find the
Security Token value. When you change the account password, the security token is also regenerated (so the
previous one expires) and a similar email is sent.
To get the security token for your Salesforce account
1. In the mailbox for the email address associated with the Salesforce account to be used by the Coveo
connector, look for the latest email message received from support@salesforce.com with
subject: salesforce.com security token confirmation.
2. If you cannot find the latest email with security token, reset the security token:
a. Log in to Salesforce using the Salesforce account to be used by the Coveo connector.
b. In the User Menu, select Setup.
c. In the menu on the left, under Personal Setup, expand My Personal Information, and then click Reset My
Security Token.
d. Follow onscreen instructions.
A new email message will be sent.
3. Open the message, and then copy the Security Token value.
4www.coveo.com 14
19. Coveo Platform 7.0 | Salesforce Connector Guide
Example: In the following email example, the Security Token value is highlighted.
4www.coveo.com 15
20. Coveo Platform 7.0 | Salesforce Connector Guide
5. Getting Salesforce Client_ID and Client_Secret Values
The Force.com platform implements the OAuth 2.0 Authorization Framework, so users can authorize applications to
access Force.com resources.
When you configure the Coveo Salesforce security provider and Salesforce source, you must know the Client_ID
and Client_Secret token values for the Salesforce organization that you want to index.
To get the Salesforce Client_ID and Client_Secret values
1. Using and administrator account, log into the Salesforce organization that you want to index.
2. On the User Menu, select Setup.
3. In the navigation menu on the left, under App Setup, expand Create, and then click Apps.
4. In the Apps page, in the Connected Application section, click New to create a new application that will use
OAuth2 to gain access to the organization.
5. In the New Connected App page:
4www.coveo.com 16
21. Coveo Platform 7.0 | Salesforce Connector Guide
a. In the Basic Information section:
i. Enter meaningful names in the Connected App Name and API Name boxes.
ii. Enter your email in the Contact Email box so that you can receive messages from this application.
b. In the API (Enable OAuth Settings) section:
i. Select the Enable OAuth Settings check box.
ii. In the Callback URL box, since a callback URL will not be used for this application, enter a dummy but
valid secured URL (https://) such as
https://login.salesforce.com/services/oauth2/callback.
iii. In the Available OAuth Scopes list, select the following items:
4www.coveo.com 17
22. Coveo Platform 7.0 | Salesforce Connector Guide
l Access and manage your data (api)
l Full access (full)
l Perform requests on your behalf at any time (refresh_token, offline_access)
and click Add for each so that they appear in the Selected OAuth Scopes list.
c. Click Save.
6. In the page that appears for your new connected app, in the API (Enable OAuth Settings) section:
a. Copy the Consumer Key value and paste it in a secure reference document of your choice.
The Consumer Key is the client_id.
b. Next to Consumer secret, click Click to reveal, copy the value that appears, and then paste it in your
secure reference document.
The Consumer secret is the client_secret.
c. Save your reference document.
Note: You can always come back to this Salesforce page (Setup > App Setup > Create > Apps, and clicking
the application name in the Connected Apps list).
7. Create a Salesforce permission set dedicated to the Coveo crawler and assign it to your dedicated app and
user:
a. In the Setup page, select Manage Users > Permission Sets.
b. In the Permission Sets page, click New.
c. In the Create page, in the Label and API Name boxes, enter significant names, and then click Save.
4www.coveo.com 18
23. Coveo Platform 7.0 | Salesforce Connector Guide
d. In the page for the new permission set:
i. Click Manage Assignments, and then add the dedicated user you created earlier for the Coveo
crawler (see "Creating a Dedicated Salesforce Crawling Account" on page 12).
ii. In the Apps section, click Assigned Connected Apps.
iii. In the Assigned Connected Apps section, click Edit, add the connected app you just created to the
4www.coveo.com 19
24. Coveo Platform 7.0 | Salesforce Connector Guide
Enabled Connected Apps list, and then click Save.
What's Next?
Create an ObjectsToGet Configuration file (see "Salesforce ObjectsToGet Configuration File" on page 21).
4www.coveo.com 20
25. Coveo Platform 7.0 | Salesforce Connector Guide
6. Salesforce ObjectsToGet Configuration File
The ObjectsToGet configuration file of the Salesforce connector contains the definition of all standard or custom
objects that will be retrieved from the Salesforce organization. Each object definition is used to generate the
SOQL query executed by the connector to retrieve the records for that object.
With this configuration file, you get control over:
l Which information is retrieved by specifying the fields and relationships that should be fetched for each object.
This information will be available to use in the mapping file.
l Which records are returned by specifying conditions on the SOQL query that will be used to filter the query
results.
Notes:
l If you want to retrieve Salesforce Knowledge Base articles, you need to specify at least two queries for each
type of Knowledge article, one for the *__ka object and one the *__kav object (see "Salesforce
ObjectsToGet Configuration File Example for Knowledge Base" on page 48).
l There is a bug in the Salesforce API that causes the returned JSON to be invalid when querying a binary field
of an object, so ensure to not include any binary field in your query.
l CES 7.0.7914+ (October 2015) Support for the * character to replace a list of Objects and Parent relationship
fields that are queryable.
Example: When the mapping file contains the following:
<Query>
<ObjectName>Case</ObjectName>
<Fields>
<string>*</string>
</Fields>
</Query>
You can use the following SOQL query: <Query value="Select * from Case" />
l CES 7.0.8047+ (December 2015) Support for the * character to replace a list of Child relationship fields that
are queryable.
Example: <Query value="Select *,Parent.*, (Select * from Children) From Object/>
6.1 Salesforce Object Definition
To obtain the list of queryable fields on a specific object:
l Salesforce developers can use the describeSObject() method to obtain the complete object definition in
JSON format.
Example: https://na15.salesforce.com/services/data/v27.0/sobjects/Account/describe
4www.coveo.com 21
26. Coveo Platform 7.0 | Salesforce Connector Guide
l Salesforce administrators can obtain the complete list of fields from Salesforce API online documentation (see
Account, Task).
To obtain the list of available relationships on a specific object:
l Salesforce administrators can access any object definition from Salesforce in the Setup under the Customize
menu. Object relationships are identified by fields of data type Lookup (see AccountFields, TaskFields).
6.2 Configuration File Elements
The ObjectsToGet Salesforce configuration file is an aggregate of query XML nodes. A query node contains several
elements, each one being used to generate the SOQL query of a Salesforce object.
Value attribute (optional)CES 7.0.7814+ (August 2015)
You can specify an SOQL query in the query value as shown in the following example (see Salesforce Object
Query Language (SOQL)):
<Query value="Select Id, Owner.Id, (Select Id From Shares) From Case Where CaseNumber>10" />
Keep in mind that only what is already in the objects to get is supported.
ObjectName (required)
The name of the object (standard or custom) to query (see Standard Objects).
Note: If you are using the value attribute, the object name is optional and must be the same.
GroupBy (optional)
The name of the field on which results should be grouped by.
Limit (optional)
The maximum number of items that will be retrieved by the query.
Offset (optional)
The number of items that should be skipped in query results.
Fields (required)
Contains the name of the fields (Field Name column in Salesforce) that will be available on each record
returned by the query. Each field name must be in a <string> element, no matter its data type. Fields specified
in this section can be of any data type except Lookup.
4www.coveo.com 22
27. Coveo Platform 7.0 | Salesforce Connector Guide
Example:
<Query>
<ObjectName>Account</ObjectName>
<Fields>
<string>Id</string>
<string>IsDeleted</string>
<string>Name</string>
<string>Type</string>
<string>BillingStreet</string>
<string>BillingCity</string>
<string>BillingState</string>
<string>BillingPostalCode</string>
<string>BillingCountry</string>
<string>Phone</string>
<string>Fax</string>
<string>AccountNumber</string>
<string>Website</string>
<string>Sic</string>
<string>Industry</string>
<string>AnnualRevenue</string>
<string>NumberOfEmployees</string>
<string>Ownership</string>
<string>TickerSymbol</string>
<string>Description</string>
<string>Rating</string>
<string>Site</string>
<string>CreatedDate</string>
<string>LastModifiedDate</string>
<string>SystemModstamp</string>
</Fields>
</Query>
QueryCondition (optional)
Important: CES 7.0.6942– (August 2014) This operator is not validated and has a free form. However, the
resulting SOQL must be in the format FIELD OPERATOR VALUE. Rather use QueryCondition2.
One or more conditions that will be applied to the SOQL query used to retrieve object records.
l Field (required):
Case-insensitive name of the object field on which the condition is applied. Relationship names can also
be used (ex.: Parent.Type).
l Operator (required):
The operator to apply to the condition. Any operator supported by Salesforce SOQL queries can be used
(see Comparison Operators).
l Value (required):
Case-sensitive value used to evaluate the condition. String values must be enclosed in single quotes.
4www.coveo.com 23
28. Coveo Platform 7.0 | Salesforce Connector Guide
Example:
<Query>
<ObjectName>Account</ObjectName>
<Fields>
<string>Name</string>
<string>AccountNumber</string>
</Fields>
<Conditions>
<QueryCondition>
<Field>Type</Field>
<Operator>!=</Operator>
<Value>'Prospect'</Value>
</QueryCondition>
<QueryCondition>
<Field>Owner.Name</Field>
<Operator>=</Operator>
<Value>'John Smith'</Value>
</QueryCondition>
</Conditions>
</Query>
The generated query is:
SELECT Name FROM Account WHERE Type != 'Prospect' AND Owner.Name = 'John Smith'
QueryCondition2 (optional)
Note: This query condition is validated and has more options. This is the prefered way to create a query
condition.
One or more conditions that will be applied to the SOQL query used to retrieve object records.
l Field (required): Case-insensitive name of the Object Field on which the condition is applied. Relationship
names can also be used (e.g. Parent.Type).
l Relation (required): The operator to apply to the condition. Supported operators are Equal, NotEqual,
Less, LessOrEqual, Greater, GreaterOrEqual, Like, NotLike.
l SoqlString|SoqlBoolean|SoqlDateTime (required): Case-sensitive value (not Like) used to evaluate
the condition.
4www.coveo.com 24
29. Coveo Platform 7.0 | Salesforce Connector Guide
Example:
<Query>
<ObjectName>Account</ObjectName>
<Fields>
<string>Name</string>
</Fields>
<Conditions>
<QueryCondition2>
<Field>Type</Field>
<Relation>NotEqual</Relation>
<SoqlString>Prospect</SoqlString>
</QueryCondition2>
<QueryCondition2>
<Field>IsEscalated</Field>
<Relation>Equal</Relation>
<SoqlBoolean>true</SoqlBoolean>
</QueryCondition2>
<QueryCondition2>
<Field>LastViewDate</Field>
<Relation>GreaterOrEqual</Relation>
<SoqlDateTime>2014-04-28T00:00:00.0000000-00:00</SoqlDateTime>
</QueryCondition2>
</Conditions>
</Query>
Note: For SoqlDateTime, the date/time format must exactly match YYYY-MM-DDTHH:MM:SS.0000000-
00:00
The generated query is:
SELECT Name FROM Account WHERE Type != 'Prospect' AND IsEscalated = true AND LastViewDate >= 2014-
04-28T00:00:00
InCondition (optional)
l Field (required): Case-insensitive name of the Object Field on which the condition is applied. Relationship
names can also be used (e.g. Parent.Type).
l AllowedValues (required): Case-sensitive possible values of the field.
Example:
<Query>
<ObjectName>Account</ObjectName>
<Fields>
<string>Name</string>
</Fields>
<Conditions>
<InCondition>
<Field>Type</Field>
<AllowedValues>
<SoqlString>Prospect</SoqlString>
<SoqlString>Client</SoqlString>
</AllowedValues>
</InCondition>
</Conditions>
</Query>
The generated query is:
SELECT Name FROM Account WHERE Type IN ('Prospect', 'Client')
4www.coveo.com 25
30. Coveo Platform 7.0 | Salesforce Connector Guide
InQueryCondition (optional)
CES 7.0.7183+ (November 2014) Semi-joins are supported in query's conditions (see Comparison Operators).
Semi-joins are useful when you want to index only a subset of records based on another set of records.
l Field (required):
Case-insensitive name of the object field on which the condition is applied. Relationship names can also
be used (ex.: Parent.Type).
l Query (required): A valid query object (with ObjectName, Fields, etc) (see Semi-Joins or Anti-Joins
Relationship Query Limits).
Example:
<Query>
<ObjectName>Case</ObjectName>
<Fields>
<string>Id</string>
</Fields>
<Conditions>
<InCondition>
<Field>Id</Field>
<Query>
<ObjectName>CaseComment</ObjectName>
<Fields>
<string>ParentId</string>
</Fields>
<Conditions>
<QueryCondition>
<Field>CommentBody</Field>
<Operator>=</Operator>
<Value>'this is a test'</Value>
</QueryCondition>
</Conditions>
</Query>
</InCondition>
</Conditions>
</Query>
The generated query is:
SELECT Id FROM Case WHERE Id IN (SELECT ParentId FROM CaseComment WHERE CommentBody = 'this is a
test')
Not InQueryCondition (optional)
CES 7.0.7183+ (November 2014) Anti-joins are supported in query's conditions (see Comparison Operators). Anti-
joints are useful when you want to index only a subset of records based on another set of records.
l Field (required):
Case-insensitive name of the object field on which the condition is applied. Relationship names can also
be used (ex.: Parent.Type).
l Query (required): A valid query object (with ObjectName, Fields, etc) (see Semi-Joins or Anti-Joins Query
Limits).
4www.coveo.com 26
31. Coveo Platform 7.0 | Salesforce Connector Guide
Example:
<Query>
<ObjectName>Case</ObjectName>
<Fields>
<string>Id</string>
</Fields>
<Conditions>
<NotCondition>
<InCondition>
<Field>Id</Field>
<Query>
<ObjectName>CaseComment</ObjectName>
<Fields>
<string>ParentId</string>
</Fields>
<Conditions>
<QueryCondition>
<Field>CommentBody</Field>
<Operator>=</Operator>
<Value>'this is a test'</Value>
</QueryCondition>
</Conditions>
</Query>
</InCondition>
</NotCondition>
</Conditions>
</Query>
The generated query is:
SELECT Id FROM Case WHERE NOT Id IN (SELECT ParentId FROM CaseComment WHERE CommentBody = 'this is
a test')
ParentRelationship (optional)
One or more relationships which information will be available on each object record returned by the query. An
object relationship is defined by a lookup field which creates a relation between the current object being
queried and another object. These relations allow SOQL query operations similar to SQL joins.
l RelationshipName (required):
The field name of data type Lookup.
l Fields (required):
The name of the fields of the related object that will be available on each record returned by the query.
l ParentRelationships (optional):
Another level of parent relationship, but this time, the relationship applies to the related object.
4www.coveo.com 27
32. Coveo Platform 7.0 | Salesforce Connector Guide
Example:
<Query>
<ObjectName>Account</ObjectName>
<Fields>
<string>Name</string>
<string>AccountNumber</string>
</Fields>
<ParentRelationships>
<ParentRelationship>
<RelationshipName>Owner</RelationshipName>
<Fields>
<string>Name</string>
<string>Email</string>
</Fields>
</ParentRelationship>
</ParentRelationships>
</Query>
Important: The parent field is copied to the record. If the parent is modified, the indexed record is not updated.
ChildRelationship (optional)
One or more relationships which information will be available on each Object record returned by the query. An
Object relationship is defined by a Lookup Field which creates a relation between the current Object being
queried and another Object. These relations allow SOQL query operations similar to SQL joins.
l Query (required): A valid query object (with ObjectName, Fields, etc).
Example:
<Query>
<ObjectName>Opportunity</ObjectName>
<Fields>
<string>Id</string>
<string>Name</string>
</Fields>
<ChildRelationships>
<Query>
<ObjectName>Attachments</ObjectName>
<Fields>
<string>Id</string>
<string>Name</string>
</Fields>
</Query>
</ChildRelationships>
</Query>
The generated query is:
SELECT Id, Name, (SELECT Id, Name FROM Attachments) FROM Opportunity
The generated metadata, when an attachment is found on the opportunity:
"Attachments.attribute.type" => "Attachment"
"Attachments.attribute.url" => "/services/data/v29.0/sobjects/Attachment/00PG000000B8RUvMAN"
"Attachments.Id" => "00PG000000B8RUvMAN"
"Attachments.Name" => "a_stash_of_werthers.jpg"
4www.coveo.com 28
33. Coveo Platform 7.0 | Salesforce Connector Guide
Note:
l When more than one child exist, the fields contain values separated with a semicolon.
Example: Attachments.Name: a.jpg;b.jpg
l Nested child relationships (sub-sub queries) are not supported.
Important: CES 7.0.8850– (March 2017) The child field is copied to the record. If a child is modified, the
indexed record is not updated.
CreateRecord (optional)
CES 7.0.8996+ (June 2017) To be used only inside a ChildRelationship. It creates an item from child records.
In the following example, Attachments from Opportunities are created as items in the Coveo index.
Example:
<Query>
<ObjectName>Opportunity</ObjectName>
<Fields>
<string>Id</string>
<string>Name</string>
</Fields>
<ChildRelationships>
<ChildRelationship>
<RelationshipName>Attachments</RelationshipName>
<Fields>
<string>Id</string>
<string>Name</string>
</Fields>
<CreateRecord>true</CreateRecord>
</ChildRelationship>
</ChildRelationships>
</Query>
PolymorphicRelationship (optional)
Polymorphic relationships can be useful for parent relationships on a Lookup field that can be related to
multiple types of objects (ex.: Lookup
(Contract,Campaign,Account,Opportunity,Product,Asset,Case,Solution)). The polymorphic
relationship allows for different fields to be retrieved depending on the object that will be related for a specific
record.
4www.coveo.com 29
34. Coveo Platform 7.0 | Salesforce Connector Guide
Notes:
l CES 7.0.8047+ (December 2015) Polymorphic relationships no longer depend on a parent relationship to
work.
Example: You can add the following on feed items (TextPost, LinkPost, ContentPost, PollPost) to
create the CreatedBy.SmallPhotoUrl metadata when indexing FeedItem, FeedComment and
collaborationgroup:
<PolymorphicRelationship>
<RelationshipName>CreatedBy</RelationshipName>
<ObjectName>User</ObjectName>
<Fields>
<string>Name</string>
<string>Type</string>
<string>PhotoURL</string>
</Fields>
</PolymorphicRelationship>
l The two following metadata appear on the record with polymorphic relationships: <polymorphic_
relationship_name>.<field> and <polymorphic_relationship_name>_<object_
name>.<field>.
l CES 7.0.7104– (October 2014) The record with polymorphic relationships only provided the metadata
named <polymorphic_relationship_name>_<object_name>.<field>.
l RelationshipName (required):
The field name of data type Lookup.
l ObjectName (optional):
The related object type this polymorphic relationship applies to.
Note: CES 7.0.7104– (October 2014) The ObjectName field is required.
l Fields (required):
The name of the fields of the related object that will be available on each record returned by the query.
l ParentRelationships (optional):
Another level of parent relationship, but this time, the relationship applies to the related object.
4www.coveo.com 30
35. Coveo Platform 7.0 | Salesforce Connector Guide
Example:
<Query>
<ObjectName>Task</ObjectName>
<Fields>
<string>Id</string>
<string>Subject</string>
<string>ActivityDate</string>
</Fields>
<ParentRelationships>
<ParentRelationship>
<RelationshipName>What</RelationshipName>
<Fields>
<string>Name</string>
<string>Type</string>
</Fields>
</ParentRelationship>
</ParentRelationships>
<PolymorphicRelationships>
<PolymorphicRelationship>
<RelationshipName>What</RelationshipName>
<ObjectName>Account</ObjectName>
<Fields>
<string>Name</string>
<string>AccountNumber</string>
</Fields>
</PolymorphicRelationship>
<PolymorphicRelationship>
<RelationshipName>What</RelationshipName>
<ObjectName>Opportunity</ObjectName>
<Fields>
<string>Amount</string>
<string>TotalOpportunityQuantity</string>
</Fields>
</PolymorphicRelationship>
</PolymorphicRelationships>
</Query>
Important: The parent field is copied to the record. If a parent is modified, the indexed record is not updated.
Order (optional) CES 7.0.6607+ (April 2014)
One or more order restrictions that will be applied to the SOQL query used to retrieve Object records.
l Ascending (optional): The direction of the ordering. Default is true (ascending). Use false for
descending.
l NullsFirst (optional): Whether records with NULL values in the specified fields must be returned first or
last. Default is true.
l Fields (required): One or more fields to base the ordering on, in the specified field order.
4www.coveo.com 31
36. Coveo Platform 7.0 | Salesforce Connector Guide
Examples:
With the following configuration:
l Opportunity.Id shows that we can specify the query object name as the parent of the field.
l Account.Foo.Id is a field on the parent Foo, which is also a field of the parent Account of
Opportunity.
l What.Id is a field on the polymorphic parent What of Opportunity.
<Query>
<ObjectName>Opportunity</ObjectName>
<Fields>
<string>Id</string>
</Fields>
<Order>
<Ascending>true</Ascending>
<NullsFirst>false</NullsFirst>
<Fields>
<string>Name</string>
<string>Opportunity.Id</string>
<string>Account.Foo.Id</string>
<string>What.Id</string>
</Fields>
</Order>
</Query>
The generated query is:
SELECT Id FROM Opportunity ORDER BY Name, Opportunity.Id, Account.Foo.Id, What.Id ASC NULLS LAST
Configuration including a child relationship:
<Query>
<ObjectName>Opportunity</ObjectName>
<Fields>
<string>Id</string>
</Fields>
<ChildRelationships>
<Query>
<ObjectName>Attachments</ObjectName>
<Fields>
<string>Id</string>
</Fields>
<Order>
<Fields>
<string>Name</string>
</Fields>
</Order>
</Query>
</ChildRelationships>
</Query>
The generated query is:
SELECT Id, (SELECT Id FROM Attachments ORDER BY Name ASC NULLS FIRST) FROM Opportunity
4www.coveo.com 32
37. Coveo Platform 7.0 | Salesforce Connector Guide
6.3 XML Schema Definition
Note: CES 7.0.7183+ (November 2014) Each of the ObjectsToGet in your Salesforce sources are validated
against the XSD.
If it is not the case, a SALESFORCE_INVALID_CONFIGURATION error message appears in the CES console and
logs.
Use the following XML schema definition to validate your configuration file.
<?xml version="1.0" encoding="utf-8"?>
<xs:schema id="ArrayOfQuery" xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xs:element name="Fields">
<xs:complexType>
<xs:sequence>
<xs:element name="string" nillable="true" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:simpleContent msdata:ColumnName="string_Text" msdata:Ordinal="0">
<xs:extension base="xs:string">
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ParentRelationships">
<xs:complexType>
<xs:sequence>
<xs:element name="ParentRelationship" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="RelationshipName" type="xs:string" minOccurs="0" maxOccurs="1" />
<xs:element ref="Fields" minOccurs="0" maxOccurs="unbounded" />
<xs:element name="ParentRelationships" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="ParentRelationship" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="RelationshipName" type="xs:string" minOccurs="0"
maxOccurs="1" />
<xs:element ref="Fields" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Query" type="QueryType" />
<xs:complexType name="QueryType">
<xs:sequence>
<xs:element name="ObjectName" type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="GroupBy" type="xs:string" minOccurs="0" />
<xs:element name="Limit" type="xs:string" minOccurs="0" />
<xs:element name="Offset" type="xs:string" minOccurs="0" />
<xs:element name="FoundRecordsAreDeleted" type="xs:string" minOccurs="0" />
<xs:element ref="Fields" minOccurs="0" maxOccurs="unbounded" />
4www.coveo.com 33
39. Coveo Platform 7.0 | Salesforce Connector Guide
6.4 Creating a Salesforce ObjectsToGet Configuration File
You must create an ObjectsToGet configuration file and attach it to your Salesforce source to instruct the connector
which objects to retrieve from your Salesforce organization (see "Salesforce ObjectsToGet Configuration File" on
page 21).
Note: You must be familiar with standard and custom objects and fields used in your Salesforce organization to
be able to create a custom ObjectsToGet configuration file.
The content of the ObjectsToGet configuration file typically includes standard objects but most likely also the custom
objects that you want to index. You can create your ObjectsToGet configuration file by starting with provided
examples and customize it to suit your needs.
It is recommended to create separate ObjectsToGet configuration files with separate sources for the following types
of Salesforce content:
l Service Cloud standard and custom objects and fields
l Knowledge base articles
l CRM Content
To create a Salesforce ObjectsToGet configuration file
1. Refer to the most appropriate of the following topics to copy the content of the corresponding ObjectsToGet
XML configuration file example:
l Salesforce ObjectsToGet Configuration File Example for Standard Objects
l "Salesforce ObjectsToGet Configuration File Example for Knowledge Base" on page 48
l "Salesforce ObjectsToGet Configuration File Example for CRM Content " on page 51
2. Using a text editor:
a. Paste the content of the ObjectsToGet configuration file example.
b. Modify or remove standard objects and fields, or add custom objects and fields to match the needs of your
Salesforce organization (see "Salesforce ObjectsToGet Configuration File" on page 21).
c. Save your ObjectsToGet configuration file.
3. Validate your ObjectsToGet configuration file (see "XML Schema Definition" on page 33).
4. Using an administrator account, connect to the Coveo Master server, and copy your custom ObjectsToGet
configuration file to a location accessible to CES.
Example: On the Coveo Master server, for an ObjectsToGet configuration file for standard and custom objects
and fields, save the file as:
D:CES7ConfigSalesforce_Basic_ObjectsToGet.xml.
4www.coveo.com 35
40. Coveo Platform 7.0 | Salesforce Connector Guide
You will specify the full path to this file when you configure your Salesforce source (see "ObjectsToGet File" on
page 107).
What's Next?
Create a mapping file to transfer the values of fields retrieved from Salesforce into CES fields (see "Creating a
Salesforce Mapping File" on page 69).
6.5 Salesforce ObjectsToGet Configuration File Example for Standard Objects
The ObjectsToGet configuration file example presented in this topic specifies to retrieve the following standard
Service Cloud objects and fields (including Chatter feed items) that are typically useful to index:
l Account
l Case
l Case Comment
l Contact
l Event
l Solution
l Task
l User
l Attachment
l Feed item (Chatter) CES 7.0.6196+ (November 2013)
l Feed comment (Chatter) CES 7.0.6196+ (November 2013)
The following code sample is the content of the ObjectsToGet configuration file example for standard Service Cloud
objects and fields.
<?xml version="1.0" encoding="utf-8"?>
<ArrayOfQuery xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Query>
<ObjectName>Account</ObjectName>
<Fields>
<string>Id</string>
<string>IsDeleted</string>
<string>Name</string>
<string>Type</string>
<string>BillingStreet</string>
<string>BillingCity</string>
<string>BillingState</string>
<string>BillingPostalCode</string>
<string>BillingCountry</string>
<string>Phone</string>
<string>Fax</string>
<string>AccountNumber</string>
<string>Website</string>
<string>Sic</string>
<string>Industry</string>
<string>AnnualRevenue</string>
4www.coveo.com 36
52. Coveo Platform 7.0 | Salesforce Connector Guide
<string>CommentType</string>
<string>ParentId</string>
<string>RelatedRecordId</string>
</Fields>
<ParentRelationships>
<ParentRelationship>
<RelationshipName>CreatedBy</RelationshipName>
<Fields>
<string>Name</string>
<string>Type</string>
</Fields>
</ParentRelationship>
<ParentRelationship>
<RelationshipName>InsertedBy</RelationshipName>
<Fields>
<string>Name</string>
</Fields>
</ParentRelationship>
</ParentRelationships>
<PolymorphicRelationships>
<PolymorphicRelationship>
<RelationshipName>CreatedBy</RelationshipName>
<ObjectName>User</ObjectName>
</PolymorphicRelationship>
</PolymorphicRelationships>
</Query>
</ArrayOfQuery>
What's Next?
Create a mapping file for fields from obtained objects (see "Salesforce Mapping File Example for Standard Objects"
on page 70).
6.6 Salesforce ObjectsToGet Configuration File Example for Knowledge Base
Salesforce Knowledge Base content correspond to non-standard objects and fields. When your Salesforce
organization contains Knowledge Base articles and you want to index their content, you must include specific
queries to your custom ObjectsToGet configuration file.
The ObjectsToGet configuration file example presented in this topic specifies to retrieve two arbitrary named
Knowledge Base objects:
l MyKBArticleType1
l MyKBArticleType2
Note: The Salesforce connector cannot index permissions of Knowledge Base articles like it can for other objects.
It is therefore recommended to create a separate ObjectsToGet configuration file and source for Knowledge Base
articles.
The following XML code is an ObjectsToGet configuration file example for Knowledge Base articles.
<?xml version="1.0" encoding="utf-8"?>
<ArrayOfQuery xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Query>
<ObjectName>MyKBArticleType1__ka</ObjectName>
<Fields>
<string>CaseAssociationCount</string>
<string>LastModifiedDate</string>
<string>ArticleNumber</string>
4www.coveo.com 48