Select Page

October 2022 Release: Improvements for Document Automation & New API

October 2022 Release: Improvements for Document Automation & New API

1) Page Number Element

We added a new Page Number Element that can be inserted into the Headers and Footers of your automated Templates. The benefit of using this over page numbering as part of an Advanced Layout Design is that a Page Number Element can be conditional, so based on the user’s choice, there can be different page numbering, or the page numbering can be added or removed.

You can define all standard numberings, including the sum of all pages and can continue the numbering from the previous Next Page Section.

All standard Element formatting options are also available in the Page Number Element.

There can be multiple Page Number Elements contained in each Next Page Section.

2) Restrictions in the format of exported documents

It is possible to select which formats a Legito Document from a specific Template can be exported.

To restrict formats, go to the Template Administration Area and select the permitted formats for the Template in the left bar. All formats are permitted by default. If at least one format is selected, the formats that are not selected will be restricted.

If any format is restricted, it does not matter that a user is allowed to export documents in such a format according to the user permissions. If any format is restricted here, the user will not be permitted to export documents in the restricted format(s) regardless of their user permissions.

These settings do not affect the triggering of the signing process from Legito – the document will always export as a PDF for the purposes of electronic signature.

3) REST API v6

A new version of our REST API was released that contains a new endpoint POST /document-version/json-integration that supports the new JSON Integrations feature and enhancements for the following endpoints:

POST /document-version/data/{templateSuiteId}

New query parameters:

  • favoriteSettingId – If Favorite Setting ID parameter is not specified, the document will be created with the default Favorite Setting or with no Favorite Setting if the default Favorite Setting is does not exist in Template Suite.
  • authorId – User ID of author (and owner if not specified) that will be assigned to the created Document Version and Document Record. The Default API user will be assigned if not specified
  • ownerId – User ID of owner that will be assigned to the created Document Version and Document Record. The Default API user will be assigned if not specified

GET /document-version/data/{code}

PUT /document-version/data/{code}

POST /document-version/data/{templateSuiteId}

Added new Element Types to body / response of requests:

  • ObjectRecordsSelectbox
  • ObjectLink
  • HyperLink
  • Question
  • ObjectRecordsQuestion
  • RichText
  • RepeatContainer
  • TableOfContents
  • Switcher

Added new attributes to Template Elements

  • Uuid – ID that is not changed if a new revision of Template is created.
  • isRepeated
  • repeatIdentifier – Can be used to identify a specific repeated Element and filled by this Identifier

GET /file/{documentRecordCode}

Added new attributes to File response

  • signAdobesigned
  • signFlowsigned
  • signLegitosigned

GET /template-suite

Added new attributes to Template Suite response

  • templates – List of Template information about each Template in Template Suite
  • favoriteSettings – List of Favorite Settings created in Template Suite
  • categories – List of Category IDs assigned to Template Suite

GET /user/permission/{userIdOrEmail}

POST /user/permission/{userIdOrEmail}

Added new User Permissions

  • draftTemplates
  • templateSuitesAll
  • templateSuitesList
  • templateSuitesCategoriesAll
  • templateSuitesCategoriesList
  • templateSuitesCountriesAll
  • templateSuitesCountriesList
  • createTemplateSuite
  • createLabel
  • manageStyles
  • manageObjects
  • manageJsonIntegration
  • manageLegitoSign
  • signAdobeSign:
  • signFlowSign
  • signLegitoSign
  • objectsAll
  • objectsList

Removed obsolete User Permissions

  • viewTemplatesAll
  • viewTemplatesList
  • viewTemplatesGroupAll
  • viewTemplatesGroupList
  • viewTemplatesCountryAll
  • viewTemplatesCountryList
  • manageList

Documentation to this REST API version is available at https://app.swaggerhub.com/apis-docs/Legito/legito-api/6.

4) New formatting options for Template Elements

Positioning and wrapping for Images

We enhanced the Layout Options for Image Elements. It is possible to select several text wrapping, image position, and distance from text options. This setting is applicable to exported Word and PDF documents only.

Background color for Non-exporting Clauses

You can select a background color and other Clause formatting options for Clauses that are marked as non exportable.

 

New options for Line spacings

We added the following new options for Line spacing: At least, Exactly, and Multiple.

You can now select the option “Don’t add space between paragraphs of the same style.”

This setting is applicable to exported Word and PDF documents only.

Optional empty lines before and after Tables

It is possible to choose if these shall, or shall not be hard returned before or after a Table. This setting is applicable to exported Word and PDF documents only.

5) Print Preview

Legito Documents are automatically modified in real time according to a user’s choices, but if you would like to see the exact layout of the documents as they will appear when exported to Word or PDF, you can use our new Print Preview feature that is included in the secondary actions dropdown in the Document Menu Bar. 

Print Preview is available after the first draft of a Legito Document is saved from a Template.

6) Search for dropdowns in Template Editor

We added search boxes to multiple dropdowns in the Template Editor to help you automate your documents even more efficiently.

October 2022 Release: Improvements for Document Automation & New API

