There are some values that eAutomate needs, which do not have a corresponding value in Connectwise. For example, if you create an item record in eAuto, that item requires an inventory code or fee code, a product category, a sales code, perhaps a service code, if the item is “usable as an item” and can be serviced as an item (called “add-ons” in CW agreements), eAuto needs a distribution code. We offer the possibility for the integration to “copy” all the necessary eauto fields from an article that you create in eAuto and that only serves as a template. Businesses are only updated, not created. We need to connect the CW company to the eAuto# client. UOM is updated by CW if your units match CW and eAutomate (by name). If there is no UOM-compliant UOM in CW in eAutomate, UOM models are used. Either create a custom field in ConnectWise for the entity: we see to customers who have billed their IT contracts in eAuto without PSA tool that we synchronize with the same contracts after switching to CW Manage so that they can have contractual profit reports containing the old contract. Although it is possible, we do not recommend it, as it can cause many synchronization problems. Instead, we recommend that you have a new sync contract created and then change the contract number to eAuto to match the next revision of the old contracts. Note that you also need to update the above field in CW Manage where the eAuto# contract is saved.
If you have existing contracts bound by leases, it may be worth it. If you only use the CW Company Details Status field for Credit Hold, place this field so that it matches your holds (CH, etc.) in eAuto. Otherwise, you will create ZCJ_OnHoldCode and we will update. By filtering the custom fields we created for the agreements, we created two different sub-reports to display the details of the agreement in a certain way, depending on the control boxes that were enabled. This made it possible to print an invoice with different formats of display of contractual details by convention. Note: This guide makes some assumptions and is only provided as a guide. None of this is a prerequisite for using Huntress. Please use as you please. Please direct all Connectwise support questions to Connectwise or a ConnectWise consultant. A few thoughts before continuing: – This document assumes that the ConnectWise Manage partner has set up a funding agreement containing a position for Huntress and the partner understands how ConnectWise Manage works, its agreements, and its billing functions. – The partner must understand that this configuration will change the number “addition” to “Agreements” in ConnectWise.
In this case, you may have unintended effects on your billing if they are not configured correctly or if the settings are not compatible with your environment. – This updates “Huntress Product” on your “agreement” with the number of automatic terminals installed with Huntress. For example, if there are 50 agents in AUTOMATAs equipped with huntress installed, but that organization has 5 more stopping points than in PLCs, the line for Huntress is always updated to 50 agents, regardless of what the partner sets manually (probably 55). . . .