1)  QR Code Element

Legito Templates has a new Element type: QR Code

The QR Code Element can generate QR codes based on the content of the Document created from a Template, including information (data) inserted by the end user.

It is possible to define QR Code content by using either JSON or XML inserted into the Item Menu.

To include a value from an Element in the Template Suite into the QR Code, insert $ followed by the Template ID and System Name of an Element in {}, for example {12345.first_party_name}. Legito will help you to choose a Template and Element.

It is also possible to include the URL address of the Document Version or Document Record using ${DR.detailLink} or ${DV.documentEditorLink}. For more details, please read the instructions in the user interface.

Choose the size of the QR Code by dragging its right lower corner or using the Properties tab similarly to the Image Element.

Real-time preview of a QR code is available on the right side of the Item menu. QR Code in the Template content is updated when the Item menu is closed.

QR Code in the Document Editor is generated or updated in the Document Editor when the Document Version is saved.

2) Faster Template Editor Loading 

We improved loading of sophisticated Templates in the Template Editor so the scrolling is now much smoother. 

3) JSON Integration Matching Improvements

We added a new feature for matching JSON Integration attributes with Elements in Legito Templates. In addition to matching JSON attributes with a specific Element in the Template Suite, you can now  match it with the first Element where the System Name contains a certain string. This is especially useful for when a Clause from the Clause Library is used in a Template Suite, and is needed to fill-in Clause content with data from an incoming JSON file. 

4) Page Numbering in Body of Template

You can insert the Page Number Element into the body of a Template. Previously, it was only possible to insert it to header or footer only.

Legito’s current Document Editor has pageless view only, so the Page Number Element is applied to the Exported Documents (Word/PDF) only.

1)  QR Code Element

Legito Templates has a new Element type: QR Code

The QR Code Element can generate QR codes based on the content of the Document created from a Template, including information (data) inserted by the end user.

It is possible to define QR Code content by using either JSON or XML inserted into the Item Menu.

To include a value from an Element in the Template Suite into the QR Code, insert $ followed by the Template ID and System Name of an Element in {}, for example {12345.first_party_name}. Legito will help you to choose a Template and Element.

It is also possible to include the URL address of the Document Version or Document Record using ${DR.detailLink} or ${DV.documentEditorLink}. For more details, please read the instructions in the user interface.

Choose the size of the QR Code by dragging its right lower corner or using the Properties tab similarly to the Image Element.

Real-time preview of a QR code is available on the right side of the Item menu. QR Code in the Template content is updated when the Item menu is closed.

QR Code in the Document Editor is generated or updated in the Document Editor when the Document Version is saved.

2) Faster Template Editor Loading 

We improved loading of sophisticated Templates in the Template Editor so the scrolling is now much smoother. 

3) JSON Integration Matching Improvements

We added a new feature for matching JSON Integration attributes with Elements in Legito Templates. In addition to matching JSON attributes with a specific Element in the Template Suite, you can now  match it with the first Element where the System Name contains a certain string. This is especially useful for when a Clause from the Clause Library is used in a Template Suite, and is needed to fill-in Clause content with data from an incoming JSON file. 

4) Page Numbering in Body of Template

You can insert the Page Number Element into the body of a Template. Previously, it was only possible to insert it to header or footer only.

Legito’s current Document Editor has pageless view only, so the Page Number Element is applied to the Exported Documents (Word/PDF) only.

More From New Releases

1) Conditional Default Values for Elements and Clauses

You can now set one or multiple Default Values for Template Elements and Clauses.

To set a Default Value, open a Template in the Template Editor, click an Element or the Edit button for a Clause, open Default Values tab in the top Element/Clause menu, click the “+ Default Value” button, and insert or choose the Default Value of that Element or Clause.

If more than one Default Value is set for the same Element or Clause:

• Each Default Value has to be conditioned. Conditional Default Values work similarly to Conditions for Elements and Clauses, including multiple sub-conditions and nested conditions (condition groups).
• Until a user manually changes a value of an Element or a Clause in the Document Editor, the Default Value will change dynamically based on the relevant choices or inputs a user done elsewhere in the Template Suite.
• In the case of conflicted Default Values, the system will apply the one that is higher in the order (e.g. From Default Value 1 and 2, 1 will be applied).

Default Value can by added to the following types of Elements and Clauses:

