Purging EDI Data on specific node to reduce performance issues

Description: To reduce performance issues when purging EDI data, you can use the 'PurgeEdiDataOnly' code extension to select a specific node and run the background job that performs the purge action for the EDI data based on the EDI settings. This helps to aggressively purge EDI data such as EdiBatchProcess, EdiError, EdiInterchange, EdiQueuedInterchange and EdiEvent. Since the EDI data is not archived, you can schedule to purge the EDI job on any available node.

Abstract Base Class: GroovyApi

Methods: execute()

Module: EDI

Version Added: 3.3

Requires Code Extension Name or Name Pattern: Yes

Code Extension Name or Name Pattern: PurgeEdiDataOnly

Where to Specify Code Extensions of this Type: Not necessary. Groovy jobs are called by name.

System-Seeded Code Extensions Using this Type: None