Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Step 1 - Install CloudConnector and collect information

To connect to the customer’s Visma Lønn server over the internet, the CloudConnector software must first be installed. Please refer to this guide for installing CloudConnector on the customer’s Visma Lønn server:

https://cma.zendesk.com/hc/en-us/articles/360016409374-Connecting-to-Visma-L%C3%B8nn

Note that there is a separate CloudConnector version for each version number of Visma Lønn, so make sure that the correct version is installed.

If the customer upgrades Visma Lønn (for example from version 16.1 to 17.0) then a new CloudConnector for version 17.0 must also be installed.

After completing the steps above you should have the following pieces of information ready:

  • CloudConnector key

  • Visma Lønn login (username and password)

  • Visma Lønn VAF SDK BAPI key

  • Exact ‘firmanavn’ for Visma Lønn clients to integrate with, as shown in Visma Lønn

It is recommended to ask the user to check that the username and password work correctly in Visma Lønn. If a one-time password is set, or the account is locked, this may cause problems in the next step.

Step 2 - Register information on Canvas

Find and manage the client account

In Canvas, go to the “Clients” tab:

Search for the customer’s Canvas account, and click “Manage” on the account you wish to use. (If you do not see the customer’s Canvas account in the list of clients, please contact ConnectMyApps - the account may not have been added to your organization yet.)

You will see a text like this indicating that you are managing the customer’s user account:

Add the application

Especially if you are adding multiple apps, it is important to add the company name to the app title, to differentiate among the various apps. Otherwise you may end up choosing the wrong app later, when building your integration.

Common issues:

  • No labels