• Question (Default Value is defined by choosing one answer to the Question)
• Text Input (Default Value is defined by inserting text string)
• Select (Default Value is defined by choosing one option from the Select)
• Date (Default Value is defined by inserting a date)
• Money (Default Value is defined by inserting an amount and choosing a currency)
• Switcher (Default Value is defined by choosing either Active or Deactivated status)
• Article, Paragraph, Subparagraph, Point, and Item (Default Value is defined by choosing either Active or Removed status)

Prior to the release of this feature, we recommended using Default Template Settings in the Document Editor for default values. The Default Template Settings feature is not affected by Conditional Default Values and Default Template Settings will work in the same way.

Limitations:

• Default Values do not work for Questions or Selects referring to Objects.
• Default Values do not work for Reference Options in Questions, and Selects that are referring to repeated Elements (or Elements in repeated Clauses).
• Limitations for Conditions are applicable to conditional Default Values.

2) Word Insertion Section

There may be a situation where you need to allow users to upload a Word document into a Legito document, typically a technical description or service specification, and export everything as one document. For these situations, we developed a special type of Next Page Section – a Word Insertion Section that will allow users upload a Word document to the Document Editor.

There can be multiple Word Insertion Sections in one Template.

The content of the uploaded Word document is exported together with other content of the Template from Legito to a Word or PDF document. Content in each uploaded Word document will be exported to its own separate Next Page Section.

To add a Word Insertion Section, go to the Template Editor, scroll down to the “+ Next Page Section” button and click the chevron on the right, then select “+ Word Insertion Section”.

Conditions and Repeat may be added to the Word Insertion Section.

Users can upload the Word document in the Document editor to this Section by clicking the Upload button and selecting the .docx file. Once uploaded, the file can be removed by clicking on the trash icon in the top right corner. The Element also contains the preview of the uploaded Word document.

Notes:

• Elements or Clauses cannot be inserted to the Word Insertion Section because its content is defined by the inserted Word document.
• Word Insertion Section does not have a Header and Footer because these are defined by the inserted Word Document.
• If the uploaded Word document has correctly defined Page Numbering, it will continue from the previous Section when the final document is exported from Legito.

1) Conditional Default Values for Elements and Clauses

You can now set one or multiple Default Values for Template Elements and Clauses.

To set a Default Value, open a Template in the Template Editor, click an Element or the Edit button for a Clause, open Default Values tab in the top Element/Clause menu, click the “+ Default Value” button, and insert or choose the Default Value of that Element or Clause.

If more than one Default Value is set for the same Element or Clause:

• Each Default Value has to be conditioned. Conditional Default Values work similarly to Conditions for Elements and Clauses, including multiple sub-conditions and nested conditions (condition groups).
• Until a user manually changes a value of an Element or a Clause in the Document Editor, the Default Value will change dynamically based on the relevant choices or inputs a user done elsewhere in the Template Suite.
• In the case of conflicted Default Values, the system will apply the one that is higher in the order (e.g. From Default Value 1 and 2, 1 will be applied).

Default Value can by added to the following types of Elements and Clauses:

• Question (Default Value is defined by choosing one answer to the Question)
• Text Input (Default Value is defined by inserting text string)
• Select (Default Value is defined by choosing one option from the Select)
• Date (Default Value is defined by inserting a date)
• Money (Default Value is defined by inserting an amount and choosing a currency)
• Switcher (Default Value is defined by choosing either Active or Deactivated status)
• Article, Paragraph, Subparagraph, Point, and Item (Default Value is defined by choosing either Active or Removed status)

Prior to the release of this feature, we recommended using Default Template Settings in the Document Editor for default values. The Default Template Settings feature is not affected by Conditional Default Values and Default Template Settings will work in the same way.

Limitations:

• Default Values do not work for Questions or Selects referring to Objects.
• Default Values do not work for Reference Options in Questions, and Selects that are referring to repeated Elements (or Elements in repeated Clauses).
• Limitations for Conditions are applicable to conditional Default Values.

2) Word Insertion Section

There may be a situation where you need to allow users to upload a Word document into a Legito document, typically a technical description or service specification, and export everything as one document. For these situations, we developed a special type of Next Page Section – a Word Insertion Section that will allow users upload a Word document to the Document Editor.

There can be multiple Word Insertion Sections in one Template.

The content of the uploaded Word document is exported together with other content of the Template from Legito to a Word or PDF document. Content in each uploaded Word document will be exported to its own separate Next Page Section.

