What's New?

The following new features are introduced in this release: 

Roles and Permissions Implementation:
To provide authorization for specific feature(s) of letzNav, we have implemented roles. Every user will have a role and each role will have specific set of permission(s) allowing access to the respective feature(s). Role assignment must be done based on the access desired. Web services and user interfaces have been Implemented with the access restrictions. A user can also have individual application access, instead of all the applications. 

Currently, roles are of two types:  

  1. Default Roles:  

There are 9 default roles which cannot be modified. 

  • System Administrator 

  • Application Administrator 

  • Publisher 

  • Content Creator 

  • Dashboard Viewer 

  • Customizer 

  • Analytics Manager 

  • Scheduler 

  • Translator 

  1. Custom Roles:  

Custom roles can be created or deleted. Newly created roles can have desired permissions with respective access to feature/application(s).  

Learn more about Roles 

Positioning Feature: 

User can now adjust the positions for all the tools (validations, tooltips, launchers) just like workflow balloons. The icon tooltip will be adjusted automatically with respect to the element position on the screen. The icon can be moved further using the icon offset which will move the icon away from the element in the respective direction.  

Additional Controls: 

  1. For Element Selection:  
    In few places element picking might not be an ideal for identifying the page element, so we have added three new ways of identifying an element (These features are for power users who create the content for guiding users through the application).   

  

  • Custom script: Identify the element by writing a JavaScript code which returns an element that needs to be identified (For using this option we assume the user to have basic understanding on JavaScript). 

                 Limitation: No JavaScript libraries are supported  

                  

  • CSS Selector/XPath: Identify the element uniquely with CSS Selector and XPath.  

 

  1. For Frames:  
    In places where anchor points cannot be used to differentiate frames, we can use other options shown in the image to identify the page  

 

  

  • URI Hash: Insert a part of the page URI into the expression box, with which the page can be uniquely identified. While using this option the user must make sure that no other page in the application gets identified with the expression provided

 


  • Custom Script: Identify the page by writing a small JavaScript code that returns a Boolean value (For using this option we assume the user to have basic understanding on JavaScript).  

Limitation: No JavaScript libraries are supported  

  

  1. For Workflow Entry Points:  
    In Flow entry point where anchor points cannot be used to differentiate pages, we can use other options shown in the image to identify the page  

Shape

  • URI Hash: Insert a part of the page URI into the expression box, with which the page can be uniquely identified. While using this option the user must make sure that no other page in the application gets identified with the expression provided  

  

  • Custom Script: Identify the page by writing a small JavaScript code that returns a Boolean value (For using this option we assume the user to have basic understanding on JavaScript).  

Limitation: No JavaScript libraries are supported 

Keyboard Shortcuts in letzNav: 

To make the application more accessible, Keyboard shortcuts are introduced which help the user access all the tools without using the mouse. For each application, users can map unique key combination which will help them to perform the operation assigned. The key combinations can be changed in the Admin screen.  

Limitation: The default shortcuts from the browser cannot be overridden. User should select a unique key combination.  

Note: Keyboard shortcuts in letzNav are language independent  





Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.