Actions
Navigation: -> Actions
Action URIs are a powerful tool for performing - external - actions on tasks and appointments (among others). By constructing a link with placeholders, you create a reusable template that can be executed by any task or appointment. Examples of action URIs include sending out e-mails or opening the card in the back office system directly.
Action URIs in the planning view
There are four locations in which action uris are available:
- Map
- New appointments
- Existing appointments
- Open tasks
These values correspond to the options in the Type column.
The actions grid
This view allows the management of those action links:
Zooming in on the image above, these are two examples of action uris:
| Type | Description | Source App | Source Type | Url |
|---|---|---|---|---|
| Planboard | Register new Absence | CRONUS2017 | HR | dynamicsnav://DIMEDM01:7046/DynamicsNAV100/CRONUS%20International%20Ltd./runreport ?report=2087625 &filter=DSApp.Source Type:#SOURCETYPE# &filter=DSApp.Database Action:#DATABASEACTION# &filter=DSApp.Start:#START# &filter=DSApp.End:#END# &filter=DSApp.Resource Report Filter:#RESOURCE# |
| Appointment | Send E-mail | CRONUS 2017 | HR | dynamicsnav://DIMEDM01:7046/DynamicsNAV100/CRONUS%20International%20Ltd./runreport ?report=2087625 &filter=DSApp.Source Type:#SOURCETYPE# &filter=DSApp.Database Action:#DATABASEACTION# &filter=DSApp.Appointment Id:#APPOINTMENTID# &filter=DSApp.Start:#START# &filter=DSApp.End:#END# &filter=DSApp.Resource Report Filter:#RESOURCE# |
The type column refers to the scope of the action. The entity and the component will determine which action uris are applicable. For instance, action uris for the planboard will never be shown in the open tasks list. For instance, when opening the context menu in the scheduler component, the "Register New Absence" action is shown:
Likewise for the appointment type. Only the action uris within the right context will be considered.
The description column is the text that will be displayed.
The source app and source type columns provide extra filters. All job-derived entities (tasks and appointments) can be traced back by a source app and type. An action uri will only be enabled when a task or appointment matches these values - and is operative in the right context.
Constructing an action URI
Let's deconstruct the example from above:
dynamicsnav://DIMEDM01:7046/DynamicsNAV100/CRONUS%20International%20Ltd./runreport
?report=2087625
&filter=DSApp.Source Type:#SOURCETYPE#
&filter=DSApp.Database Action:#DATABASEACTION#
&filter=DSApp.Start:#START#
&filter=DSApp.End:#END#
&filter=DSApp.Resource Report Filter:#RESOURCE#
There is not much to report other than to note that this is a URI with a Dynamics Navision protocol. Executing such a URL will open the client directly with the query string providing all kinds of information. The actual contents are not important at this point. The placeholders make this such a flexible and powerful feature. A placeholder is defined by a variable name surrounded by hashtags, like #SOURCETYPE# or #RESOURCE#. For the moment, there are only a limited amount of placeholders, which may change in the future to make it even more flexible.