Category filters can help you narrow down search results
-
Latest News
-
Quick Start
-
Work Place
-
-
- How to schedule tickets
- How to search for tickets
- How to query tickets
- How to filter for tickets
- How to grab/ungrab tickets
- How to link & unlink components together
- How to download ticket data as a excel sheet
- How to copy filters/queries for colleagues
- How to email filters/queries to colleagues
- How to assign/unassign tickets to partners
- How to manage parts
- How to show tickets on Map
- How to use the ticket clipboard
- How to open tickets in a new tab
- How to use container tickets
-
-
- How to use the Optimizer from the Timeline
- How to schedule tickets
- How to publish tickets to engineers from the Timeline
- How to lock/unlock tickets
- How to lock/unlock engineers
- How to manually reschedule PUDOs
- How to show tickets on Map
- How to manage availabilities
- How to manage subgroups
- How to display an additional time zone
- How to move tickets back to the Ticket Pool
-
-
-
- How to manage parts
- How to assign/unassign tickets to partners
- How to use the Interaction buttons
- How to use the Workflow buttons
- How to use communications
- How to schedule tickets
- How to edit ticket details
- How to cancel a ticket
- How to use the Remove Pending button
- How to report a ticket
- How to create intervention infos
- How to create intervention reports
- How to cancel an appointment
-
Admin Panel
-
- What is the Process menu?
- What is the Workflows menu?
- How to create & edit projects
- How to create & edit automated actions
- How to create & edit conditions
- How to create & edit indications
- How to set up email templates
- How to create & edit ticket durations
- How to create & edit custom fields
- How to create & edit custom forms
- How to create & edit value sets
- How to create & edit SLA Profiles
- How to move stuck tickets via Ticket Workflow Monitoring
-
FMA
-
- Fieldcode App (FMA)
- How to download the Fieldcode App
- How to login to Fieldcode
- How to configure multiple accounts
- How to enable/disable notifications
- How to change the theme
- How to log work times
- How to synchronize tickets
- How to navigate to appointments
- How to log drive times & drive breaks
- How to inform dispatchers
- How to view archived appointments
-
-
FMA 1
-
Customer Portal
What are aliases?
Aliases are used in certain parts of the applications to automatically pull specific ticket details out of the system so that manual data input is not required anymore.
Aliases are placeholders and will be replaced with the corresponding ticket details once the action is triggered.
- Aliases can be used when configuring Automated Actions, when configuring email templates.
- The alias list only appears context-sensitive and only where the usage of aliases actually makes sense.
- You may see for example a different alias list popping up in email templates, than in Automated Actions.
- Triggering the alias list: This is done by typing @ in a text field, where aliases can be used.
- The aliases list will then appear and you can decide which alias to use.
- When the content is sent out, the placeholder will be replaced with actual ticket details.

Alias examples
You can use aliases to pull data from the Ticket Details, so you don’t have to enter data manually every time.
For example, this may provide as useful the “Send email” action inside Automated Actions.

-
The affected email alias will use ticket details from the ticket to fill in the data. So instead of the Alias @affectedEmail the actual recipient value of the ticket will be auto-filled. As aliases are dynamic and tied to the ticket, the data will auto-replace accordingly.
-
Aliases can be also used in the Subject field. They will be suggested context-based by the system.
-
Aliases can also be used inside the Body field. They will be suggested context-based by the system. In this example the dispatched from and dispatched to times are used to dynamically inform the end customer.
Another helpful usage of aliases is when writing one-time emails to customers, which are not automated yet for any reason:

-
The affected email alias will use ticket details from the ticket to fill in the data. So instead of the Alias @affectedEmail the actual recipient value of the ticket will be auto-filled. As aliases are dynamic and tied to the ticket, the data will auto-replace accordingly.
-
Aliases can be also used in the Subject field. They will be suggested context-based by the system.
-
Aliases can also be used inside the Body field. They will be suggested context-based by the system. In this example the dispatched from and dispatched to times are used to dynamically inform the end customer.
-
The Preview button lets you check how the final email that is actually sent out will look like.
This is how the actual sent out email will look like:

-
After clicking on the Preview button you can double check which values are actually used for the alias placeholders. In our example you can see that every value has been taken over properly, therefore we are ready to send out this email by clicking on the Send button.
0 out of 5 stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |