Document generation flows in Create

TABLE OF CONTENTS

• Document generation flows in Create Classic
• Start creation from an app
• Start creation from Word
• Document editing
• Updating data post-generation

Document generation flows in Create Classic

The flow that the users go through to generate documents in Create Classic

Document generation in Create Classic can be triggered either from a third-party app or from Microsoft Word. Any system that can transmit data over the internet can communicate with Create Classic. For some examples, head over to our Documotor Integrations page - Create Classic has been designed to integrate with similar systems.

Create Classic supports both online and on-premise versions of Word, with only minor differences.

Start creation from an app

Document creation from a third-party app is usually the most natural way for Create Classic to be a part of a document flow. A Generate document button or a template selection widget is added to an app and an integration is built between the app and Create Classic. This is the flow that the user experiences:

1. The user selects the Generate document button or a selects a template from the app.
2. A separate window opens with the user site of Omnidocs Create Classic.
3. The user selects a template from the Create Classic user site. When the template is selected, a preview of the document with the data forwarded from the app is shown, and the user has an opportunity to adjust the data.
4. The user creates the document. It is then either returned to the requesting application for editing, or an editing flow is initiated by Create Classic, opening the document in Word Online. Editing is discussed in more detail below, under Document editing.

Start creation from Word

The user flow can also be initiated from Microsoft Word. It's supported in both the online and the on-premises versions of Microsoft Word.

1. The user opens Microsoft Word.
2. The user starts the Omnidocs Create Classic add-in that opens in a side pane, with the same functionality as the Omnidocs Create Classic user site.
3. The user selects the template.
4. The user or the API provides data to populate the template. The preview of the template filled out with the provided data is shown.
5. When the user selects Create Classic, the document is created and saved.
6. The document can be saved to a predetermined location, or the user can choose where it should be saved. Saving to external systems is supported.

Document editing

Editing flows can be performed both online and on-premises. If your application doesn't support online editing itself, the Create Classic editing flow can invoke Word Online to put finishing touches on created documents.

The on-premise solution doesn't require downloading and reuploading documents each time an edit is made. A solution that enables the user to edit the document in their on-premise application and save it to their systems without leaving a copy on the local drive.

Updating data post-generation

Create Classic supports updating the data that's been provided to a document, even after the document is generated. This is supported both in Word Online and on-premise, but the options have to be decided on before implementation, because it results in a higher complexity.