| Usually workflow & messaging is realized in CRM | | | | Plains tables structureo Microsoft Exchange/Outlook |
| and then transactions are just logged into Accounting | | | | approach. This is the second way - when you do not |
| ERP/MRP. In the case of Microsoft Business Solutions | | | | want to deploy Lotus Domino, and would be OK with |
| products: Microsoft Great Plains, Navision, Solomon, | | | | simple messaging and notification through Microsoft |
| Axapta the natural CRM choice would be Microsoft | | | | Exchange. The technical realization should either |
| CRM. However typical CRM application targets Sales | | | | involve Dexterity or SQL trigger, calling COM object |
| automation, which is usually not applicable to | | | | (Dexterity) or simply sending notification email from |
| government structure, non-profit or public company | | | | MS SQL Server. The scenario to post or take off |
| (community services, public utilities, churches, | | | | hold from Great Plains transaction could be realized |
| charities, etc.). Not-for-profit organization needs | | | | via MS Exchange event sink - this MS Exchange |
| purchasing and requisition workflow, payroll approval | | | | event handler will check all the messages and when |
| workflow, and in certain cases special General Ledger | | | | the one has certain criteria - it calls MS SQL Server |
| (GL) transactions workflow. Microsoft CRM doesn't | | | | stored procedure in the Great Plains company |
| provide the functionality. Then how could this be | | | | databaseo Programming Tools. Java agent to address |
| realized? We'll provide two scenarios to realize this | | | | Lotus - you need either Sun JDK or somewhat more |
| customization:o Lotus Notes/Domino approach. In | | | | advanced: VisualCafe or JBuilder. Great Plains |
| Great Plains you could realize either Great Plains | | | | Dexterity trigger should be done in Dexterity IDE - |
| Dexterity triggers or MS SQL database trigger on | | | | this language requires expertise and it is difficult to |
| certain events (Purchase Order creation, Payroll | | | | code without experience, Microsoft Exchange event |
| Transaction, GL transaction). This event calls COM+ | | | | sink should be programmed in Visual Studio as COM+ |
| application and this one in turn creates Lotus objects | | | | application, then you need to register COM+ |
| via Java agent (Lotus Notes Domino should be | | | | application through Control |
| version 6.0 or newer). This is basically the bridge. | | | | Panel->System->Component Serviceso |
| Then in Lotus you have to design workflow - but this | | | | Feasibility. To be honest and do not set unrealistic |
| is natural task for Lotus and it is not difficult. Users | | | | expectations - this Workflow implementation is |
| should work in Lotus to get transactions approved | | | | pretty serious project and we do not recommend if |
| and when it should be posted in Great Plains - Lotus | | | | for small non-profit organization - it is rather for large |
| calls SQL script against Great Plains company | | | | and mid-size-to-large structure. |
| database. Developer should know Microsoft Great | | | | We encourage you to analyze your alternatives. |