Sometimes workflow & messaging is realized in CRM and then transactions are simply logged into Accounting/ERP/MRP. Within the case of Microsoft Business Solutions product: Microsoft Nice Plains, Navision, Solomon, Axapta the natural CRM alternative would be Microsoft CRM. However typical CRM application targets Sales automation, that is sometimes not applicable to government structure, non-profit or public company (community services, public utilities, churches, charities, etc.). Not-for-profit organization wants buying and requisition workflow, payroll approval workflow, and in certain cases special General Ledger (GL) transactions workflow. Microsoft CRM doesn't give the functionality. Then how could this be realized? We have a tendency to'll provide 2 situations to understand this customization:

o Lotus Notes/Domino approach. In Nice Plains you could notice either Nice Plains Dexterity triggers or MS SQL database trigger on sure events (Purchase Order creation, Payroll Transaction, GL transaction). This event calls COM+ application and this one in flip creates Lotus objects via Java agent (Lotus Notes Domino should be version 6.0 or newer). This is primarily the bridge. Then in Lotus you have to style workflow - but this can be natural task for Lotus and it's not difficult. Users ought to work in Lotus to urge transactions approved and when it should be posted in Nice Plains - Lotus calls SQL script against Great Plains company database. Developer should know Microsoft Nice Plains tables structure

o Microsoft Exchange/Outlook approach. This is often the second means - when you are doing not need to deploy Lotus Domino, and would be OK with easy messaging and notification through Microsoft Exchange. The technical realization should either involve Dexterity or SQL trigger, calling COM object (Dexterity) or simply sending notification email from MS SQL Server. The scenario to post or set out hold from Nice Plains transaction may be realized via MS Exchange event sink - this MS Exchange event handler can check all the messages and when the one has sure criteria - it calls MS SQL Server stored procedure within the Great Plains company database

o Programming Tools. Java agent to address Lotus - you wish either Sun JDK or somewhat additional advanced: VisualCafe or JBuilder. Nice Plains Dexterity trigger ought to be done in Dexterity IDE - this language requires experience and it is difficult to code while not experience, Microsoft Exchange event sink ought to be programmed in Visual Studio as COM+ application, then you wish to register COM+ application through Management Panel->System->Component Services

o Feasibility. To be honest and don't set unrealistic expectations - this Workflow implementation is pretty serious project and we have a tendency to do not advocate if for small non-profit organization - it's rather for large and mid-size-to-giant structure.

Leave a Reply