Sage CRM Developers Course Coding the Web Self

Sage CRM Developers Course Coding the Web Self. Service COM API (1)

Looking ahead to the classes DP 01: Introduction to the Development Partner Program DP 02: Entities and the Data Model (Part 1 of 2) DP 03: Entities and the Data Model (Part 2 of 2) DP 04: Implementing Screen Based Rules (Part 1 of 2) DP 05: Implementing Screen Based Rules (Part 2 of 2) DP 06: Screen and User Independent Business Rules DP 07: Workflow (Part 1 of 2) DP 08: Workflow (Part 2 of 2) DP 09: Using the API Objects in ASP Pages (Part 1 of 2) DP 10 : Using the API Objects in ASP Pages (Part 2 of 2) DP 11: Using the Component Manager DP 12: Programming for the Advanced Email Manager DP 13: Using the Web Services API DP 14: Using the Web Services API (Part 2 of 2) DP 15: Coding the Web Self Service COM API (Part 1 of 2) DP 16: Coding the Web Self Service COM API (Part 2 of 2) DP 17: Using the. NET API (Part 1 of 2) DP 18: Using the. NET API (Part 2 of 2)

Agenda Introducing CRM Self Service Technical Features and Architecture Advantages and Limitations Anonymous and Authenticated Access Registry Settings and Self Service Configuration Simple Pages including Logon and Logoff

What is CRM Self Service? Allows customers to access and request services and support over the web Can integrate key features of Sage CRM with a corporate website A means to create a self service website. Exposes CRM data to the WWW. Enables powerful web-based sales, marketing and customer support solutions Can 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!

CRM Self Service Technical Features Use familiar Sage CRM object methods and properties Great flexibility – leverage industry standard scripting technologies to integrate with existing website Flexible security features – define different levels of access

Users vs. Visitors A User: someone who logs into CRM using the familiar CRM interface they 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 website number of visitors is limited by WSS separate licensing arrangements Represented in the database as a record on the person table

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

The Registry Settings Class registrations

The registration

The e. Ware. Self. Service Object e. Ware. Self. Service is referenced in ewaress. js It is a child of the e. Ware Object Inherits all its properties and methods Has a few extra, self service specific methods. Only one registered object Uses data from “Software/e. Ware/Self. Service”

The Self. Service configuration Always points to “Software/e. Ware/Self. Service” registry entry Not CRM install specific, even though it can be altered there.

Building a Self Service System Anonymous Usage Build a Registration (New Lead) Page Authenticated Usage Logon Page Logoff Page Main Page (user details) Record List Page (users cases) New Record Page (new case) Search Page (knowledge base)

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. Get. Tabs() CRM. URL() etc, Can't use the output mechanism of a typical application extension ASP page CRM. Add. Content(my. Block. Execute(Arg)); Response. Write(CRM. Get. Page()); Self Service Pages use the more basic Response. Write(my. Block. Execute(Arg));

Logoff Typical Code if(CRM. Authenticated) { CRM. End. SSSession(Request. Querystring, Request. Form, Request. Cookies("eware")); Response. Redirect("customlogon. asp") } else { Response. Redirect("customlogon. asp") }

COM Objects available in the Self Service API

COM Objects not available in Self Service API

Q&A

Looking ahead to the classes DP 01: Introduction to the Development Partner Program DP 02: Entities and the Data Model (Part 1 of 2) DP 03: Entities and the Data Model (Part 2 of 2) DP 04: Implementing Screen Based Rules (Part 1 of 2) DP 05: Implementing Screen Based Rules (Part 2 of 2) DP 06: Screen and User Independent Business Rules DP 07: Workflow (Part 1 of 2) DP 08: Workflow (Part 2 of 2) DP 09: Using the API Objects in ASP Pages (Part 1 of 2) DP 10 : Using the API Objects in ASP Pages (Part 2 of 2) DP 11: Using the Component Manager DP 12: Programming for the Advanced Email Manager DP 13: Using the Web Services API DP 14: Using the Web Services API (Part 2 of 2) DP 15: Coding the Web Self Service COM API (Part 1 of 2) DP 16: Coding the Web Self Service COM API (Part 2 of 2) DP 17: Using the. NET API (Part 1 of 2) DP 18: Using the. NET API (Part 2 of 2)