sage crm developers course

20
Sage CRM Developers Course Coding the Web SelfService COM API (1)

Upload: talasi

Post on 25-Feb-2016

43 views

Category:

Documents


1 download

DESCRIPTION

Sage CRM Developers Course. Coding the Web SelfService COM API (1). Looking ahead to the classes. DP01: Introduction to the Development Partner Program DP02: Entities and the Data Model (Part 1 of 2) DP03: Entities and the Data Model (Part 2 of 2) - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Sage CRM Developers Course

Sage CRM Developers Course

Coding the Web SelfService COM API (1)

Page 2: Sage CRM Developers Course

Looking ahead to the classes

DP01: Introduction to the Development Partner ProgramDP02: Entities and the Data Model (Part 1 of 2)DP03: Entities and the Data Model (Part 2 of 2)DP04: Implementing Screen Based Rules (Part 1 of 2)DP05: Implementing Screen Based Rules (Part 2 of 2)DP06: Screen and User Independent Business RulesDP07: Workflow (Part 1 of 2)DP08: Workflow (Part 2 of 2)DP09: Using the API Objects in ASP Pages (Part 1 of 2)DP10 : Using the API Objects in ASP Pages (Part 2 of 2)

DP11: Using the Component ManagerDP12: Programming for the Advanced Email ManagerDP13: Using the Web Services APIDP14: Using the Web Services API (Part 2 of 2)DP15: Coding the Web Self Service COM API (Part 1 of 2)DP16: Coding the Web Self Service COM API (Part 2 of 2)DP17: Using the .NET API (Part 1 of 2)DP18: Using the .NET API (Part 2 of 2)

Page 3: Sage CRM Developers Course

Agenda

Introducing CRM Self ServiceTechnical Features and ArchitectureAdvantages and LimitationsAnonymous and Authenticated AccessRegistry Settings and Self Service ConfigurationSimple Pages including Logon and Logoff

Page 4: Sage CRM Developers Course

What is CRM Self Service?

Allows customers to access and request services and support over the webCan integrate key features of Sage CRM with a corporate websiteA means to create a self service website.Exposes CRM data to the WWW.

Enables powerful web-based sales, marketing and customer support solutionsCan capture new data straight to Sage CRM entities.How much, or little, data is exposed or captured is entirely up to the self service implementation!

Page 5: Sage CRM Developers Course

CRM Self Service Technical Features

Use familiar Sage CRM object methods and propertiesGreat flexibility – leverage industry standard scripting technologies to integrate with existing websiteFlexible security features – define different levels of access

Page 6: Sage CRM Developers Course
Page 7: Sage CRM Developers Course

Users vs. Visitors

A User:someone who logs into CRM using the familiar CRM interfacethey have a paid license ‘seat’represented in the database as a record on the user table

A Visitor:someone who accesses CRM via the Web Self Service websitenumber of visitors is limited by WSS separate licensing arrangementsRepresented in the database as a record on the person table

Page 8: Sage CRM Developers Course

Demonstration

Use Anonymous access to create a new Lead(Not to be confused with the WebtoLead feature)Within CRM promote created Lead into Company and OpportunityAssign selfservice logon rights to created contact.Logon as this new contact and view opportunitiesLogon new Case

Page 9: Sage CRM Developers Course

The Registry SettingsClass registrations

Page 10: Sage CRM Developers Course

The registration

Page 11: Sage CRM Developers Course

The eWareSelfService Object

eWareSelfService is referenced in ewaress.jsIt is a child of the eWare ObjectInherits all its properties and methodsHas a few extra, self service specific methods.Only one registered objectUses data from “Software/eWare/SelfService”

Page 12: Sage CRM Developers Course

The SelfService configuration

Always points to “Software/eWare/SelfService” registry entryNot CRM install specific, even though it can be altered there.

Page 13: Sage CRM Developers Course

Building a Self Service System

Anonymous UsageBuild a Registration (New Lead) PageAuthenticated UsageLogon PageLogoff PageMain Page (user details)Record List Page (users cases)New Record Page (new case)Search Page (knowledge base)

Page 14: Sage CRM Developers Course

Block Usage

Self Service is a COM based API Usage of the blocks different from main application extension API. Self Service environment lacks a user 'logon' that generates a CRM SID (Session ID) or context Therefore can't use any API objects/methods that rely on session or context information for building URLs. Can't use CRM.Button()CRM.GetTabs()CRM.URL() etc, Can't use the output mechanism of a typical application extension ASP pageCRM.AddContent(myBlock.Execute(Arg));Response.Write(CRM.GetPage());Self Service Pages use the more basic Response.Write(myBlock.Execute(Arg));

Page 15: Sage CRM Developers Course

Logoff

Typical Codeif(CRM.Authenticated){CRM.EndSSSession(Request.Querystring, Request.Form, Request.Cookies("eware"));Response.Redirect("customlogon.asp")}else{Response.Redirect("customlogon.asp")}

Page 16: Sage CRM Developers Course

COM Objects available in the Self Service API

Page 17: Sage CRM Developers Course

COM Objects not available in Self Service API

Page 18: Sage CRM Developers Course

Q&A

Page 19: Sage CRM Developers Course

Looking ahead to the classes

DP01: Introduction to the Development Partner ProgramDP02: Entities and the Data Model (Part 1 of 2)DP03: Entities and the Data Model (Part 2 of 2)DP04: Implementing Screen Based Rules (Part 1 of 2)DP05: Implementing Screen Based Rules (Part 2 of 2)DP06: Screen and User Independent Business RulesDP07: Workflow (Part 1 of 2)DP08: Workflow (Part 2 of 2)DP09: Using the API Objects in ASP Pages (Part 1 of 2)DP10 : Using the API Objects in ASP Pages (Part 2 of 2)

DP11: Using the Component ManagerDP12: Programming for the Advanced Email ManagerDP13: Using the Web Services APIDP14: Using the Web Services API (Part 2 of 2)DP15: Coding the Web Self Service COM API (Part 1 of 2)DP16: Coding the Web Self Service COM API (Part 2 of 2)DP17: Using the .NET API (Part 1 of 2)DP18: Using the .NET API (Part 2 of 2)

Page 20: Sage CRM Developers Course