This is the fifth in a short series of articles that introduces the new version of the integration between Sage CRM 2018 R3 and Sage 300cloud 2019.
This article will look at how the integration is administered and importantly how security policies are applied.
The revised integration has provided some very strong benefits for administrators. Implementors should find the integration much easier and simpler to install and set up. I've discussed in the previous articles that the integration itself is simpler with fewer moving parts; partners no longer have to worry about web deployment for some parts of the integration and the portal for other parts. No longer needing to make sure web deployment launches properly on every workstation removes a big potential hassle.
The administrative task for the new integration cover:
- The Simplified set-up integration steps
- New Synchronize Currencies link
- New Sage 300 User-level and Database-level security set-up screen
- Add logging for all individual set-up tasks
The new Sage 300 Administration replaces the previous Classic ASP integration pages with an integration that leverages the Sage CRM .NET API. This technology is modern and allows for a DLL to be provided by Sage 300, which implements an interface provided by Sage CRM.
As you can see from in the image below the Database Setup for a new integration has been simplified.
The grid used in the Support Database Setup screen now allows in-line editing and therefore does not need to display another page to allow for the entry of data. It also adds a new feature, the Company Email address field. If it’s defined, this Email address will be automatically populated to the Sage 300 O/E Order Entry > CRM Opportunity Tab > Email Cc field as we saw in an earlier article within the series.
In the old version of the integration, the Sage 300 Web Deployment needed to be set up. The image below shows the new screen that drives the synchronization of tables needed for the integration.
The development team wanted to replace as many “old” pieces as possible with the new integration. We've already seen how the integration makes use of direct invocation of Sage 300cloud Web Screens. At the same time that these are enabled and setup within the Sage 300cloud server the Sage 300 Web API is installed. This makes the Sage 300 Web API the ideal mechanism with which to implement synchronization. Consequently the Set Up process becomes much easier.
Logging is an important aspect of process management.
Therefore, a log file will be generated in the Sage CRM Log folder after the synchronization has completed.
And just like Synchronization has been rebuilt using the Sage 300 Web API, so has the Importing of Customers.
And the Sage 300 Web API is likewise used for the Importing of Vendors.
As has the importation of National Accounts.
The developers have been able to use the Sage 300 Web API endpoints for all the imports required by Sage CRM.
This includes the new Synchronize Currency Function
This allows for the synchronization of Sage 300 Currency Codes with Sage CRM and the update of the existing Sage CRM Currency Code Symbol. It also allows selection of Sage 300 Currency Codes for synchronization. And a log file will be generated in Sage CRM Log folder after synchronization.
But let's turn to the set up of security for new users.
This has been simplified with inline editing.
Rights for a user can be granted at the level of the Sage 300cloud database.
The set of the database-level security is much easier because of the inline editing.
In the next article, I will look again at the technology used in the integration AND the new approach to the proxy & why it matters.
The integration between Sage CRM 2018 R3 and Sage 300cloud 2019