To add a Word Insertion Section, go to the Template Editor, scroll down to the “+ Next Page Section” button and click the chevron on the right, then select “+ Word Insertion Section”.

Conditions and Repeat may be added to the Word Insertion Section.

Users can upload the Word document in the Document editor to this Section by clicking the Upload button and selecting the .docx file. Once uploaded, the file can be removed by clicking on the trash icon in the top right corner. The Element also contains the preview of the uploaded Word document.

Notes:

• Elements or Clauses cannot be inserted to the Word Insertion Section because its content is defined by the inserted Word document.
• Word Insertion Section does not have a Header and Footer because these are defined by the inserted Word Document.
• If the uploaded Word document has correctly defined Page Numbering, it will continue from the previous Section when the final document is exported from Legito.

More From New Releases

1) New Property for Document and Object Records: Associated Templates

This feature helps you efficiently draft Amendments, Termination Notices, Purchase Orders (within a Master Agreement), and similar documents that share a lot of the same data contained within the main contract by automatically pre-filling data from the main document (typically a contract) to its related documents.

How this features works

The Associated Templates property lets you attach Template Suites to Documents Records. When such a Template Suite is used, it automatically triggers the Smart Import feature which populates the data from the Legito Document connected with the Document Record (e.g. Master Service Agreement), and sets the Document Record of the newly generated Legito Document (e.g. Amendment) as Related (subordinate) to the Document Record where the Template Suite was selected from.

How to set up this Property

It is possible to create this Property in Workspace Settings, either in the Document Records section or Objects section the same way as any other Property.

Except for the standard Property settings, you must define which Template Suites are displayed. It is possible to choose from all Template Suites of the Workspace regardless of user permissions assigned to them. This Property overrides Template Suites permissions, which means that Users who do not have permission to use a certain Template Suite may use it when defined in this Property and have access to the Document Record where this Property is used.

Enabling Templates in selected Workflow Stages

We understand that you might want to only allow Users to use some Template Suites (Documents) in certain Workflow Stages, for example, use Termination Notice only when a document is scheduled to be terminated, so it is possible to define which Workflow Stage in each Template Suite is enabled for each User.

Apply the Sharing from the main Document Record

You may also want to share a related Document (Document Record) created by using this Property with the same Users as the main Document. You can do this by activating the “Apply Sharing” feature.

Other Use

Associated Templates may also be used in Object and Document Records without a Legito Document but in this case, the data import won’t be applied.

2) Related Document Setting in the Document Editor

Relative to the previous feature (but not limited to it), we added an option to select if a Document (Document Record) created from a Template should be related (subordinate) to another Document Record.

You can find this setting in the new “Document Record” Tab of the Document Menu Bar.

3) Redesign of Workspace Main Menu

We slightly redesigned the Main Menu of your Workspace and significantly improved its responsiveness on tablets and phones. Items that do not fit on the screen are automatically added to the More dropdown menu.

4) Redesign of Template Editor Left Bar

You probably noticed that we have added more Element types to our Template Editor. To keep the user interface nice and simple, we added a view setting that allows you to display only Popular Elements. If you are an Advanced Power User, we recommend you display the Full List of Elements.

5) Improvements to the JSON Integrations Feature

We improved mapping of JSON Objects to Template Elements in the JSON Integration Editor.

In addition to selecting the Template and its certain Element, it is possible to insert a System Name. In such a case, the JSON Object will be matched with each Element in the Template that has such a System Name (exact match).

This feature is especially useful when Clause Library Clauses are used in your Templates.

6) Enhanced Tags & Scripts Section

To improve your user experience, we enhanced management of the Template Tags and Scripts.

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

1) New Property for Document and Object Records: Associated Templates

This feature helps you efficiently draft Amendments, Termination Notices, Purchase Orders (within a Master Agreement), and similar documents that share a lot of the same data contained within the main contract by automatically pre-filling data from the main document (typically a contract) to its related documents.

How this features works

The Associated Templates property lets you attach Template Suites to Documents Records. When such a Template Suite is used, it automatically triggers the Smart Import feature which populates the data from the Legito Document connected with the Document Record (e.g. Master Service Agreement), and sets the Document Record of the newly generated Legito Document (e.g. Amendment) as Related (subordinate) to the Document Record where the Template Suite was selected from.

How to set up this Property

It is possible to create this Property in Workspace Settings, either in the Document Records section or Objects section the same way as any other Property.

