PDF4me icon

PDF4me

Comprehensive PDF and document processing: generate barcodes, convert files, extract data, manipulate images, and automate workflows with the PDF4ME API

Actions80

Overview

This node operation enables the "Track Changes" feature in a Microsoft Word document. It processes a Word document input and outputs a new Word document with change tracking activated. This is useful when you want to monitor edits made to a document, such as during collaborative editing or review cycles.

Practical examples include:

  • Automatically enabling change tracking on documents before sending them for review.
  • Processing batches of Word files to prepare them for collaborative editing workflows.
  • Integrating with document management systems to ensure all edited documents have tracking enabled.

Properties

Name Meaning
Input Data Type How the Word document is provided:
- Binary Data (from previous node)
- Base64 String
- URL
Input Binary Field The name of the binary property containing the Word document (used if Input Data Type is Binary Data). Usually "data".
Base64 Word Content Base64 encoded content of the Word document (used if Input Data Type is Base64 String).
Word Document URL URL pointing to the Word document to process (used if Input Data Type is URL).
Output File Name Desired file name for the output Word document with tracking enabled. Defaults to "tracking_enabled_output.docx".
Async Whether to process the operation asynchronously (true/false).
Binary Data Output Name Custom name for the binary data field in the node's output. Defaults to "data".

Output

The node outputs the processed Word document with change tracking enabled. The output includes:

  • A JSON object per input item.
  • A binary data field containing the Word document file data, named according to the "Binary Data Output Name" property (default "data").
  • The binary data represents the Word document file (.docx) ready for download or further processing.

No additional JSON fields are specified beyond the binary file output.

Dependencies

  • Requires access to the Word document either as binary data, base64 string, or via a URL.
  • No explicit external API keys or services are indicated in the source code snippet.
  • The node likely depends on an internal or bundled library capable of manipulating Word documents to enable tracking changes.
  • If URLs are used, network access must be available to fetch the document.

Troubleshooting

  • Common issues:

    • Providing an invalid or inaccessible URL will cause failure to fetch the document.
    • Incorrect binary property name may result in missing input data.
    • Invalid base64 content will cause decoding errors.
    • Output file name conflicts or invalid characters might cause downstream issues.

  • Error messages:

    • Errors related to fetching or reading the input document usually indicate incorrect input parameters.
    • Processing errors may occur if the document format is unsupported or corrupted.

  • Resolutions:

    • Verify the input data type matches the provided input.
    • Ensure URLs are accessible and point directly to valid Word documents.
    • Confirm base64 strings are correctly encoded.
    • Use default or safe file names for output.

Links and References

This summary is based solely on static analysis of the provided source code and property definitions.

Discussion