1) Page Number Element

 

We added a new Page Number Element that can be inserted into the Headers and Footers of your automated Templates. The benefit of using this over page numbering as part of an Advanced Layout Design is that a Page Number Element can be conditional, so based on the user’s choice, there can be different page numbering, or the page numbering can be added or removed.

You can define all standard numberings, including the sum of all pages and can continue the numbering from the previous Next Page Section.

All standard Element formatting options are also available in the Page Number Element.

There can be multiple Page Number Elements contained in each Next Page Section.

2) Restrictions in the format of exported documents

 

It is possible to select which formats a Legito Document from a specific Template can be exported.

To restrict formats, go to the Template Administration Area and select the permitted formats for the Template in the left bar. All formats are permitted by default. If at least one format is selected, the formats that are not selected will be restricted.

If any format is restricted, it does not matter that a user is allowed to export documents in such a format according to the user permissions. If any format is restricted here, the user will not be permitted to export documents in the restricted format(s) regardless of their user permissions.

These settings do not affect the triggering of the signing process from Legito – the document will always export as a PDF for the purposes of electronic signature.

3) REST API v6

 

A new version of our REST API was released that contains a new endpoint POST /document-version/json-integration that supports the new JSON Integrations feature and enhancements for the following endpoints:

POST /document-version/data/{templateSuiteId}

New query parameters:

  • favoriteSettingId – If Favorite Setting ID parameter is not specified, the document will be created with the default Favorite Setting or with no Favorite Setting if the default Favorite Setting is does not exist in Template Suite.
  • authorId – User ID of author (and owner if not specified) that will be assigned to the created Document Version and Document Record. The Default API user will be assigned if not specified
  • ownerId – User ID of owner that will be assigned to the created Document Version and Document Record. The Default API user will be assigned if not specified

GET /document-version/data/{code}
PUT /document-version/data/{code}
POST /document-version/data/{templateSuiteId}

Added new Element Types to body / response of requests:

  • ObjectRecordsSelectbox
  • ObjectLink
  • HyperLink
  • Question
  • ObjectRecordsQuestion
  • RichText
  • RepeatContainer
  • TableOfContents
  • Switcher

Added new attributes to Template Elements

  • Uuid – ID that is not changed if a new revision of Template is created.
  • isRepeated
  • repeatIdentifier – Can be used to identify a specific repeated Element and filled by this Identifier

GET /file/{documentRecordCode}

Added new attributes to File response

  • signAdobesigned
  • signFlowsigned
  • signLegitosigned

GET /template-suite

Added new attributes to Template Suite response

  • templates – List of Template information about each Template in Template Suite
  • favoriteSettings – List of Favorite Settings created in Template Suite
  • categories – List of Category IDs assigned to Template Suite

GET /user/permission/{userIdOrEmail}
POST /user/permission/{userIdOrEmail}

Added new User Permissions

  • draftTemplates
  • templateSuitesAll
  • templateSuitesList
  • templateSuitesCategoriesAll
  • templateSuitesCategoriesList
  • templateSuitesCountriesAll
  • templateSuitesCountriesList
  • createTemplateSuite
  • createLabel
  • manageStyles
  • manageObjects
  • manageJsonIntegration
  • manageLegitoSign
  • signAdobeSign:
  • signFlowSign
  • signLegitoSign
  • objectsAll
  • objectsList

Removed obsolete User Permissions

  • viewTemplatesAll
  • viewTemplatesList
  • viewTemplatesGroupAll
  • viewTemplatesGroupList
  • viewTemplatesCountryAll
  • viewTemplatesCountryList
  • manageList

Documentation to this REST API version is available at https://app.swaggerhub.com/apis-docs/Legito/legito-api/6.

4) New formatting options for Template Elements

 

 

Positioning and wrapping for Images

We enhanced the Layout Options for Image Elements. It is possible to select several text wrapping, image position, and distance from text options. This setting is applicable to exported Word and PDF documents only.

Background color for Non-exporting Clauses

You can select a background color and other Clause formatting options for Clauses that are marked as non exportable.

 

New options for Line spacings

We added the following new options for Line spacing: At least, Exactly, and Multiple.

You can now select the option “Don’t add space between paragraphs of the same style.”

This setting is applicable to exported Word and PDF documents only.

Optional empty lines before and after Tables

It is possible to choose if these shall, or shall not be hard returned before or after a Table. This setting is applicable to exported Word and PDF documents only.

 

5) Print Preview

Legito Documents are automatically modified in real time according to a user’s choices, but if you would like to see the exact layout of the documents as they will appear when exported to Word or PDF, you can use our new Print Preview feature that is included in the secondary actions dropdown in the Document Menu Bar. 

Print Preview is available after the first draft of a Legito Document is saved from a Template.

6) Search for dropdowns in Template Editor

We added search boxes to multiple dropdowns in the Template Editor to help you automate your documents even more efficiently.

More From New Releases

September 2022 Release: Clause Library & No Code JSON Integration

