TeamDesk has straightforward navigation logic which works well in most cases and usage scenarios. But there can be the case when you may want to change it for some reason. In that case new Navigate Action come in handy.
You can link a navigate action to any record change trigger or custom button and redirect user to another location after system perform the action.
Following redirection options are available:
|System will redirect user to the new record form. You can use navigate action assignments section to prefill form fields with some values if needed.
|System will redirect user to the edit record form.
|System will redirect user to the preview record form.
|System will redirect user to the selected custom button.
|System will redirect user to the selected document generation page.
|System will redirect user to the selected view.
|System will redirect user to the selected dashboard.
|System will redirect user to the specified custom URL. As with Call URL actions, you can use <% %> to construct it dynamically.
Edit Record, Preview Record, Custom Button and Document options require some “current” record to work properly. Depending on table selected for particular navigate action TeamDesk will use last created record or current record as and action context. If there is no table match then navigate action will be ignored.
Using navigate action you’ll be able to implement following scenarios:
- Create a custom button to open new child record form directly from parent table view without the need to open record preview form and using new button from detail records.
- Open preview form for record created with help of create record workflow action linked to the custom button.
- Create a custom button to log document generation timestamp.
- and many others.