TeamDesk has straightforward navigation logic which works well in most cases and usage scenarios. But there can be case when you may want to change it for some reason. In that case
Navigate action come in handy.
Please note, that the Navigate action does NOT work with Time-Dependent and Periodic triggers. Also, it does NOT work, if you add it as an action triggered by a Multi-Record button.
To create the
Navigate option in the action type list and fill out the form as described below.
General section of the form enter the action name and write notes if needed.
Navigate dropdown the following redirection options are available:
|New Record||The system redirects a user to an opened new record form. You can use the section with navigate action assignments to prefill form fields with some values, if it’s needed.|
|Edit Record||If a Create Record action (or a Update Record action) proceeds a |
|Preview Record||If a |
|Custom Button||The system will redirect a user to the selected custom button.|
|Document||The system will redirect a user to the selected document generation page.|
|View||The system will redirect a user to the selected view.|
|Dashboard||The system will redirect a user to the selected dashboard.|
|Custom URL||The system will redirect a user to the specified custom URL. As with Call URL actions, you can use <% %> to construct it dynamically.|
Table dropdown select a table where a new record should be created.
Moreover, if the
New Record option is chosen, in the
Navigate dropdown the following
After save options are available:
Navigate Back or
Navigate to record's preview. The first one allows to go back to the page where the action was activated, the second one navigates to an opened new record form, a user can make changes on this record form and can save this new record or can cancel it.
Custom Button and
Document options require some "current" record to work properly. Depending on a table selected for a navigate action, TeamDesk will use the last created record or current record as an action context. If there is no table match, then navigate action will be ignored.
Using navigate action you’ll be able to implement the following scenarios:
Create a custom button to open a new child record (related detail record) form directly from a parent table (master 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.
Let’s consider the example where a
Navigate action opens a new Booking record form related to a Tour. Say, there is One-to-Many relation, each Tour master record can be related to many Bookings detail records.
You created the "Add Related Booking" custom button with the Navigate action. The action should open a new Booking record form related to a certain Tour. So, a corresponding Tour Id value should be inserted into the "Tour" reference column field shown in a new Booking record form. To make this automatic insertion, you need an assignment, therefore when the action is created, click on the
New button in the
Fill in the "From" and "To" options to create the assignment, that will insert a value specified in the "From" field into the column chosen in the "To". As the result, the opened new record form will comprise this column value.
|From …||In the |
|To …||From the |
When finished, click
If it’s needed, you can add many assignments to one action.