September 2022 Release: Clause Library & No Code JSON Integration

1) Clause Library

After several months of hard work, we are thrilled to announce that we have released the highly awaited Clause Library that can automatically update a clause in multiple templates from one place.

Managing auto-updated Clauses

Legito Workspace has a new Clause Library area accessible from the top bar. Permissioned users can add, remove or edit Clauses here.

This area has a similar look and feel to the Templates area.

Clauses in the Clause Library can be divided into Categories that are editable in the “Templates & Docs Grouping” section in the Workspace Settings.

 

 

Name, Categories, and Country of a Clause can be edited in the Clause Properties.

 

The content of a Clause can be edited in the Template Editor, similar to the way you can edit the content of standard Templates, including Draft and Public versions.

Inserting Clauses from the Clause Library into Templates

There is a new “Library” tab in the Template Editor’s left bar.

All Clauses from the Clause Library are listed in this tab, and users can drag & drop them into Templates.

Clause Library Clauses cannot be inserted into any other Clauses.

Users working on a Template in the Document Editor will see no difference between content from the Clause Library and other content in that particular Template.

Except for in Test mode, when a user creates the first draft of a Document from a Template, the latest published version of Clauses will be loaded into the Template every time a user opens the Document Editor. 

User Permissions

Similar to the User Permissions of Template Suites, it’s possible to define which Clauses, Clause Categories, and Countries can be accessed by which users.

Workspace Admins automatically have access to the Clause Library and all its Clauses.

Limitations

Sections cannot be used within Clause Library Clauses.

Do not insert a Table of Contents (ToC) to a Clause Library Clause if a ToC Element is already utilized in another part of a Template.

This feature is currently in the open beta version.

2) Dynamic Insertion of Clauses from the Clause Library

In some advanced cases, you might want to dynamically select a clause from a pool of Clause Library Clauses to be added to a document based on a certain value, as creating a new condition for each of the Clause Library Clauses would be too time-consuming. This new Dynamic Clause element was designed to cover such a use case.

The Dynamic Clause element works similarly to a Link, in the way that a user has to link the element to a value of another element in the Template Suite or a JSON Object (see the JSON Integration feature below). 

If the name of a Clause from the Clause Library matches the value from a selected element or JSON Object, the Clause will be inserted to your Document. It is possible to choose if the match should be an Exact Match, Contains, Start with or Ends with as well as filter only the Clauses from a selected Category of Clause Library.

3) Conditions, Links, and Repeats to and from Clause Library Clauses

We added the “any Template Suite content” type of Condition, Link, and Repeat that will allow you to build logical dependencies between content inserted directly to a Template and content in a Clause from the Clause Library. However, it is not limited to the Clause Library use case. It can be used to refer to any Element or Clause in your Template Suite. 

This new type requires a user to insert the System Name as well as the value manually. It is possible to choose from Numerical, Text, and Generic (is present/is not present) operators.

 

4) No Code JSON Integrations

The new JSON Integrations feature exponentially increases the integration capabilities between Legito and any third-party software.

With the JSON Integrations feature, it is possible to create new Documents from Templates based on data from received JSON files with no coding required. 

 

JSON Integrations Administration

Your Workspace can have multiple JSON Integrations.

Users can manage JSON Integrations in the JSON Integrations section of the Workspace Settings area.

New JSON Integration can be added by clicking on the Create button in the upper right corner.

Before a JSON Integration is created, the user has to insert at least the name, upload an example JSON file for the purposes of the no code JSON Integration Editor, and select the Template Suite from which a Document (or Document Bundle) shall be created. It is also possible to insert a description of the integration and upload an additional JSON file for triggering the integration (explained below). 

 

JSON Integration Editor

JSON Integration Editor opens when a user clicks the Edit button in the administration.

The JSON Integration Editor is similar to the Workflow Editor. The content of the example of a JSON file is displayed in the main area. The right bar contains either JSON Integration settings or JSON Object settings.

JSON Integration settings

  • Integration Trigger
  • Assigned Template Suites and their triggers
  • Versioning

JSON Object settings

  • Matching the JSON Object to an Element or Document Settings
  • Data Transformations of the JSON Object when used in a Template Suite
  • Filtering of sub-objects (array) for the purposes of a Template Suite
  • Ordering of sub-objects (array) for the purposes of a Template Suite
  • Application of the JSON Object in a Template Editor


Versions

Similar to other Legito areas such as Workflows, Templates, or Scripts, each JSON Integration contains two types of versions: (a) Drafts that are available only for purposes of testing, and (b) Published version that are used for common creation of Documents from Templates. Draft version is created when a user clicks the Save button. Published versions are created when a user clicks the Publish button.

It is also possible to go back to any previous version.

 

Conditional Triggering of a JSON Integration

Each JSON Integration has 3 ways to identify if that JSON Integration will be used when the Workspace receives a JSON file:

  • String – JSON Integration will be used if the JSON file contains a defined unique string

  • Conditions – For more complex use cases, it is possible to define a condition based on the content of a received JSON file and if the condition is met, the JSON Integration will be used

  • None – In this case, the ID of the JSON Integration has to be contained in the REST API call (details below)

