Until recently, people used a technique called symmetric key cryptography to secure information being transmitted across public networks in order to make sound equipment sales shopping more secure. This method involves encrypting and decrypting a sound equipment sales message using the same key, which must be known to both parties in order to keep it private. The key is passed from one party to the other in a separate transmission, making it vulnerable to being stolen as it is passed along.
With public-key cryptography, separate keys are used to encrypt and decrypt a message, so that nothing but the encrypted message needs to be passed along. Each party in a sound equipment sales transaction has a *key pair* which consists of two keys with a particular relationship that allows one to encrypt a message that the other can decrypt. One of these keys is made publicly available and the other is a private key. A sound equipment sales order encrypted with a person's public key can't be decrypted with that same key, but can be decrypted with the private key that corresponds to it. If you sign a transaction with your bank using your private key, the bank can read it with your corresponding public key and know that only you could have sent it. This is the equivalent of a digital signature. While this takes the risk out of sound equipment sales transactions if can be quite fiddly. Our recommended provider listed below makes it all much simpler.Microsoft CRM Implementation & Remote Support – overview for V.P. IT
by: Andrew Karasev
Microsoft CRM is now on the scene and it is increasing its market share, due to the Microsoft Business Solutions muscles and marketing strategy. It is tightly integrated with other Microsoft Business Solutions products such as Microsoft Great Plains, Solomon, Navision. Being relatively inexpensive in comparison to competitors, like Siebel, Oracle - Microsoft CRM opens you the door for worldwide operations automation.
We would like to give you pluses and minuses of Microsoft CRM.
1. Web and MS Outlook based client - this means that you don't need additional installations or training - everyone is using Outlook if you are on Windows XP/2000/2003
2. SQL Server database - just to mention
3. Integration with Microsoft Exchange 2003/2000 - this means that replies to CRM originated emails will be captured and store in CRM as activities for the Contact, Account or Lead.
4. Remote Support - I would say - this would be in the nature of MS CRM - you host it's database in your headquarter and users will connect to it worldwide via Internet Explorer
5. Integration with other MBS products - currently it has integration interface with Microsoft Great Plains
6. Microsoft technologies dependence - yes, this is true and maybe considered as minus, it doesn't work with Netscape or Mozilla browser.
7. New Product - it is relatively new on the market and may not have industry specific features yet
Also if you are considering some customization scenarios, we would suggest you to review the options below:
1. Microsoft CRM SDK – this is software development kit with C# and partly VB.net code samples – it is supported by Microsoft Business Solutions technical support. It is based on web service calls, if you are C# .NET developer – you are excellently positioned to do this type of customizations. This is the preferred modification scenario and this should be easily upgradeable customization. VB.Net examples will be available soon.
2. Legacy SQL Data integration. This is also easy and safe. If you have SQL database, sitting on the same or linked SQL Server – you can create ASPX .Net application and simply integrate it into CRM. You can place it on the navigation bar or menu in isv.config – please refer to MS CRM SDK
3. Legacy ASP integration – this is somewhat more sophisticated. You have to deploy HTTP handler to be a middle party between CRM which is .Net based and ASP which is legacy IIS. The trick is – you have to have INI file with security settings to penetrate into MS CRM with proper credentials, calling web service.
4. Microsoft Exchange Programming. Microsoft CRM has Exchange connector – which moves CRM incoming email to MS if it has GUID in its subject. You can alter this logic (for instance - move email to CRM if it doesn't have GUID but it is from the sender who is contact or account in MS CRM). Refer to MS Exchange SDK onsyncsave event handling. Then simply apply some MS CRM SDK programming - you need some COM+ objects creation and VB programming experience.
5. Direct SQL touch – in #4 above I described you the scenario with MS Exchange handlers – this would be ideal world if MS CRM SDK does the job. But – in real world this is not always true – you have to do direct flags correction in CRM database (like making Activity closed, moving email attachments/octet streams, etc). This is not supported by MBS technical support – but you can rescue to this technique if you have to get job done.
6. MS CRM Customization tool – this is rather end-user tool and we don't describe it here – read the manual. We've described above the options to use when this tool doesn't do the job
7. Crystal Reports - feel free to create Crystal report - tables and views structure is self explanatory. Try to avoid the temptation to create your own SQL view or stored procedure in MS CRM database, instead - create custom database and place your view and stored proc in it.
Happy selection, implementation and modification! If you want us to do the job - give us a call 1-866-528-0577! help@albaspectrum.com
About The Author
Andrew Karasev is Chief Technology Officer in Alba Spectrum Technologies – USA nationwide Microsoft CRM, Microsoft Great Plains customization company, based in Chicago, Boston, San Francisco, San Diego, Los Angeles, Houston, Dallas, Atlanta, and Miami and having locations in multiple states and internationally (www.albaspectrum.com), he is Dexterity, SQL, VB/C#.Net, Crystal Reports and Microsoft CRM SDK developer.
akarasev@albaspectrum.com
|
|