Except for the standard Property settings, you must define which Template Suites are displayed. It is possible to choose from all Template Suites of the Workspace regardless of user permissions assigned to them. This Property overrides Template Suites permissions, which means that Users who do not have permission to use a certain Template Suite may use it when defined in this Property and have access to the Document Record where this Property is used.

Enabling Templates in selected Workflow Stages

We understand that you might want to only allow Users to use some Template Suites (Documents) in certain Workflow Stages, for example, use Termination Notice only when a document is scheduled to be terminated, so it is possible to define which Workflow Stage in each Template Suite is enabled for each User.

Apply the Sharing from the main Document Record

You may also want to share a related Document (Document Record) created by using this Property with the same Users as the main Document. You can do this by activating the “Apply Sharing” feature.

Other Use

Associated Templates may also be used in Object and Document Records without a Legito Document but in this case, the data import won’t be applied.

2) Related Document Setting in the Document Editor

Relative to the previous feature (but not limited to it), we added an option to select if a Document (Document Record) created from a Template should be related (subordinate) to another Document Record.

You can find this setting in the new “Document Record” Tab of the Document Menu Bar.

3) Redesign of Workspace Main Menu

We slightly redesigned the Main Menu of your Workspace and significantly improved its responsiveness on tablets and phones. Items that do not fit on the screen are automatically added to the More dropdown menu.

4) Redesign of Template Editor Left Bar

You probably noticed that we have added more Element types to our Template Editor. To keep the user interface nice and simple, we added a view setting that allows you to display only Popular Elements. If you are an Advanced Power User, we recommend you display the Full List of Elements.

5) Improvements to the JSON Integrations Feature

We improved mapping of JSON Objects to Template Elements in the JSON Integration Editor.

In addition to selecting the Template and its certain Element, it is possible to insert a System Name. In such a case, the JSON Object will be matched with each Element in the Template that has such a System Name (exact match).

This feature is especially useful when Clause Library Clauses are used in your Templates.

6) Enhanced Tags & Scripts Section

To improve your user experience, we enhanced management of the Template Tags and Scripts.

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

More From New Releases

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.

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

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.

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

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.

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

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.

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

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.

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

1) Questions and Selects referring to Objects​

The much-awaited connection between Templates and Objects is here.

a) New category of Questions and Selects

Up until now, it was possible to manually add options to Questions and Selects by either typing the text of the option or referencing a value from another element in the Template. Additionally, it is now possible to choose that a Question or Select will display Object Records as an alternative to the ones with options defined “statically” in the given Question or Select.

To apply a choice from Object Records to a Question, click on the Objects tab above the Question. To apply a choice from Object Records for a Select, click the Select and choose Objects at the top of the dropdown. Then continue by selecting the following properties:

Object

Define the Object from which Records users can choose.

Property

Define which Property of the selected Object Record will be displayed.

Dropdown Label (optional)

Choose another property of the Object that will be displayed in the dropdown where users choose the option. The purpose of this label is to help your users identify the right option if the Property value is the same for more options. For example, if the Object is a list of your customers – the Property is <Name> and the Label is <Address>, and there are 3 John Does, the address will help the user identify the correct John Doe.
The Label of the selected Option will not be displayed, therefore it will not be part of the document in the case of a Select element. This property is optional and you can leave it blank.

Filter (optional)

In case you don’t want to allow users to choose from all Records of the selected Object, it is possible to apply the saved Object Filter (more info in point 5 of this article) for the Select or Question. In this case, users will only be allowed to choose in the Select or Question Records according to the applied filter).

For example, if you have an Object containing your customers that are either active or churned, you can use this to apply a filter so your users can choose only from active customers. The Filter is optional and you can also leave it blank.

b) Links to Questions and Selects referring to Objects

It is possible to set Links to Questions and Selects referencing to Objects. The difference between Links to other types of Template Elements or Clauses is that such Links contain one additional parameter that makes it possible to display a value from another Property of the selected Object Record than the one defined in the Question or Link.

Therefore, such Links may display a different text than that of the selected Option in the Question or Select they are referring to. For example, if there is an Object containing your customers and each customer (Object Record) contains information about Name, Address, and Date of Birth, and the Select contains the Name, then one Link to such a Select will display the Address, and the other Link will display the Date of Birth. 

c) Condition based on Questions and Selects referring to Objects

It is possible to create Conditions based on a Question or Select referencing to an Object. Because there might be a large number of Object Records and they can dynamically change, it is possible to apply only the text operators (contains, does not contain, is empty, is not empty, etc.) for the definition of such a Condition.