Matching JSON Objects and Template Elements

Similar to Import from a Sheet and Import from a Legito Document, it is possible to match each JSON Object to an Element in the assigned Template Suite to populate the a value from a JSON file to the content of a Template.

Additionally, it is possible to set other Document Settings such as an Owner according to a value of the JSON Object.

Matching arrays from JSON with repeated content of Templates

Tick the checkbox “Use in repeated content” to populate values from arrays in the JSON file to repeated Elements and Clauses in the assigned Template Suite. Values from instances in such an array will be then populated to instances of the released Clauses or Elements. For example, the first instance of the array will be populated in the first repeated Clause, the second instance to the second Clause and so on. 

Filtering

It is possible to filter instances of an array in the JSON file and populate only the instances that meet the filtering criteria.

Sorting

It is possible to reorder instances of an array according to a selected attribute, either ascending or descending.

Data Transformations

Advanced use cases may require a transformation of data from JSON before they are inserted into Templates. The JSON Integration Editor contains several types of popular data transformations, for example, transforming a URL address to an image that is placed on the URL address and inserting an image to the Document instead of a URL address. 

Connecting JSON Integration with multiple Template Suites

It is also possible to assign multiple Template Suites to one JSON Integration.

In case there are at least 2 Templates Suites assigned to the same JSON Integration, users have to set conditional logic to determine which of the Templates Suites will be used. Only one Template Suite can be triggered from one JSON file. Features described in the “Conditional Triggering of a JSON Integration” section above are also applicable for triggering Template Suites.

Other JSON Editor Features

Search within the content of the example JSON file uploaded to the JSON Integration.

Undo and Redo actions in the Template Editor.

Auto-matching of JSON Objects and Template Suite Elements based on an exact match between the name of the objects and the System Name of Elements.

The JSON file for triggering a JSON Integration may be used in addition to the JSON file for populating content in your Template Suites. This feature is useful when the main JSON file is too large and the use case requires a quick response time.

REST API

JSON files will be sent to Legito using our REST API (supported from version 6). Please contact us for early access to the REST API v6.

This feature is currently in the beta stage. 

Limitations

This feature is currently in the open beta version.

Too large JSON files – if there are a lot of JSON Integrations and the Integration ID is not contained in the REST API call.

5) Conditions and Links referring to a JSON File

We added new types of Conditions and Links to the Template Editor that will allow Template authors to set Conditions and Links directly based on the values of the received JSON file.

 

Only JSON Objects with the activated “Use in Template Editor” checkbox can be referred to in Conditions and Repeats.

 

We will roll out this update on each of Legito’s server locations in the upcoming days.

September 2022 Release: Clause Library & No Code JSON Integration

1) Clause Library

After several months of hard work, we are thrilled to announce that we have released the highly awaited Clause Library that can automatically update a clause in multiple templates from one place.

Managing auto-updated Clauses

Legito Workspace has a new Clause Library area accessible from the top bar. Permissioned users can add, remove or edit Clauses here.

This area has a similar look and feel to the Templates area.

Clauses in the Clause Library can be divided into Categories that are editable in the “Templates & Docs Grouping” section in the Workspace Settings.

Name, Categories, and Country of a Clause can be edited in the Clause Properties.

The content of a Clause can be edited in the Template Editor, similar to the way you can edit the content of standard Templates, including Draft and Public versions.

Inserting Clauses from the Clause Library into Templates

There is a new “Library” tab in the Template Editor’s left bar.

All Clauses from the Clause Library are listed in this tab, and users can drag & drop them into Templates.

Clause Library Clauses cannot be inserted into any other Clauses.

Users working on a Template in the Document Editor will see no difference between content from the Clause Library and other content in that particular Template.

Except for in Test mode, when a user creates the first draft of a Document from a Template, the latest published version of Clauses will be loaded into the Template every time a user opens the Document Editor. 

User Permissions

Similar to the User Permissions of Template Suites, it’s possible to define which Clauses, Clause Categories, and Countries can be accessed by which users.

Workspace Admins automatically have access to the Clause Library and all its Clauses.

Limitations

Sections cannot be used within Clause Library Clauses.

Do not insert a Table of Contents (ToC) to a Clause Library Clause if a ToC Element is already utilized in another part of a Template.

This feature is currently in the open beta version.

2) Dynamic Insertion of Clauses from the Clause Library

In some advanced cases, you might want to dynamically select a clause from a pool of Clause Library Clauses to be added to a document based on a certain value, as creating a new condition for each of the Clause Library Clauses would be too time-consuming. This new Dynamic Clause element was designed to cover such a use case.

The Dynamic Clause element works similarly to a Link, in the way that a user has to link the element to a value of another element in the Template Suite or a JSON Object (see the JSON Integration feature below). 

If the name of a Clause from the Clause Library matches the value from a selected element or JSON Object, the Clause will be inserted to your Document. It is possible to choose if the match should be an Exact Match, Contains, Start with or Ends with as well as filter only the Clauses from a selected Category of Clause Library.

