Ask us

LLP CRM developed tools

Technology abstract pictureTelephone Integration – a connector (server, client or both) that allows interaction of Dynamics 365 (formerly known as Microsoft Dynamics CRM) with a customer’s telephone hardware. It features logic for incoming calls that allows definition of different scenarios based on identification of the phone number and a one-click dial for outgoing calls.

Consent Management GDPR – enabling the complete overview and management of consents related to contacts, leads and accounts. It covers all consents operations (requirement, granting, withdrawal, etc.), definition of different types of consents and their validity. It includes double opt-in functionality for automated consent by email based on templates in different languages.

Approval process – A general function developed to enable approval processes triggered by any action in the system. It includes the flexible definition of approval processes (based on roles, hierarchies or record owner approval). Approvals can be given on mobile devices or can be subject to third-party application integration.

Document Generator – is a service allowing the flexible definition of document templates including graphics, conditionally displayed sections, tables, etc. Formats can be set to doc, pdf or xls. The created document can be saved as an attachment (into Dynamics or SharePoint) or emailed.

Public Registry Connector – a set of components that check and enrich data from external registers – ARES for the Czech Republic, Finstat for Slovakia and Optem for Hungary. It allows data prefilling during Account creation or a scheduled data check in order to ensure data are up to date.

Prospector Connector – goes further than standard public registers as it allows definition of custom indicators used as a basis for customer segmentation.

Data Migration Tool – an application allowing the definition of a data source to be migrated to Dynamics 365 (formerly known as Microsoft Dynamics CRM). The mapping can include logical operators, and migration can be scheduled and run batches for migration of large numbers of records. The tool also includes extensive logging, allowing easy evaluation of the migration result.

Global Settings – is a pre-built function within Dynamics 365 (formerly known as Microsoft Dynamics CRM) that allows the storage of parameters and variables. These are then used for batch or scheduled workflows (as custom steps), allowing easy parameterisation of daily routine jobs.

General Web Service – an integration layer enabling seamless integration with Dynamics 365 using a SOAP WS or REST API. It can be deployed on Azure or on a customer’s server. It is fully logged into an SQL database allowing data reading or writing into any Dynamics 365 entity (including custom ones).

External Data Reader – a tool allowing scheduled data reads from an external database (MS SQL or Oracle). It includes interfaces for mapping attributes and transformations using XML. It can be scheduled by an external component (Windows Service) or by any trigger within Dynamics 365.

System Integration Tool – a set of components within Dynamics 365 that allows configuration of integration calls into external applications. The calls are triggered by actions within Dynamics 365 (such as creating a new customer). The logic includes XML mapping, full logging and error handling. It also offers a dashboard for administrators to monitor the status of integrations.

Custom Subgrid Plugin – even though Dynamics 365 includes editable grids, it still has some limitations that are resolved with LLP’s Custom Subgrid. It allows the creation and editing of related data directly on the form, tree visualisation and grouping.

Workflow Scheduler – a component allowing the scheduled execution of batch jobs that update data. It includes logic that enables the passing of data such as last execution time to subsequent runs.

Duplicate Detection check – standard duplicate detection in Dynamics 365 doesn’t prevent duplicate records from being created (it only warns the user). We have developed a “hard-stop” based on defined criteria such as VAT or Registration number. The conditions are configurable using XML.