Feedback
Redact validation workflow
The Redact validation workflow prevents production issues with markups on native spreadsheet and PDF documents. The workflow runs in the background on any eligible spreadsheet or PDF documents to prevent interruptions. The Redact validation workflow alerts users early on about issues they may experience while applying markups. The Redact validation workflow does not apply to images.
When a document that cannot be redacted is identified by the validation workflow, two choices are applied to the Redact Document Warnings field: Caught by Validation Workflow and Cannot be Redacted in Native Viewer. The Cannot be Redacted in the Native Viewer value automatically adds the document to the Redact External Markups tab. The Caught by Validation Workflow value is informational.
Here are the steps in the Redact validation workflow:
- All native files are checked for compatibility during the initial document preparation process.
- Whenever a user applies a new markup on a native document or when a Redact markup project is run, the native file is flagged so that the markup can be checked for compatibility during off-hours according to your region. Off-hours are configured per-tenant and region.
- If an incompatible markup is identified, the native file is populated with the Cannot be Redacted in Native Viewer choice on the Redact Document Warnings field. The Redact Document Warnings field can be added to a layout so that you can see this information while reviewing documents.
- Any document that cannot receive markups should go through an external markup workflow. The native spreadsheet or PDF file can be accessed on the Redact External Markups tab. You can then download the file, apply markups in the native application, and re-upload it to Relativity.