3) Conditions, Links, and Repeats to and from Clause Library Clauses

We added the “any Template Suite content” type of Condition, Link, and Repeat that will allow you to build logical dependencies between content inserted directly to a Template and content in a Clause from the Clause Library. However, it is not limited to the Clause Library use case. It can be used to refer to any Element or Clause in your Template Suite. 

This new type requires a user to insert the System Name as well as the value manually. It is possible to choose from Numerical, Text, and Generic (is present/is not present) operators.

4) No Code JSON Integrations

The new JSON Integrations feature exponentially increases the integration capabilities between Legito and any third-party software.

With the JSON Integrations feature, it is possible to create new Documents from Templates based on data from received JSON files with no coding required.  

JSON Integrations Administration

Your Workspace can have multiple JSON Integrations.

Users can manage JSON Integrations in the JSON Integrations section of the Workspace Settings area.

New JSON Integration can be added by clicking on the Create button in the upper right corner.

Before a JSON Integration is created, the user has to insert at least the name, upload an example JSON file for the purposes of the no code JSON Integration Editor, and select the Template Suite from which a Document (or Document Bundle) shall be created. It is also possible to insert a description of the integration and upload an additional JSON file for triggering the integration (explained below). 

JSON Integration Editor

JSON Integration Editor opens when a user clicks the Edit button in the administration.

The JSON Integration Editor is similar to the Workflow Editor. The content of the example of a JSON file is displayed in the main area. The right bar contains either JSON Integration settings or JSON Object settings.

JSON Integration settings

  • Integration Trigger
  • Assigned Template Suites and their triggers
  • Versioning

JSON Object settings

  • Matching the JSON Object to an Element or Document Settings
  • Data Transformations of the JSON Object when used in a Template Suite
  • Filtering of sub-objects (array) for the purposes of a Template Suite
  • Ordering of sub-objects (array) for the purposes of a Template Suite
  • Application of the JSON Object in a Template Editor

Versions

Similar to other Legito areas such as Workflows, Templates, or Scripts, each JSON Integration contains two types of versions: (a) Drafts that are available only for purposes of testing, and (b) Published version that are used for common creation of Documents from Templates. Draft version is created when a user clicks the Save button. Published versions are created when a user clicks the Publish button.

It is also possible to go back to any previous version.

Conditional Triggering of a JSON Integration

Each JSON Integration has 3 ways to identify if that JSON Integration will be used when the Workspace receives a JSON file:

  • String – JSON Integration will be used if the JSON file contains a defined unique string

  • Conditions – For more complex use cases, it is possible to define a condition based on the content of a received JSON file and if the condition is met, the JSON Integration will be used

  • None – In this case, the ID of the JSON Integration has to be contained in the REST API call (details below)

Matching JSON Objects and Template Elements

Similar to Import from a Sheet and Import from a Legito Document, it is possible to match each JSON Object to an Element in the assigned Template Suite to populate the a value from a JSON file to the content of a Template.

Additionally, it is possible to set other Document Settings such as an Owner according to a value of the JSON Object.
 

Matching arrays from JSON with repeated content of Templates

Tick the checkbox “Use in repeated content” to populate values from arrays in the JSON file to repeated Elements and Clauses in the assigned Template Suite. Values from instances in such an array will be then populated to instances of the released Clauses or Elements. For example, the first instance of the array will be populated in the first repeated Clause, the second instance to the second Clause and so on. 

Filtering

It is possible to filter instances of an array in the JSON file and populate only the instances that meet the filtering criteria.

Sorting

It is possible to reorder instances of an array according to a selected attribute, either ascending or descending.

Data Transformations

Advanced use cases may require a transformation of data from JSON before they are inserted into Templates. The JSON Integration Editor contains several types of popular data transformations, for example, transforming a URL address to an image that is placed on the URL address and inserting an image to the Document instead of a URL address. 

Connecting JSON Integration with multiple Template Suites

It is also possible to assign multiple Template Suites to one JSON Integration.

In case there are at least 2 Templates Suites assigned to the same JSON Integration, users have to set conditional logic to determine which of the Templates Suites will be used. Only one Template Suite can be triggered from one JSON file. Features described in the “Conditional Triggering of a JSON Integration” section above are also applicable for triggering Template Suites.

Other JSON Editor Features

Search within the content of the example JSON file uploaded to the JSON Integration.

Undo and Redo actions in the Template Editor.

Auto-matching of JSON Objects and Template Suite Elements based on an exact match between the name of the objects and the System Name of Elements.

The JSON file for triggering a JSON Integration may be used in addition to the JSON file for populating content in your Template Suites. This feature is useful when the main JSON file is too large and the use case requires a quick response time.

REST API

JSON files will be sent to Legito using our REST API (supported from version 6). Please contact us for early access to the REST API v6.

This feature is currently in the beta stage. 

Limitations

This feature is currently in the open beta version.

