Good to know
Implementation & set-up
Praktische antwoorden over de installatie, configuratie en ingebruikname van Clickker en integraties, inclusief technische vereisten, testomgevingen en migraties.
How long does it take to implement an API integration with Exact?
The time required for implementation depends heavily on the complexity of the integration.
A simple integration involving the exchange of a single type of data generally requires less preparation and development than a process in which multiple systems work together.
Factors that influence the turnaround time include the availability of API documentation, the quality of the source data, the authorisations required and the amount of customisation involved.
Testing for exceptional situations and checking data consistency also take time.
A realistic schedule should therefore ideally be drawn up once the functional requirements and technical possibilities have been assessed.
How does the implementation of a new Clickker integration work?
The implementation of Clickker begins with an assessment of the existing IT environment and the required data exchange.
This involves, amongst other things, examining the Exact version used, the relevant accounting systems, the server environment and the external applications that need to be integrated.
The technical requirements are then checked. These include network access, the necessary software components, user rights and the configuration of the database environment.
Once installation is complete, the connection to Exact is checked and the required API endpoints can be tested.
Once the technical infrastructure is functioning correctly, the actual integration with the external application can be set up.
How can I avoid problems when migrating existing links?
A migration begins by documenting how the integration currently works.
Document what data is exchanged, which systems are involved and which processes depend on the integration.
Next, it must be investigated whether the new environment supports the same functionality and whether any adjustments are required.
Ideally, schedule the migration for a time when the impact on business operations will be minimal. You should also have a contingency plan in place in case the new connection does not function correctly.
Following the migration, the initial data processing operations must be carefully checked in order to detect any discrepancies quickly.
How is a new integration linked to the correct Exact system?
During the set-up process, it must be determined which Exact accounting system(s) may be used.
This usually requires specific identification details, access rights and configuration settings.
Where multiple systems are available, it is important to explicitly link each data flow to the correct system.
A good test involves, for example, requesting recognisable master data and checking whether it actually originates from the relevant records.
In the case of integrations that write data, checks must be carried out with particular care. After all, incorrectly processed transactions can have financial or operational consequences.
Is a separate test environment required before an integration goes live?
A separate test environment is strongly recommended, particularly where an integration may create or modify data.
In a test environment, developers can check whether data exchange is working correctly without directly affecting day-to-day operations.
Important tests include, for example, processing valid data, handling missing fields and preventing duplicate transactions.
Exception scenarios must also be tested, such as temporary network issues or an external application that is unavailable.
Where a separate test environment is not available, additional measures must be taken to minimise risks to production data.
Can Clickker be moved to a new server?
Yes, a Clickker installation can be migrated to a different server environment, provided the migration is carefully prepared.
It is necessary to check in advance whether the new server meets the current system requirements and whether all the necessary connections are available.
In addition, relevant configuration data, database settings and dependencies must be identified.
When migrating a server, it is important to ensure that the old and new installations do not process the same data at the same time.
According to the Clickker documentation, the old installation must be deactivated and a new API key must be requested when moving the server. Please refer to the current migration procedure for further details.
Can an existing Clickker installation be upgraded with CAS at a later date?
Yes, an existing Clickker environment can be expanded with the Clickker Automation Suite in suitable situations.
CAS adds capabilities to automate data flows and processes using visual workflows.
Before the upgrade is carried out, it must be checked whether the existing server environment meets the additional technical requirements.
It is also advisable to determine in advance which processes need to be set up within CAS and which existing integrations should be retained.
A phased roll-out makes it possible to automate one process first and then add further applications.
What needs to be tested before an integration is put into production?
Before an interface goes live, it must be checked that data exchange functions correctly in both normal and exceptional circumstances.
For example, check whether data is imported in full, whether required fields are validated, and whether existing records are recognised correctly.
In addition, error messages, duplicate processing and the system’s behaviour in the event of temporary connection problems must be tested.
In the case of financial or logistical processes, it is important that the results are also checked from a functional perspective by the staff members responsible.
Only once the key scenarios have been successfully tested can the integration be put into operation in a controlled manner.
What information do I need to provide for a Clickker or CAS installation?
To ensure efficient installation, it is important that the necessary technical and organisational details are available in advance.
Please provide the name of the organisation, the contact persons, the preferred installation type and details of the application and database servers.
Information is also required regarding the Exact version used, the accounting systems to be linked, and any external developers.
When CAS is installed, the specific system requirements for CAS must also be checked.
Clickker provides an installation checklist for this purpose. By completing this checklist together with the IT administrator, you can ensure the installation is better prepared.
What technical preparations are required for the installation of Clickker?
For a Clickker installation, various technical specifications and facilities must be in place.
Depending on the installation, you will need, amongst other things, access to the application server, information about the SQL Server environment and a suitable technical user account.
It is also necessary to check whether the server meets the current system requirements and whether the necessary network connections are available.
In a CAS installation, additional components may be required, such as IIS components, external URLs and SSL certificates.
It is advisable to discuss these preparations with the system administrator in advance. This will help to avoid unnecessary delays during the installation.