"> "> ">
Larger Chevron Button

Canvas Enhancements

Automatic restore points to save your progress

With NLSv10.4 we introduced the ability to manually create application restore points so that Canvas authors could easily return to a previous snapshot of their application. However, these restore points had to be made manually, and naturally, sometimes we will forget.

xx

With NLS v10.5 we have implemented automatic restore points, ensuring that there is always a recent snapshot of your Canvas application to return to if something goes wrong.

As of v10.5, automatic restore points will be generated:

  • When an application is opened for editing;
  • 5 minutes after a change is made to the application;
  • When an application is closed for editing.

View restore points by clicking on the application's name in the 'Canvas' tab of Workbench and navigating to the 'Restore Points' menu on the left sidebar.

Automatic restore points are clearly marked with the tag 'Automatic' while manual restore points are marked 'Non-Automatic'.

Run drafts of your Canvas applications

NLS v10.4 introduced Versions to Canvas. With Versions, Canvas authors can save snapshots of their application at a particular point. An application version can be made 'default'. The default version is the version of the app that will be run if a user clicks the 'Run' button on Workbench, or visits the application's URL.

With v10.5 Canvas authors can now utilize the same 'Run Draft' functionality that already exists for Studio applications.

xxx
Clicking the 'Run draft' button under the 'Actions' column in Workbench will now run whatever version of the application is currently being edited.
 
Clicking the 'Run' button will run whatever version of the app is marked as 'default' from the 'Versions' tab of the application settings.
 
With this functionality authors can maintain an official default version of the application for end-users, while still being able to run and test new drafts as they're building out their applications or adding new features.

Multiple inbound node connections

Previously, Canvas nodes could only receive one inbound connection, meaning that diverging application pathways had to remain separate.

Now, Canvas nodes can receive inbound connections from multiple other nodes, allowing for the convergence of multiple pathways and enabling Canvas authors to construct more complex and streamlined business solutions.

s

Branch labels to enhance organization

With NLS v10.5, Canvas now supports author-customizable branch labels for branching pathways, enabling better application organization in the Canvas workspace for Canvas authors and collaborators.
 
When a pathway is branched, the branches are each assigned a name. By default, they are given numbers (1, 2, 3...). The branch labels will appear in the Canvas workspace hovering near their respective branch. They can be moved by clicking and dragging.
a

Authors can customize the branch labels by clicking in the field marked 'situation label' in the editing window.

Branch labels 2

The labels can also be edited from the Canvas workspace directly by double-clicking on them.

Utilize application variable values in Email Node subject lines

The Canvas email node now supports the insertion of variable values into the subject field, enabling authors to utilize application values in their subject lines.

To insert a variable into a subject line, simply click 'INSERT' within the subject line and choose 'Variable value' to create a value insertion tag. Click the insertion tag and choose an upstream application variable or system variable whose value you wish to insert.

This enhancement allows for more modularity and personalization in email subject lines, further enhancing the effectiveness of emails generated by your Canvas application.

 

q

Support for more than 3 branches from a node

Previously, Canvas applications did not support more than three branches stemming from a particular node, meaning that Canvas authors were limited to providing a maximum of three potential pathways at any given point in the application. That limitation has been removed with NLS v10.5.
 
Canvas authors can now create as many branches as they wish, to achieve even more complex and functional business solutions with their Canvas applications.
qq

All Canvas apps are now synced to NDM by default

As of NLS v10.5 all newly created Canvas applications will be synced to Neota Data Manager (NDM) by default. NDM is Neota Logic's no-code database storage solution. Apps synced to NDM will have their data stored in a secure SQL database.

NDM functionality also enables Canvas applications to be integrated with Workflows: Neota Logic's multi-user, multi-application business process and workflow management solution.

What's more, when a Canvas app is added to a Workflow, Canvas authors can then take advantage of Neota Logic's Sessions and Dashboards functionality.

NDM connection information can be found within the Canvas 'Start' node.

 All newly created Canvas apps will be automatically assigned to an NDM server. You can change which NDM server the app is synced to.

If you're not sure which NDM database to use, consult with your site administrator, or reach out to support@neotalogic.com.

w (2)
Canvas apps created prior to v10.5 can also be synced to an NDM database. Simply visit the Start node an existing application and click the 'Save application data' toggle to activate the NDM connection.
ww (2)

Workflow

Workflow lanes can now be accessed anonymously 

In Workflow, lanes represent particular roles or personas in an organization. Previously, Workflow users required an active user account and needed to be logged into Workbench in order to interact with an application in a Workflow lane.
However, there are many contexts in which Workflow authors would like applications in a lane to be accessed anonymously, with no requirement for the end-user to be logged in with a Workbench user name and password.
 
With NLS v10.5 workflow lanes can now be toggled as 'Anonymous', enabling workflow authors to grant application access to any user with the workflow URL.
 
To set a lane as anonymous, simply edit a lane and uncheck the box that says 'Login Required'.
e

Service Task – Run Neota applications as a service in the background of a Workflow 

The Service task is a new addition to Workflow which enables Workflow authors to utilize Neota Logic applications as a service as part of their Workflow.

d

A service application is a Neota Logic application which does not have any runtime component. A service application can be invoked to perform a particular function, and this function is carried out in the background without any user interaction. A service application can receive input values and produce output values. Service applications are typically used to perform specific tasks or execute complex logic.

dd

For more information, consult the Workflow Service Applications and the Service Task sections of the User Manual.

Canvas Apps now supported in Workflow

Workflow authors can now add Canvas applications to their Workflow, enabling even more rapid development and deployment of their business solution.
 
Canvas applications can now be added the same way as Studio applications, from the 'Apps' tab of the Workflow editor.
A Canvas application must be synced to the same NDM database as the Workflow in order to be added to the Workflow. See above for more information on syncing your Canvas applications with NDM.