Too large JSON files – if there are a lot of JSON Integrations and the Integration ID is not contained in the REST API call.

5) Conditions and Links referring to a JSON File

We added new types of Conditions and Links to the Template Editor that will allow Template authors to set Conditions and Links directly based on the values of the received JSON file.

Only JSON Objects with the activated “Use in Template Editor” checkbox can be referred to in Conditions and Repeats.

We will roll out this update on each of Legito’s server locations in the upcoming days.

More From New Releases

August 2022 Release: Sections and More

August 2022 Release: Sections and More

1) Sections (beta)

Legito Templates now contain multiple Sections, similar to sections you will recognize from MS Word or Google Docs documents.

There are 2 types of sections:

  • Next Page Sections
  • Continuous Sections

It is possible to attach conditions to the Sections (in other words, created conditioned Sections) as well as create repeated Sections. If a Section is conditioned and the condition is not met, the entire Section (including its content) is removed from the document.

It is also possible to Tag a Section.

In the case of dual language documents, it is possible to set a Section to ignore the second language.

Next Page Sections

A Next page Section can be added by clicking the button underneath the last Next Page Section in the Template Editor.

Each Template has to contain at least one Next Page Section.

Each Next Page Section contains a Header and Footer.

Continuous Sections

Continuous Sections can be inserted into Next Page Sections from the left menu. Continuous Sections cannot be inserted into Clauses.

Any Clause or Element can be inserted into a Continuous Section, the same way you insert them into a Next Page Section.

This feature is currently available in beta. Please be aware that there might be some breaking changes and some functionality that is not supported yet, for example, using multiple Sections in the Legito Templates in combination with Advanced Layout Designs. 

2) Page Size, Orientation, Margins, and Columns

We enhanced the formatting options of Legito Templates in connection with the Section above.

The formatting is visible (applicable) for exported Word and PDF documents only.

Page Size

It is possible to choose page size for each Next Page Section.

Page Orientation

A Next Page Section can have either portrait (default) or landscape page orientation.

Page Margins

You may set left, right, top, and bottom margins in a Next Page Section.

Columns

Each Next Page and Continuous Section can be split into multiple columns.

It is not necessary to use Advanced Layout Designs if you need to set the above mentioned formatting.

Since Sections are still in Beta version mode, it may also affect the formatting.

3) New Line Before or After an Element

So far, it was possible to define if there should or should not be a space between two Elements. We enhanced this settings and from now on, you can also set if the Element or the following one shall start on a new line. 

This setting does not affect any logic of your Template (contions, repeats, etc.) since the Elements are still in the same Clause.

4) Template Suite Permissions

User Permissions to Template Suites has been upgraded to make it  possible to define in each Template Suite if the given User can only use it (to generate documents), or use and edit(edit content, logic, and settings of the Template Suite and its Templates, including saving and publishing new versions).

We have also transformed the “Can draft Templates” permission into “Can create new Template Suites”. This permission gives Users the ability to create a new Template Suite and edit the newly created Template Suite.

This change will be reflected in the next version of our REST API (version 6) that will be released in about a month. It is not necessary to change your integrations with the currently released and supported REST API version.

5) NetDocuments integration (beta)

It is possible to directly upload Legito generated Word or PDF documents to your NetDocuments account.

Please contact our Helpdesk for more information and to activate this integration.

August 2022 Release: Sections and More

1) Sections (beta)

Legito Templates now contain multiple Sections, similar to sections you will recognize from MS Word or Google Docs documents.

There are 2 types of sections:

  • Next Page Sections
  • Continuous Sections

It is possible to attach conditions to the Sections (in other words, created conditioned Sections) as well as create repeated Sections. If a Section is conditioned and the condition is not met, the entire Section (including its content) is removed from the document.

It is also possible to Tag a Section.

In the case of dual language documents, it is possible to set a Section to ignore the second language.

Next Page Sections

A Next page Section can be added by clicking the button underneath the last Next Page Section in the Template Editor.

Each Template has to contain at least one Next Page Section.

Each Next Page Section contains a Header and Footer.

Continuous Sections

Continuous Sections can be inserted into Next Page Sections from the left menu. Continuous Sections cannot be inserted into Clauses.

Any Clause or Element can be inserted into a Continuous Section, the same way you insert them into a Next Page Section.

This feature is currently available in beta. Please be aware that there might be some breaking changes and some functionality that is not supported yet, for example, using multiple Sections in the Legito Templates in combination with Advanced Layout Designs. 

2) Page Size, Orientation, Margins, and Columns

We enhanced the formatting options of Legito Templates in connection with the Section above.

The formatting is visible (applicable) for exported Word and PDF documents only.

Page Size

It is possible to choose page size for each Next Page Section.

Page Orientation

A Next Page Section can have either portrait (default) or landscape page orientation.

Page Margins

You may set left, right, top, and bottom margins in a Next Page Section.

Columns

Each Next Page and Continuous Section can be split into multiple columns.

It is not necessary to use Advanced Layout Designs if you need to set the above mentioned formatting.

