Tutorial on How to Setup Ohioedge CRM

Tutorial on How to Setup Ohioedge CRM

• Is This Tutorial For Me?

• Table of Content

• What’s Next?

• References

Home

Executive Summary

• Who is the intended audience for this tutorial?

• What knowledge and skills should I expect to acquire by the end of this tutorial?

• What is the pre-requisite for taking this tutorial?

• How long does it take to complete this tutorial?

Home -> Executive Summary

Who is the intended audience for this tutorial?

• This tutorial is designed for Ohioedge CRM administrators that are responsible for the hands-on implementation of Organizational Hierarchy, Workflow, and Security models for their organizations.

• Ohioedge CRM is an enterprise-class application. It is designed to encompass and bring together a large number of processes and people. Higher the number, more involved is the design phase. This requires that the setup and configuration activity be well thought out and planned in advance. This guide documents the ‘process’ of building Ohioedge CRM hierarchy and process models. In this guide we have explained the creation of organizational hierarchy/chart and process models in a tutorial-like format. An Ohioedge CRM administrator should find this guide a good source of information on building organizational models.

Home -> Executive Summary

What knowledge and skills should I expect to acquire by the end of this tutorial?

– How to create/build organizational (vertical) hierarchy model. For example, organization has two regions, each region has four business units, etc.

– How to create/build business process (horizontal) model (also referred as workflow model). For example, first process is “Make a cold call” followed by “Send company literature”, etc.

– How to create/build security model. For example, grant “User1”, a “Worker” privilege on “Make a cold call” process. This also includes maintaining security objects such as, user, role, privilege, grants, etc.

– How to create HTML/PDF reports, Charts, Letter Templates, Email Templates, and Template Scripts.

Home -> Executive Summary

What is the pre-requisite for taking this tutorial?

– You will need to have your organizational hierarchy, workflow and security models drawn on paper.

– For creating Template scripts, you will need to know JSP.

– For creating Letter Templates and Email Templates you will need to know HTML.

– For creating query-based HTML/PDF reports, Charts, and Campaign you will need to know SQL.

– For PDF reports and Charts, you will need to know open-source JapserReports and JFreeChart.

Home -> Executive Summary

How long does it take to complete this tutorial?

– Depending on your level of expertise with the Organizational, Workflow, and Security modeling, and understanding of your business requirements this tutorial could take anywhere from two (2) to ten (10) days.

– The material covered in this tutorial is also at the core of our five (5) day on-site course - Ohioedge CRM Administrator’s Training.

Home -> Executive Summary

• End of Executive Summary Chapter

Table of Content

• OhioedgeCRM Interactive Environment– What is a component?

– Learning GUI

– Accessing a component

– Working with a component• Search/Select function

• Update function

• Create function

• Delete function

– Working with a List

• Overview– Roadmap

Home -> Content

Table of Content (contd.)

• Creating an Organization– Creating a Shared Organization

• Connect to a database

• Create records

• Component level security

• How to create entitlements?

• How to setup shared organization?– List of organization-independent components

– Creating a New (Functional) Organization• OrgAdmin user of the new organization

• OrgAdmin user privileges

• Inheritance of privileges diagram

• Login

Home -> Content

Table of Content (contd.)• Component Security– Basic Security

– Primary users of OhioedgeCRM

– How are privileges granted to the primary users of OhioedgeCRM• Group component

• Role component

• Privilege component

• RolePrivilege component

• ComponentStatusType component

• Component component

• ComponentStatus component

• ComponentStatusTypePrivilege component

– How is a Mechanism granted component management privileges diagram

– Use Case I• Defining Use Case scenario in OhioedgeCRM

Home -> Content

Table of Content (contd.)

• Planning– Model Overview

• What are these models?

• Organizational Hierarchy Model– Nomenclature used in the Organizational hierarchy model

• Organizational Process Model I– Explanation

• Organizational Process Model II– Explanation

• License Setup

• Prologue

• Configuring the Foundation Module– OrgAdmin and ApplAdmin user privileges on the Foundation Module co

mponents

Home -> Content

Table of Content (contd.)

– Foundation Module components• Organization component• NamePrefix component• NameSuffix component• NameTitle component• Employee component• State component

• Configuring the Customer Module– OrgAdmin and ApplAdmin user privileges on the Customer Module compo

nents– Customer Module components

• Customer component• CustomerPerson component• BuyerRole component• RequirementStatus component

Home -> Content

Table of Content (contd.)

• Configuring the Publisher Module– OrgAdmin and ApplAdmin user privileges on the Publisher Module comp

onents

– Publisher Module components• Script component

– How to upload your JSP script file?

• LetterTemplate component– How to upload your HTML letter template file?

– Example LetterTemplate

• EmailTemplate component– How to upload your TXT email template file?