Document Automation

Studio

Value Displays for Unset Values in List and Yes/No Variable Types
Studio now supports the creation of custom value displays for Unset values in List and Yes/No variables.
 
With this functionality authors may enter more descriptive or helpful Unset value displays, allowing for better UX and enabling more efficient application debugging.
c

Save and load sets of value displays 

NLS v10.5 further enhances the utility of display values with support for the saving and loading of custom display value sets for List and Yes/No variables.

When an author has crafted custom display values, the set of display values can be saved and re-used with other variables.

Save a set of value displays with the 'Save Preset List' button and load a set of value displays with the 'Load Preset List' button from the 'Values' tab of any Yes/No or List type variable.

v

Toggle between value displays and default variable values for List and Yes/No variable types 

As of version 10.5, when mapping from a List or Yes/No type variable into a document merge field, authors may now choose between using the 'default' variable value, or using the 'value display' value of a particular variable when passing that value into the document merge field.
A new column has been added to the document configuration screen: 'Value Type'.
 
When mapping from a List or Yes/No to a merge field, authors can choose which value type they prefer from a drop-down menu.
 
'Variable Value' will pass the raw value as recorded by the system into the merge field.
 
'Variable Value Display' will pass the value display value into the merge field.
r

Neota Logic Word Toolbar

Assigned Named Value Display Sets with the Word Toolbar 

As described above, Neota Logic authors now have the ability to create and save custom sets of display variables for List and Yes/No variable types. Concurrently, we have enhanced the Neota Logic Word Toolbar to so that authors can specify a display variable set to be applied to their List or Yes/No variable when it's generated in Studio from their document import.

This will save authors' time when importing their template document to Studio, as the appropriate variable display sets will be automatically applied to application variables.

To implement named value display sets in your document automation solution, follow these steps:

You should create and save your custom display variable set in Studio before proceeding with these steps.

First define the Named Display Variable Sets by selecting it from the 'Variables' drop-down menu in the Word Toolbar.

t
Click 'Add' to define the named variable sets you wish to assign to your variables. These names should correspond exactly to the set in Studio which they will be matched with.
f
Create a new List or Yes/No variable, or edit an existing one, and assign the display value set you want to be applied in Studio.
ff

Now when you import this template document to Studio and create the variable with the import tool, the value display set you specified with the Word Toolbar will be applied to the variable.

Organizer Search

The World Toolbar Organizer function has been enhanced with a search function. The search makes for more efficient template document creation and management, particularly with larger template documents.

Search for a keyword and relevant variables, forms, issues and conditions will appear.

g

Statistics

NLS v10.5 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 access 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

Workflow Statistics

The new Workflow Statistics page offers essential insights into how Workflows are being utilized on your subsite.
2

Track data points including how many times the workflow has been run, how many sessions have been completed, how many emails have been generated, and more.

Application Usage Statistics

The application statistics page contains usage data for all applications on your subsite.

Application Usage

Track data points including how number of sessions started, reports generated, emails sent and whether or not the app was run as part of a workflow.

Workbench

Canvas applications as a homepage for new users 

With NLS v10.5 subsite administrators may now specify Canvas applications as the default homepage for new user accounts.
 
When inviting a new user (from the gear options menu -- > 'Users' --> 'Invite new user(s)') navigate to the 'Application' option under the 'Homepage' configuration.
 
Canvas applications present on the site will now appear here and can be set as the new user's homepage.
3

Library

Building Blocks

The Neota Library contains pre-built application components and template applications to assist authors in deploying complex and useful application functionality. We are continually adding new application Building Blocks—pieces of key application functionality—to support Neota Logic authors in developing and deploying their business solutions.
 
We are always looking to create new Building Blocks to support our authors. If you have an idea for a future Building Block, please click this link and let us know!
 
The following additions to the Library are available with NLS v10.5:
 
DocuSign: Add e-signatures
Connect your DocuSign account and add in our two DocuSign building blocks to rapidly implement e-signatures in your business solution with just a few clicks. These building blocks take care of much of the technical heavy lifting required to integrate Neota Logic applications with DocuSign. Utilize these easy-to-implement building blocks and have e-signature functionality in your application in minutes.
 
 
Screenshot 2021-03-01 151109

Box Integration

Upload a file: Connect your Box account, and add in our Box building block. Within minutes your Neota Logic application will be capable of uploading a file from your application to Box cloud storage. Utilize this functionality to upload and store a document automated with the Neota Word Toolbar, or save a file uploaded at runtime by your end users.

Retrieve a file: Connect your Box account, and add in our building block to retrieve a file from your Box cloud storage and utilize it within your Neota Logic application.

 

Screenshot 2021-03-01 151340

Neota-as-a-Service (NaaS)

Support for MIME variables in NaaS operations 

Neota Logic now supports the sending and receiving of MIME variables as part of Neota-as-a-Service (NaaS) operations and Workflow Service Tasks.

With the ability to easily send and receive entire files and documents to Neota service applications, this update greatly enhances Studio and Workflow authors' abilities to implement complex solutions which rely on service tasks; e.g. processing of multiple PDF files, generation of automated documents or transfer of excel spreadsheets.

To send a MIME variable to a Neota Logic application in Workflow, simply map the MIME variable to the corresponding input using the Service Task node. The MIME variable must have been uploaded to NDM prior to this service task.

6
 
To send a MIME variable to a Neota Logic application using the NaaS tool in Studio, open the API name configuration by selecting 'Attribute API Names' from the 'Navigation' drop-down menu.
 
Attribute the MIME variables you wish to send to an appropriate API name and make sure that it's marked as an 'Output'.
 
Finally, tick the checkbox labelled 'Return MIME as binary'.
 
7