Since Sections are still in Beta version mode, it may also affect the formatting.

3) New Line Before or After an Element

So far, it was possible to define if there should or should not be a space between two Elements. We enhanced this settings and from now on, you can also set if the Element or the following one shall start on a new line. 

This setting does not affect any logic of your Template (contions, repeats, etc.) since the Elements are still in the same Clause.

4) Template Suite Permissions

User Permissions to Template Suites has been upgraded to make it  possible to define in each Template Suite if the given User can only use it (to generate documents), or use and edit(edit content, logic, and settings of the Template Suite and its Templates, including saving and publishing new versions).

We have also transformed the “Can draft Templates” permission into “Can create new Template Suites”. This permission gives Users the ability to create a new Template Suite and edit the newly created Template Suite.

This change will be reflected in the next version of our REST API (version 6) that will be released in about a month. It is not necessary to change your integrations with the currently released and supported REST API version.

5) NetDocuments integration (beta)

It is possible to directly upload Legito generated Word or PDF documents to your NetDocuments account.

Please contact our Helpdesk for more information and to activate this integration.

More From New Releases

July 2022 Release: Focus on Advanced Features

July 2022 Release: Focus on Advanced Features

1) Rich Text Element​

Rich Text Element is an area in Your Template where you can create formatted text in the Template Editor as well as in the Document Editor. The goal is not to replace our standard Text and Text Input Elements that are essential for our “Documents as structured data” approach, but to provide our users with options to create formatted text without predefined limitations in parts of contracts and other documents that are always unique, and therefore cannot be automated such as technical schedules or description of work.

2) More options for Images

From now on, it is possible to set Image overlay in the Template Editor. This only applies to exported documents for now.

It is now possible to export documents from Legito with low resolution images in order to decrease file size.

3) Fixed Table Width

You can set a fixed width for Tables in the Template Editor.

4) Labels in the Template Editor

To improve the user experience for template authors, we added labels providing important information about Template Elements and Clauses, such as information about the System Name, Conditions, and Repeats.

Each user can widely customize the Labels. These settings apply to all Templates opened by the user.

5) Enhanced Permissions for Document & Object Record Properties

It is possible to define what permission level is needed to edit a Document or Object Record Property. The Property can be edited after a Document Record is created with the Edit permission to the Document Record, Manage permission to the Document Record, or a user has to be the Workspace Admin to be able to edit the value/content of the property which ensure that only the admin will be able to change the property value/content after the Document Record is created.

6) New Customizations for Document Records

You can now choose if Property Groups (and Properties inside them) will be situated on the right or left side.

7) New “Related Documents” Property

Document Records now contain a “Related Documents” Property where you can define a “tree” structure or related Document Records (documents).

8) Off-the-Shelf customizable Single-Sign On integration

To empower our enterprise customers, we have created an off-the-Shelf customizable Single-Sign On integration for the most common services such as Azure Active Directory.

This feature allows your admins to connect your user management service to Legito without any programming, including mapping of your SSO roles with permissions in your Legito Workspace.

To activate, please contact our Helpdesk and request a subdomain for your Workspace.

9) More Customizable User Experience

Workspace admins can choose for each of the major Workspace areas if it opens in the same browser window or in new tabs.

July 2022 Release: Focus on Advanced Features

1) Rich Text Element​

Rich Text Element is an area in Your Template where you can create formatted text in the Template Editor as well as in the Document Editor. The goal is not to replace our standard Text and Text Input Elements that are essential for our “Documents as structured data” approach, but to provide our users with options to create formatted text without predefined limitations in parts of contracts and other documents that are always unique, and therefore cannot be automated such as technical schedules or description of work.

2) More options for Images

From now on, it is possible to set Image overlay in the Template Editor. This only applies to exported documents for now.

It is now possible to export documents from Legito with low resolution images in order to decrease file size.

3) Fixed Table Width

You can set a fixed width for Tables in the Template Editor.

4) Labels in the Template Editor

To improve the user experience for template authors, we added labels providing important information about Template Elements and Clauses, such as information about the System Name, Conditions, and Repeats.

Each user can widely customize the Labels. These settings apply to all Templates opened by the user.

5) Enhanced Permissions for Document & Object Record Properties

It is possible to define what permission level is needed to edit a Document or Object Record Property. The Property can be edited after a Document Record is created with the Edit permission to the Document Record, Manage permission to the Document Record, or a user has to be the Workspace Admin to be able to edit the value/content of the property which ensure that only the admin will be able to change the property value/content after the Document Record is created.

6) New Customizations for Document Records

You can now choose if Property Groups (and Properties inside them) will be situated on the right or left side.

7) New “Related Documents” Property

Document Records now contain a “Related Documents” Property where you can define a “tree” structure or related Document Records (documents).

8) Off-the-Shelf customizable Single-Sign On integration

To empower our enterprise customers, we have created an off-the-Shelf customizable Single-Sign On integration for the most common services such as Azure Active Directory.

