New feature in Ultimate Forms: you can now configure where the Edit form redirects when you click on Save. By default, the form redirects back to the list view. Now, you are able to configure the target of redirection to the view (default), edit form or display form. Additionally, you can configure whether to add a new button to the form (Save & Edit or Save & View) or just to use the regular Save button. When you use the regular button and redirect back to Edit form, the second time you save, you will be redirected to the view, to prevent users from getting stuck in an infinite loop.
One of the common reasons to use this feature is integration of actions. Actions are executed on Save, so the user might need to perform additional data entry based on the results of the action execution. Note that in this scenario it's best to set the action to execute Synchronously, to make sure it completes before the form reloads.
The new features is accessible under General Settings section of Tabs and tab permissions.
NOTE: the feature is already added to the app version and will be coming to on-premises version in the next release.
In multi-lingual sites, the user interface of the site will appear in the preferred language of the current user. The same site will be displayed in English, French or Spanish, based on who accesses the site. You can even localize the column names, to make the forms appear in the preferred language.
When you add tabs and tab descriptions, they will appear in the language in which they were created. So if the site creator uses English, the tab names will appear in English even when the current user sees the site in French.
We now added a new feature to Ultimate Forms that allows you to translate the tab names and descriptions into additional languages. They will then appear to user translated into the preferred language (provided of course that you included the relevant translation).
Note that section names and fragments cannot be currently translated.
NOTE: the feature currently applies to the app version only. There is an existing translation mechanism in the on-premises version, the new app mechanism will be migrated to the on-prem version in the future.
In advanced systems sometimes you need different user levels to have different access to the same data. For example you might have a Sales Management System that has Sales People and Sales Managers SharePoint security groups. Sales People might need read only access to contracts and forecasting data but edit access to customer related fields. Using Infowise Advanced Column Permissions we can use a single list and secure individual fields based on SharePoint security groups.
In this video I walk through an example of how to use Infowise Advanced Column Permissions to secure fields in a single list to provide many different views of the New, Edit and View forms of a single list called Customer.