# Automation Professionals' Integration Toolkit Module

**URL:** <https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934>\
**Category:** 3rd Party Modules\
**Tags:** ignition83, perspective, scripting, vision, ignition81\
**Created:** [June 13, 2023, 12:42am UTC](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934 "2023-06-13T00:42:35Z")\
**Posts on this page:** 1\
**Showing post:** 90

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [February 12, 2024, 7:55pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934/90 "2024-02-12T19:55:28Z")

</div>

> [@pturmel](#):
>
> { Ahem. Tips on implementing `skipAudit` would be welcome... }

In the RPC message, it's just adding a boolean `true` for the `skipAudit` arg on the outgoing `Message`, which is parsed in the RPC handling (`com.inductiveautomation.ignition.gateway.servlets.gateway.functions.AbstractUpdateQuery`). On the gateway, `skipAudit` is a no-op (the call is simply never audited), as far as I can tell.

---

_[View the full topic](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934)._