Sales 2 Design Summary

Sales Management 2 Midtier Design Summary Document Revision Date: <04-Jan-08>

1.

Project Overview

This project rewrite existing Sales Case workflows (General Lead, Referral, Flagship/ Voyager, AMS) into structured optimal workflows. It utilizes a vendor product to deliver work management capabilities. It enhances sales case functionalities. Will provide ability to interact with other applications (open account, resource management etc) It is an agile project with 2 teams. Team X and Team Y. Team X has been working on building basic Workflow functionalities and Pre-commitment workflow. Team Y has been working on AMS related functionality. Currently, we are in sprint 9 of total 19 sprints. Project Release is Summer 2008, V11.000.0

2.

Sales Management 2 Application Architecture

2. retrieval/update through SP call

Enterprise OED Application Server 4. Batch Job send data through MQ

UI

1. User retrieval /update

SOA Midtier Trigger midtier updates Filenet App Sever 3. retrieval/update through Java RMI filenet API call

3.

Highlights 1. Data storage Data collected through the life of sales case fall into 2 categories: Client Permanent Data: Use existing OED application, save into Enterprise. Sales Case Data: Transient Sales Case Data saved in Enterprise Sales Case tables. (Master Copy). Some of the data may impact Sales Work Flow decision, those minimum data also saved in Filenet DB. Activity/Workflow Step information is controlled by Filenet System with Enterprise as shadow. 2. Interaction Between Filenet and Mid-tier Mid-tier calls Filenet RMI java API to retrieve/update Filenet data Filenet component queue manager calls Mid-tier when workflow hits a system step. 3. User Single Sign-on User logged on Wave desktop does not need to log onto Filenet second time. Wrapping TE Credential Manager Service and Filenet Security Manager.

4.

Challenges 1. Customize Vendor workflow system for specific application need. Work around constraints. 2. Synch up data between Enterprise and Vendor System. 3. Build a generic workflow technical service the same time when build the Sales Workflow. 4. Due to lack of special account roles (like Sunguard account) implementation in SOA, we have to find workaround to get those account roles.