– Example EmailTemplate

• Configuring the Workflow Module– User/Mechanism sub-module

• OrgAdmin and ApplAdmin user privileges on the User/Mechanism sub-module components

Home -> Content

Table of Content (contd.)

• User/Mechanism sub-module components– MechanismType component

– Mechanism component

– Workflow Security• How is workflow security defined?

• Workflow Security Diagram

– Security sub-module• OrgAdmin and ApplAdmin user privileges on the Security sub-module compo

nents

• Security sub-module components– Privilege component

– Role component

– RolePrivilege component

– Workflow Statuses sub-module• OrgAdmin and ApplAdmin user privileges on the Workflow Statuses sub-mod

ule components

Home -> Content

Table of Content (contd.)

• Workflow Statuses sub-module components– ActivityStatusType component

– AssignmentStatusType component

– ActivityScheduleStatusType component

– Workflow-Security Integration sub-module• Workflow-Security Integration sub-module components

– ActivityStatusTypePrivilege component

– AssignmentStatusTypePrivilege component

– ActivityScheduleStatusTypePrivielge component

– Custom fields sub-module• OrgAdmin and ApplAdmin user privileges on the Custom fields sub-module c

omponents

• Custom fields sub-module components– DataType component

– DataConstraint component

Home -> Content

Table of Content (contd.)

– Workflow Definition sub-module• OrgAdmin and ApplAdmin user privileges on the Workflow Definition sub-m

odule components

• Workflow Definition sub-module components– JunctionType component

– ActivityType component

» Organizational Chart/Hierarchy Model

» Organizational Process Model

» isUOB field properties

» List of ActivityTypes based on the 2 models

» How to create ActivityType?

» ActivityType for Organizational Chart/Hierarchy Model

» ActivityType for Organizational Process Model

– Junction component

– InputType component

– InputFactoryType component

Home -> Content

Table of Content (contd.)

– InputFactory component

» How to upload your SQL file?

– ActivityTypeHierarchy component

» Important Note

» ActivityTypeHierarchy Maintain page

» Creating a root level ActivityTypeHierarchy

» Creating a next level ActivityTypeHierarchy

» How to reset ActivityTypeHierarchy model?

» Login again after resetting ActivityTypeHierarchy model

» How to view the ActivityTypeHierarchy model?

– ActivityTypeHierarchyMechanism component

– ActivityTypeHierarchyInputFactory component

• Publisher-Workflow Integration Module• OrgAdmin and ApplAdmin user privileges on the Publisher-Workflow Integrat

ion module components

Home -> Content

Table of Content (contd.)

• Publisher-Workflow Integration module components– DocumentType component

– MimeType component

– InstructionType component

– Document component

– Instruction component

– ActivityTypeInstruction component

• Customer-Workflow Integration Module– Campaign component

• How to create a campaign?

• Robot: Campaign Services– How to start a campaign?

– How to view the results of starting a campaign?

Home -> Content

Table of Content (contd.)

• Robot: Workflow services– How to start the workflow services?

• Activity Component– OrgAdmin and ApplAdmin user privileges on the Activity component– Activity Maintain page– Creating an Activity– Accessing an Activity

• Activity accessed via an html report

• Activity accessed by drilling down on the history of a customer

• What happens when a Mechanism tries to access an Activity that is not assigned to that Mechanism?

• Comparison Chart• Steps for configuring a new functional organization

Home -> Content

Overview

– Every Ohioedge CRM installation requires one mandatory Organization - SetupOrg. The setup organization consists of organization-independent data such as Name Prefix, Name Suffix, etc.

– Ohioedge CRM database included with the download consists of SetupOrg and a sample organization - DemoOrg configured for reference purposes.

– If you are starting with this pre-configured Ohioedge CRM database, you don’t have to configure the Setup organization. You can directly start implementing your organization by referencing the Demo organization.

Home -> Content -> Overview

Roadmap

• Before you start configuring an organization, you need to create an organization and an administrator user that belongs to an OrgAdmin user group.– Ohioedge CRM ASP Service subscribers please skip to OrgAdmin

Privileges.

– If you are building on the top of pre-configured database, you already have SetupOrg configured so please skip to Creating a New Organization.

– If you are implementing Ohioedge CRM from scratch (empty database), begin with Creating Setup Organization.

Home -> Content -> Overview

Roadmap

ASP ServiceSubscribers

Create aSetup

Organization

Configure aSetup

Organization

Create aFunctional

Organization

Configure aFunctional

Organization

Pre-configuredDatabase

Create aSetup

Organization

Configure aSetup

Organization

Create aFunctional

Organization

Configure aFunctional

Organization

Starting fromScratch

(Empty Database)

Create aSetup

Organization

Configure aSetup

Organization

Create aFunctional

Organization

Configure aFunctional

Organization