Implementing Fastpath’s Audit Trail: Transfer between systems

This post is part of the series on Implementing Fastpath's Audit Trail and is part of the parent Implementing Fastpath's Assure Suite series.

As mentioned in a previous post, triggers are created in one company and can be deployed to other companies on the same system, but in a lot of cases, you might need to create them on a development system and then deploy them to the live one.

Fastpath Audit Trails does allow you to do this via the Save Settings function available as a button on the toolbar:

Select a location for the file and give it a name:

Then on the destination system, clikc the Open Settings button on the toolbar:

Browse to and select the exported file and click Open:

You’ll be prompted that this will append selections to the ones already present (a marked difference to the apply triggers to a different company function):

The triggers will be loaded into the other system into the company into which you’re logged; you’ll then need to go through the create triggers process and apply to other companies if required.