This feature allows your admins to connect your user management service to Legito without any programming, including mapping of your SSO roles with permissions in your Legito Workspace.

To activate, please contact our Helpdesk and request a subdomain for your Workspace.

9) More Customizable User Experience

Workspace admins can choose for each of the major Workspace areas if it opens in the same browser window or in new tabs.

More From New Releases

June 2022 Release: Legito Sign

June 2022 Release: Legito Sign

 

In addition to Legito BioSign, and integrations with various other electronic signature providers such as Adobe Sign and DocuSign, we have now released Legito Sign – Legito’s very own electronic signature that allows you to electronically sign contracts and other documents directly in your Legito Workspace.

Legito Sign is embedded directly in your Legito Workspace with absolutely no integration required. Legito Sign is free for Legito customers.

To activate Legito Sign, go to the Basic section of your Workspace Settings and check the Legito Sign box.

If you don’t have a Drop Area on your Legito Dashboard yet, simply create one and select the ”Sign document” type and then select Legito Sign. Learn more about Dashboard customization.

 

Ensure that your Workflow settings allow you to start the signing process in the appropriate Workflow Step.

If you use Legito Templates, allow Legito Sign for the Template Suite that you would like to use Legito Sign for.

Now your Workspace is all set, and you can start your signing process in 3 easy steps:

Step 1: Upload a PDF document or use Legito Template

Drop your PDF document into the Drop Area of your Dashboard, or simply click to Start Signing in the Legito Document Editor (if you wish to sign Legito Document).

Step 2: Define Signatories

Select your signatories and choose if you want a consecutive order of signatures.

Step 3: Define fields in a document and launch the signing process

Select a Signatory in the side menu and place relevant Signature and other fields into your document via drag-and-drop from the side menu into your document.

Once all the desired fields are in the document, click to Start the signing process. When you do this, the signing process officially starts. Legito Sign works in a similar way to the many other electronic signatures. The Signatories will receive an email, they click a button or a link in the email, fill in the relevant fields in the document (in particular the Signature fields), and confirm their consent to the document. Once everyone has signed, the document is emailed back to everyone. Of course, signatories do not need to have a user account.

The Legito Sign process is segmented into these stages:

  • Draft – The signing process hasn’t started yet.
  • Sent – The signing process has started but nobody signed the document yet.
  • Signing in Process – At least one signatory signed the document and the document is awaiting other signatures.
  • Signed – All signatories signed the document. The document is officially signed. The signing process is over.
  • Declined – At least one signatory declined their signature. The signing process is over and the document is not executed.
  • Expired – At least one signatory has not signed the document within the defined time period. The signing process is over and the document is not executed.
  • Voided – A Legito user with permission to Manage Signings has voided the document in the Manage Signings area of the Legito Workspace after the process was started (Sent status) or Signing was in the Process stages. The signing process is over and the document is not executed.

Some optional steps you can take before starting the signing process:

  • Customize your email message
  • Launch the signing process later
  • Set signing process expiration date

 

Manage Signings Area

After Legito Sign is activated, Workspace Admins and users with permission to “Manage Signings” will have a new item in the top Workspace menu – Manage Signing – where they can view and manage all Legito Sign processes.

 

Action users can take in this area are:

  • Edit document – If a document is still in the draft stage, users can edit fields in the Legito Sign Editor.
  • Void document – A document can be voided if it is in the “Sent” or “Signing in Process” stage.
  • Delete document – Any document can be deleted. Deleting a document means that its status will be automatically changed to “Voided” if possible. Deleted documents can always be restored from Trash.
  • Update Expiration date – It is possible to change the expiration date at any time before the signing process of a document expires.
  • Search and filter documents – It is possible to filter documents according to several criteria or by searching the document.
  • Download signed documents – Once a document is signed, it can be downloaded.

 

User Permissions

  • Can sign with Legito Sign – Users with this permission can start the signing process using Legito Sign
  • Manage Signings – Users with this permission can manage all existing Legito Sign signing processes (documents).

 

Relation to other components of Legito Workspace

Legito Documents created from smart Templates – As with any other electronic signature tool, it is possible to use Template Tags to automatically extract signatory names and email addresses. Learn more

Workflow and Document Records – The signing process and its stages are a sub-process of Legito Workflow Stages and Approvals. Workflow Stages are independent of the signing process stages but can be automatically triggered by them (Triggers: Signing in Process, Document was signed, Signature declined). Each PDF document uploaded to your Workspace automatically generates a Document Record. Once a document has been signed by all signatories, the signed document (PDF) is uploaded to the relevant Document Record. This principle is the same for other electronic signatures.

Integrations with other providers of electronic signatures – Legito Sign will provide you with more options regarding e-signatures. It does not override any of Legito’s current integrations with other electronic signature providers. All e-signature integrations are and will be supported in the future, and we will even be adding new ones soon.

Audit Trail (Timeline) – Events such as the start of a signing process, or that the document has been signed, or the signing process was canceled, are recorded in the Audit Trail (Timeline) for the relevant Document Records related to the Legito Sign process.

More From New Releases