Expanding our updates to Forms, Workflows, and Templates from our Spring ‘23 release, users can now flexibly view Data Tables and Mappings as well.
Data Tables and Mappings now have the same new look and features as Forms, Workflows, and Templates. The new screens include the following updates:
Data Tables and Mappings now have the new grid screen (like Forms, Workflows, and Templates) instead of the previous screen that displayed only the definition names on the left hand side.
The Data Tables screen has the following columns:
When the Data Tables screen is initially opened, the records will sort alphabetically by table name.
When you select a table, the row will highlight and a preview panel will appear on the right side of the screen.
On the Preview Panel, the following features are available:
Users can now intuitively create email and HTTP Backend Action requests.
Email and HTTP requests in Backend Actions now have a much more intuitive UI.
- UI adjustments to place fields in more relevant places on the action
- Reduced clicks as everything was brought into one screen
Now you can access and organize images in Mirata Data Tables.
A new Type is now available for fields in your Data Table schema: image. You can perform all the existing Data Table actions which you can for other Types (string, decimal, datetime, etc.). For example, you can:
- Query a Data Table image field to dynamically get the right image to display in a form
- Map image fields in your form to the image field in your Data Table in an add Data Table request
Note: When you query an image field in a Data Table, the result will be a URL (a string), not the image itself. You can easily use this URL to display the image in an image component on the form.
Use the new “Login Rights” role privilege to control users’ access to logging in to the Inbox, Designer, and Admin Tool applications altogether.
Previously, you could restrict users’ access to specific features within the Inbox, Designer, and Admin Tool, but you couldn’t restrict the ability to log in to the application itself. For example, someone who cannot build forms would be able to log in to the Designer, but they would not have viewing, editing, or creating form definition rights, so they wouldn’t be able to see any form definitions or perform any actions in the Designer.
Now, you can restrict users from logging in to the Inbox, Designer, and Admin Tool altogether, so you can avoid any confusion from a user logging into an application for which they have no rights to view, edit, or create anything.
If a user tries to log into a part of the application that they do not have access to, they will see a message informing them that they do not have rights to log in.
Client-side errors from the Web Inbox, Xamarin Inbox, Designer, and Admin Tool will now display in the Log Info table in the Admin Tool.
All errors which appear in your web browser console will now display in the Admin Tool Log Info as well, so your system administrators have much increased visibility into what’s happening across your organization.