"> "> ">
Larger Chevron Button

Asset Manager:

Manage application assets from Workbench

The new Asset Manager significantly enhances how assets are uploaded and managed across applications on a Neota site.

Neota users with the role of author (including Canvas and Workbench author) and site administrators will find a new tab on Workbench: Assets. 

From the Assets tab, Neota authors and admins can manage and view existing application assets, and upload new assets.

Asset Manager
What is an 'Asset'?
Assets are files or resources that can be used in a Neota application.
 
Asset types supported include media files (images, audio), documents (Word, Excel, PDF), web fonts, proprietary fonts, custom style sheets, and more.
 
If you need to use a file in an application, Asset Manager is the tool.
What can I do with Asset Manager?
With Asset Manager, authors and site admins can upload, manage, and share assets.
 
Functions include:
  • Preview image assets — in a grid or detail view
  • Organize assets with searchable tags — filter and search tags for quicker asset navigation
  • Search for assets — search by keywords to find a specific asset
  • Export assets — download and save assets to your computer
  • Manage permissions — control who on your site can modify or access assets
  • Usage information — see all the apps in which an asset is used
  • Upload new assets — drag and drop from your computer into the web browser
  • Recycle bin — recover assets deleted by accident
 
Review the Asset Manager section of the Neota User Manual for complete documentation.
Asset Manager 2
Changes to Studio
The 'Assets' menu from Studio has been removed because assets are now managed from the Assets tab in Workbench.
 
Authors can access the Asset Manager easily from Studio by selecting 'Asset Manager' on the 'Administration' menu.
 
This will open the site's asset manager in the user's browser.
 
Using an asset in Studio, e.g., inserting an image into the tagged text editor, works exactly as before.
Asset Manager 3

Introducing 'Open Negotiation':
Neota's new document negotiation capability

We are proud to introduce Open Negotiation, our new document negotiation capability.
 
Open Negotiation enables application end-users to view a document, make edits, track changes, and leave comments, all within a familiar MS Word-style editing interface provided by OnlyOffice.
 
Open Negotiation supports Neota Document Automation, allowing authors to craft business solutions that include drafting and approval workflows as well as negotiation of document text by the participating people, both internal and external.
 
Typically, a document negotiation process is carried out by confusing threads in email to exchange drafts, or offline. Either process is slow and inefficient.
 
With Neota Open Negotiation, negotiation can be streamlined and performed and managed entirely within a Neota workflow.
 
Combine Neota Document Automation, Open Negotiation and Workflow to achieve end-to-end document drafting, approval, routing, negotiation, signature, and storage solutions.
Open Negotiation 1

Get started negotiating your first document!

 
To try Open Negotiation in Studio, add a document to an application by importing a Template document (created using the Neota Word Add-in) or uploading one manually.
Open Negotiation 2
 
Create a MIME variable of data type 'doc/docx'. Navigate to 'Question Features' and set the input type as 'Open Negotiation'.
Open Negotiation 3
 
Edit the document. While the document is open, target-drop the MIME variable and select 'Map Content to Variable'.
 
Drive a value input for this MIME variable at runtime.
 
The Open Negotiation interface will open the document.
 
Your document should be automatically set in 'track changes' mode. To toggle track changes on or off, and access other collaboration features, navigate to the 'Collaboration' tab.
Open Negotiation 4
Now you can start making edits, tracking changes and leaving comments on your document.
 
Visit the Open Negotiation page of the Neota User Manual for more information.
Open Negotiation 5

Neota Logic Connector for SharePoint
now available

The Neota Logic Connector for SharePoint is now live on the Microsoft AppSource store.

With the SharePoint connector, Neota Logic authors can upload, download and manage files on a Microsoft SharePoint site using a Neota Logic application.
 
For detailed instructions on setting up the SharePoint connector and interacting with SharePoint using a Neota app, refer to the SharePoint connector section of the Neota User manual. Also, in the Workbench Library, there are two Building Block applications to help authors get started on integrating with SharePoint.
 
Read more about the Sharepoint connector building blocks below.
NL for Sharepoint-1

Neota Library

We regularly add new content to the Neota Library—including application building blocks and instructional resources.

New Building Blocks

Building blocks are ready-built application components that can be integrated into larger solutions. With v10.6 there are three new building blocks.

Open Negotiation Connector Building Blocks
Use the Open Negotiation building blocks to get a quick start with our new negotiation capability, These building blocks provide a pre-built workflow that passes the document back and forth between users until the text is accepted.
 
