Give users a useful next step after previewing a document
Opening a document is often the beginning of a task. A customer may need a PDF copy of a proposal, an operations team may need data from a spreadsheet, or a project portal may need an image preview of a presentation.
The Doconut Converter Plugin helps developers add those conversion steps to their own .NET applications. It extends the Doconut product family with document conversion, connecting file viewing with the output a workflow needs next.
For readers exploring document tools through Doconut.app, Doconut.com is the place to evaluate the SDK and plugins for an embedded application workflow.
Match each conversion to a user task
Doconut's product page lists conversion routes for PDF, Word, Excel, PowerPoint, email, images, and CAD files. Some practical starting points are:
| Source and output | Example application workflow |
|---|---|
| Word to PDF | Prepare a proposal for review and download. |
| Excel to CSV | Export spreadsheet data for a downstream process. |
| PowerPoint to PNG or JPG | Create slide images for a project workspace. |
| PDF to DOCX | Produce an editable starting point for further work. |
| DWG to PDF | Make a drawing available in a document-review packet. |
These examples use the published Converter format combinations. They are not a promise that every file can be converted into every target format.
Choose the output according to what must survive the transformation. A CSV export serves a different purpose from a formatted workbook. An image of a slide is useful for display, but does not retain editable presentation objects. Make that distinction clear when naming export actions.
Offer only the formats available for the source
A single menu containing every possible format can frustrate users when some selections are unavailable for their file.
The Converter integration documentation describes a source-specific list of allowed targets returned when a file is opened through the conversion widget's workflow. A custom interface can use that information to show relevant choices.
For example, a portal might present a short export menu after the user opens an attachment. The application can explain the intended use of each option, then show progress and a clear download action. Preserve the original filename in the interface so that the user can tell which source produced the result.
The goal is a predictable task: choose a source, select an available output, convert, and retrieve the result.
Choose the integration that suits your product
The documentation describes conversion from C#, an optional conversion widget, and an HTTP workflow for a custom frontend. This gives teams several ways to introduce the feature:
- Use server-side conversion within an existing application process.
- Evaluate the provided widget for a user-driven conversion screen.
- Build an interface that matches an established portal or document-management system.
Follow the guide for your target framework when installing and registering the plugin. Confirm the required license capability and align the plugin package version with the Doconut viewer package.
For a first implementation, select one valuable conversion route. A small document-to-PDF workflow is easier to evaluate than a large menu whose outputs have not yet been reviewed.
Test the result your users will receive
A successful conversion request is only one part of acceptance. Open the generated file and compare the details relevant to its intended use.
For a proposal, check headings, tables, and page breaks. For a spreadsheet export, check the records and values expected by the receiving process. For a drawing, inspect line work and legibility at the size users will view or print.
Use Doconut's supported file catalog to check accepted source extensions, and test representative files from your own workflow. Include a larger document and an unsupported input so that progress and error messages receive attention too.
Measure processing time and resource use in the application environment where conversion will run. Set appropriate request limits and decide how the application handles a retry or an unavailable result. Your storage, access controls, and retention rules remain part of that application design.
Add conversion where it earns its place
A useful export action sits close to the document and explains what the user will receive. Doconut Converter provides the conversion capability; your application gives that capability a purpose in the workflow.
Explore the Doconut Converter Plugin for the available conversions and licensing options. Start with one source format, one useful output, and a representative set of documents, then expand as the integration proves itself.