Excluding Path Patterns from the RMR Process in S2IX 6.0

Excluding Path Patterns from the RMR Process in S2IX 6.0

S2IX 6.0.4.15 now supports excluding specified path patterns from the Records Management process in both legacy and modern modes, which will allow administrators to configure patterns to be ignored, such as replication conflicts folders.

To set a pattern to be excluded:
  1. Using Windows Explorer, navigate to the node.config file.
  2. Open node.config and add any require patterns to the excludepathpatterns property. Patterns should be comma-separated and are not case-sensitive.
/Replication Conflicts/ is added to the excludepathpatterns property by default when the node.cofig is generated using the Invoke-S2IXDatabaseUpgrade command.

Legacy RMR Processing

On a Node operating in Legacy mode, the RMR requests will still be generated and sent to the updated T0 Node. However, the T0 will not send the item to the Records Management System, and the status will immediately be set to Completed.  A message stating the item was excluded and the reason, is set on the Data field of the RMR request list item.


Note

The legacy RMR items path field includes the site managed path and filename.

For example, '/sites/hmasinvincible/shipsdocuments/Engineering/Authorisations/Replication Conflicts/TestFile.txt'

 

Modern RMR Processing

A RMR request for the item will not be created in SQL when it's "path" + "filename" matches one of the specified patterns.

Note

The modern RMR items path and filename includes the site title (not managed path)

For example,  '/HMAS Invincible/shipsdocuments/Engineering/Authorisations/Replication Conflicts/TestFile.txt'