Visit the User Manual page for the Open Negotiation Building Block for detailed instructions.
Building Block 1
Neota SharePoint Connector Building Blocks
1. Upload a file: Connect to your SharePoint Online account, and add the SharePoint building block. Your Neota application will be able to upload a file to a SharePoint document library. Use this functionality to upload and store a document automated with the Neota Word Toolbar, or save a file uploaded at runtime by end users.
 
2. Retrieve a file: Connect to your SharePoint Online account, and add the second SharePoint building block. Your Neota application will be able to retrieve and use a file from a SharePoint document library.
 
Visit the User Manual page for the Neota SharePoint Connector Building Blocks for detailed instructions.
 

Instructional applications

A number of instructional applications have been added to the library to help authors add specific functions to applications:
  • Add a watermark to a document
  • Add an image to a document
  • Add a form visit counter
Building Block 2

Email Node 

Workflow & Canvas

The Email Node for Workflow has been significantly enhanced.

Email attachments

The Workflow email node now supports attachments.
 
Any NDM-synced MIME variable from one of the Workflow's participant applications can be used as an attachment
 
To add an attachment to a Workflow email, click the paperclip icon in the node and then select an NDM-synced MIME variable from the drop-down menu.
Email node

'From' address

Workflow authors can now configure a 'From' address for emails generated by Workflow and Canvas email. A 'from' address will appear as the sender of the email.
 
To add a from address, enter it in the 'From' field.
 
A 'from' address can be text manually entered by the author or the runtime value of an NDM variable. A 'From' field can have only one email address.
Email Node 2

CC & BCC

The email node now supports carbon copy (CC) and blind carbon copy (BCC) in both Canvas and Workflow.
 
CC & BCC fields can be added by clicking the 'CC' and 'BCC' buttons.
 
Email addresses can be text manually entered by the author or the runtime value of an NDM variable. Multiple email addresses are separated by a semicolon.
Email Node 3

Workflow

NLS version 10.6 includes a number of enhancements and updates for Workflow to improve author productivity and end-user experience.

Support for translations

With NLS v10.6 Workflow authors can now specify a translation for a Workflow. This ensures that when applications in the Workflow are launched, they will appear in the expected language.

For a translation to be invoked, it must already exist within the relevant participant application. For more information on translations, review the Translations section of the User Manual.
There are three ways to set a translation for a Workflow:
 
1. Add a language identifier to the Workflow URL
 
A language identifier code can be added to any Workflow URL or Workflow Resume URL to launch Workflow applications with a translation.
 
The language identifier code is: '?lang=[language code]'
 
So if my Workflow URL was 'https://myserver.neotalogic.com/wf/myworkflow' and I wanted to launch it with a Spanish translation (code 'es'), the final URL would be: 'https://myserver.neotalogic.com/wf/myworkflow?lang=es'
 
Standard 2-letter language identifier codes, ISO-639-1, are listed here.
2. Add a preferred language to a user's Workbench profile
 
It is possible to specify a preferred language for any Workflow launched from a user's Workbench account.
 
To do so, visit the user profile by clicking on the avatar in the top-right corner of the Workbench screen and selecting 'Profile'.
Translation 1

From the user profile page, select a language from the 'Preferred language for Workflows' field.

Once set, any Workflow launched by your account will be launched with a translation of your preferred language, if such a translation exists.

Translation 2
3. Auto-detect language
 
Workflows can be configured to auto-detect the current user's preferred language based on the language set on the user's device and web browser.
 
Auto-detect language can be enabled from the 'Edit' button on the Workflow card settings.
Translation 3

Toggle 'Auto-detect language' on.

Translation 4

Workflow core fields

NLS version 10.6 includes new core field variables pertaining to Workflow. Any Workflow application created from version 10.6 onward will possess the following Workflow core field variables:
 
 Workflow Action: if this application is executed as a custom action then this will contain the name of the action. Otherwise, the app must be executing as part of the workflow and in that case it will be Unset.
  • Workflow ID: an identification number for the Workflow.
  • Workflow Resume URL: a URL to resume the Workflow by continuing from the current Session State.
  • Workflow Session ID: an identification number for the Workflow session.
  • Workflow Version: the version number of the version being run. If no version is specified or 'run draft' is clicked, it will read 'vdraft'.

Canvas – General

Canvas has been further improved with NLS version 10.6. With support for block image insertion and a redesigned formula node, it's now easier than ever to rapidly deploy professional, functional, and visually appealing web applications with Canvas.

Add images to Canvas applications

The Canvas text editor now supports the insertion of images. Images can be added to a paragraph element in a Canvas application.
 
To do so, edit an existing paragraph element or create a new one, click the image icon, and select an image from your computer.
Canvas 1

The image can be resized by dragging the rightmost edge or aligned to the left, centre, or right by clicking on one of the three alignment buttons.