d) Supported Object Property Types

The following Property Types are supported in this Feature:

• Single-line Text
• Multi-line Text
• Date (single)
• Number (will be displayed without prefix and suffix)
• Identifier

e) Search

Because there might be a large number of Object Records in a Question or Select referring to an Object, their dropdown in the Document Editor contains a full-text search. The full-text search is based on all text values in the Object Records; not necessarily the values displayed in the dropdown.

f) Persistence of selected options in a Legito Document

Once a Document (Document Version) is created from a Template, it keeps the values of the selected Document Records even if the values of the Properties in the Document Record are changed afterward.

Options displayed in the dropdown of the Question and Select display always be up-to-date values from the time that the page with the Document (Document Version) was opened (loaded) regardless of any previous Document Versions.

g) Permissions

User Permissions regarding the Object (or its Records) used in the Questions and Selects are not relevant for the purposes of Templates. Users with assigned permission to the given Template Suite and/or Document can always see values from the applied Object Properties in all Records available in the Question or Select.

2) Sharing for Objects

Similar to Document Records, it is not possible to apply Sharing of individual Records in an Object.

There are 3 permission levels:

• VIEW
• EDIT
• MANAGE

Object with activated Sharing has the following additional setting:

• Each Record has a mandatory Owner that has Manage permissions for the Record. 
• It is possible to define for each User if such a user has activated the auto-shared View, Edit, or Manage permissions to all Records in the Object.
• Each Object Record has a Share button where Users with Manage permissions can share the Record with other Users, as well as modify or remove permissions.
• Filter according to the assigned Owner appears in Filters, not on the left side of the Object page.
• Only Users with Manage permissions can change the assigned Owner, Share the Record, Delete the Record, and edit Properties that are by their definition editable only with Manage permissions.

It is possible to activate or deactivate Sharing for Objects in My account => Settings => Objects => Edit (for each Object) and then activate the item “Sharing” (tick the checkbox). It is also possible to deactivate Share for an Object.

1) Questions and Selects referring to Objects​

The much-awaited connection between Templates and Objects is here.

a) New category of Questions and Selects

Up until now, it was possible to manually add options to Questions and Selects by either typing the text of the option or referencing a value from another element in the Template. Additionally, it is now possible to choose that a Question or Select will display Object Records as an alternative to the ones with options defined “statically” in the given Question or Select.

To apply a choice from Object Records to a Question, click on the Objects tab above the Question. To apply a choice from Object Records for a Select, click the Select and choose Objects at the top of the dropdown. Then continue by selecting the following properties:

Object

Define the Object from which Records users can choose.

Property

Define which Property of the selected Object Record will be displayed.

Dropdown Label (optional)

Choose another property of the Object that will be displayed in the dropdown where users choose the option. The purpose of this label is to help your users identify the right option if the Property value is the same for more options. For example, if the Object is a list of your customers – the Property is <Name> and the Label is <Address>, and there are 3 John Does, the address will help the user identify the correct John Doe.
The Label of the selected Option will not be displayed, therefore it will not be part of the document in the case of a Select element. This property is optional and you can leave it blank.

Filter (optional)

In case you don’t want to allow users to choose from all Records of the selected Object, it is possible to apply the saved Object Filter (more info in point 5 of this article) for the Select or Question. In this case, users will only be allowed to choose in the Select or Question Records according to the applied filter).

For example, if you have an Object containing your customers that are either active or churned, you can use this to apply a filter so your users can choose only from active customers. The Filter is optional and you can also leave it blank.

b) Links to Questions and Selects referring to Objects

It is possible to set Links to Questions and Selects referencing to Objects. The difference between Links to other types of Template Elements or Clauses is that such Links contain one additional parameter that makes it possible to display a value from another Property of the selected Object Record than the one defined in the Question or Link.

Therefore, such Links may display a different text than that of the selected Option in the Question or Select they are referring to. For example, if there is an Object containing your customers and each customer (Object Record) contains information about Name, Address, and Date of Birth, and the Select contains the Name, then one Link to such a Select will display the Address, and the other Link will display the Date of Birth. 

c) Condition based on Questions and Selects referring to Objects

It is possible to create Conditions based on a Question or Select referencing to an Object. Because there might be a large number of Object Records and they can dynamically change, it is possible to apply only the text operators (contains, does not contain, is empty, is not empty, etc.) for the definition of such a Condition.