Canvas 2

Redesigned Formula Node

The Canvas formula node has been redesigned and enhanced to make the construction of complex formulas easier and more intuitive for authors.
 
To get started, add a new formula node, assign an output name for the formula product, and click the '+ ADD FORMULA' button.
 
Choose an operation from the list.
Canvas 3

Enter values for each operand by entering one by hand, or referencing a system variable or upstream variable value.

Canvas 4

Change the operation by clicking on the operator.

Add additional operands to the function (if applicable) with the 'ADD OPERAND' button.
 
Click the '+ ADD FUNCTION' button to add another function to this formula.
Canvas 5

We can now assign a name to the product of the first function and then use it as an operand in the next function.

This feature enables authors to gracefully craft complex formulas that utilize multiple functions.
 
Consult the Canvas Formula Node section of the Neota User Manual for more information.
Canvas 6

Document Automation

New 'Prepare Document' function added to the Word Toolbar

Sometimes Neota authors may begin a project with a Template document containing pre-existing Word fields that conflict with fields used by the Neota Word Toolbar.
 
To ensure that Template documents work properly, the 'Prepare Document' function will remove conflicting fields from a document.
 
This is intended as the first step in creating a new Template document. This will ensure that the document can be automated and used without errors.
 
To prepare a document, click the 'Prepare Document' button on the Neota Word toolbar,
Doc automation 1

Click the 'Remove' button in the warning dialogue to confirm.

This action cannot be reversed.
 
The 'Prepare Document' action can be carried out on a document with or without the '-Template' suffix.
Doc automation 2

New 'Repeats' tab in Studio Document Editor

With NLS Version 10.1 we introduced the Repeat Tag to the Neota Word Toolbar. The Repeat Tag enables authors to display the values of instances and other multi-value variables in automated documents.
 
Previously, authors could only assign the repeat tag to a variable with the Word Toolbar in MS Word, requiring that they open and re-upload the template document any time there was a change related to the Repeat Tag.
 
With NLS Version 10.6, we have now added the ability to manage in Studio which variables are mapped to Repeat Tags.
 
When working with a template document in Studio, authors will find the 'Repeats' tab on the edit document screen.
Doc automation 3

From here authors can review existing variable mappings to repeat tags and re-map them by highlighting the row to change, target-dropping the variable to link to the repeat tag, and selecting 'Map X to Repeat'.

Sessions

Improvements to Sessions help Workbench users and Workflow owners view and download the data they need more efficiently.

Download visible session data only

WIth NLS v10.6, users can download either (1) all available data the user has permission to access, or (2) only the columns appearing in their personal session view. To download only selected data columns, configure your personal session view as you wish, then select download.

Sessions 1-1

All available session data can be downloaded by checking the 'Download all available data' toggle.

Statistics

NLS v10.6 brings two new additions to the statistics page: detailed Workflow data and application activity data. These pages provide more essential data points and insights for subsite administrators to see how their site's workflows and applications are being utilized at-a-glance.

Both pages can be accessed from the 'Statistics' screen, which is the first tab of the Workbench Settings page (accessible via the gear icon on the top-right of your screen).

In addition to the main overview, there are now two tabs for Workflow and Application Usage data.

1

Workbench

Workbench site customization and user administration have been improved.

Customize site favicon

Workbench site admins can customize a site's favicon, useful for branding.
 
A favicon will appear in the web browser tab for the Neota site and for any application run from that site.
Workbench 1

To set a custom favicon, navigate to the 'Settings' page, choose 'General' from the left sidebar and select the 'Customize' tab.

Click the existing favicon to change to one of your choice.

Workbench 2

User details screen improvements

The Workbench user details screen has been redesigned and enhanced for Workbench site admins. Site admins can now download the list of users as a .csv file.
 
Moreover, the new screen features a cleaner design and shows user roles at a glance.
Workbench 3

Products tab changed to Workflows

With NLS version 10.3 we introduced Workflow, the successor to Neota Logic Products.
 
As of version 10.6 we have officially retired Products. All references to Products on Workbench, including the main tab in Workbench, will now read 'Workflows'.
 
Existing Products are still 100% supported and will continue to function without disruption, but from 10.6 onward, only new Workflows can be created.
Workbench 4

Studio

Sort PDF form fields alphabetically

When authoring a Studio application that leverages Fillable PDF Forms, managing form fields may become challenging, particularly if there is a large number of fields.
 
To improve authoring efficiency in such cases, the PDF Form tool in Studio has been upgraded to support alphabetical sorting of PDF form fields.
 
Simply click the 'PDF Field Name' column header and Studio will sort form fields alphabetically.
Studio 1