d) Supported Object Property Types

The following Property Types are supported in this Feature:

• Single-line Text
• Multi-line Text
• Date (single)
• Number (will be displayed without prefix and suffix)
• Identifier

e) Search

Because there might be a large number of Object Records in a Question or Select referring to an Object, their dropdown in the Document Editor contains a full-text search. The full-text search is based on all text values in the Object Records; not necessarily the values displayed in the dropdown.

f) Persistence of selected options in a Legito Document

Once a Document (Document Version) is created from a Template, it keeps the values of the selected Document Records even if the values of the Properties in the Document Record are changed afterward.

Options displayed in the dropdown of the Question and Select display always be up-to-date values from the time that the page with the Document (Document Version) was opened (loaded) regardless of any previous Document Versions.

g) Permissions

User Permissions regarding the Object (or its Records) used in the Questions and Selects are not relevant for the purposes of Templates. Users with assigned permission to the given Template Suite and/or Document can always see values from the applied Object Properties in all Records available in the Question or Select.

2) Sharing for Objects

Similar to Document Records, it is not possible to apply Sharing of individual Records in an Object.

There are 3 permission levels:

• VIEW
• EDIT
• MANAGE

Object with activated Sharing has the following additional setting:

• Each Record has a mandatory Owner that has Manage permissions for the Record. 
• It is possible to define for each User if such a user has activated the auto-shared View, Edit, or Manage permissions to all Records in the Object.
• Each Object Record has a Share button where Users with Manage permissions can share the Record with other Users, as well as modify or remove permissions.
• Filter according to the assigned Owner appears in Filters, not on the left side of the Object page.
• Only Users with Manage permissions can change the assigned Owner, Share the Record, Delete the Record, and edit Properties that are by their definition editable only with Manage permissions.

It is possible to activate or deactivate Sharing for Objects in My account => Settings => Objects => Edit (for each Object) and then activate the item “Sharing” (tick the checkbox). It is also possible to deactivate Share for an Object.

More From New Releases

1) Workflow for Objects​

It is now possible to use workflows for any Object you have in your workspace – similar to the way you assign a Workflow to a Template. Workflow is drafted in the Workflow Editor and set to be used for Object records. 

After the Workflow is created, you can assign it to the Object itself.

2) Template Editor – Bulk Replacement

There is new functionality for Bulk Replacement of Elements within Bulk Actions.

3) Template Editor – Search & Group Actions

You can now mark all found elements/clauses for further group actions in the Template Editor. Click “Choose all” in the search tab.

4) Filters for Grid and Kanban Dashboard Widgets

There is a new feature to apply existing filters for the Grid and Kanban Widgets on your dashboard.

5) Document Record Type Filter & Template Suite Filter

There are new options within the Document Management section where you can filter by the Template Suite your Legito Document was created from, and the Document Record Types.

6) PDF Attachments Merge

It is now possible to merge PDF attachments together with documents created from your Template Suite. If the “Combine all PDFs into one file” option is checked, attachments are included in the merged PDF export.

7) JWT Token Generator for Legito’s REST API

To simplify testing of the REST API integration, you are now able to generate a JWT Token for testing. The generated token will expire after 1 hour.

1) Workflow for Objects​

It is now possible to use workflows for any Object you have in your workspace – similar to the way you assign a Workflow to a Template. Workflow is drafted in the Workflow Editor and set to be used for Object records. 

After the Workflow is created, you can assign it to the Object itself.

2) Template Editor – Bulk Replacement

There is new functionality for Bulk Replacement of Elements within Bulk Actions.

3) Template Editor – Search & Group Actions

You can now mark all found elements/clauses for further group actions in the Template Editor. Click “Choose all” in the search tab.

4) Filters for Grid and Kanban Dashboard Widgets

There is a new feature to apply existing filters for the Grid and Kanban Widgets on your dashboard.

5) Document Record Type Filter & Template Suite Filter

There are new options within the Document Management section where you can filter by the Template Suite your Legito Document was created from, and the Document Record Types.

6) PDF Attachments Merge

It is now possible to merge PDF attachments together with documents created from your Template Suite. If the “Combine all PDFs into one file” option is checked, attachments are included in the merged PDF export.

7) JWT Token Generator for
Legito’s REST API

To simplify testing of the REST API integration, you are now able to generate a JWT Token for testing. The generated token will expire after 1 hour.

More From New Releases