Tip: Start typing in the input box for immediate search results.
-
Quick Start
-
- What is Fieldcode?
- Definitions
- What are tickets, projects and workflows?
- How to log in to Fieldcode
- What is the Fieldcode Support Panel?
- What are components?
- What are views?
- Ticket statuses and their meaning
- Ticket colors and their meaning
- Map symbols and their meaning
- Frequently Asked Questions
- Setting up Fieldcode
-
-
Release Notes
-
Short Overview
-
Fieldcode Work Place
-
-
- How to schedule tickets
- How to search for tickets
- How to expert-search for 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 spare parts
- How to show tickets on Map
- How to use the Clipboard
- How to open tickets in a new tab
- How to use container tickets
-
-
- How to use the Optimizer in the Timeline
- How to schedule tickets
- How to publish tickets to engineers from the Timeline
- How to lock/unlock tickets
- 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 use the Interaction buttons
- How to assign/unassign tickets to partners
- How to manage spare parts
- How to use the Workflow buttons
- How to use the Ticket info button
- How to use the Email button
- How to use the Comment button
- How to schedule tickets
- How to use the Remove Pending button
- How to cancel a ticket
-
Fieldcode Admin Panel
-
- What is the Process menu?
- What is the Workflows menu?
- How to create & edit projects
- Automated Actions in the overview
- How to setup custom Automated Actions
- How to setup pre-configured 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
-
- Articles coming soon
-
Fieldcode Mobile App
-
Fieldcode Customer Portal
How to create & edit a new custom Automated Action
- Inside the Fieldcode Admin Panel click on the plus button to open the Automated Action form.
- Select Create a Custom Automated Action from the Available options dropdown.
- Fill in the Basic, Filters and Action tabs.

1. Basic tab
- Decide if your new custom AA should be set to active in the system.
- Insert a name for your new or existing custom Automated Action.
- Select a project from the drop-down, where the custom Automated Action should apply.
- (Optional) Insert a description for your new or existing custom Automated Action (eg. what exactly it does).
- Select a monitorable field from the drop-down that triggers the Automated Action, if the value inside this field changes.
- Click Save.

2. Filters tab
In order for custom Automated Action to work, you need to add one or more filters to determine the tickets, where an Automated Action needs to be initiated.
Filters: Allows fine-tuning criteria for AA using comparison and logical operators.
Condition: Defines a condition for your filter criteria.
Operator: Compares the condition with the comparison (IS EQUAL TO, IS NOT EQUAL TO, IS LIKE, IS NOT LIKE, IN).
Comparison Value: Defines with which value the condition is compared.
Connector: Allows you to combine a monitored field with another monitored field (AND, OR)

3. Action tab
- Select an action from the drop-down.
- Click on Add.
- Edit your desired action or actions.
- Click on Save.

Action types explained
Email action
This action will send out emails to customers.
Email action | Field description |
---|---|
Action | Displays the selected action type |
From | Insert from which email address the email should be sent |
To | Insert to which email address or addresses the email should be sent |
CC | Customize to whom you want to CC ("Carbon Copy") the email |
BCC | Customize to whom you want to BCC ("Blind Carbon Copy" the email |
Subject | Insert the email subject |
Body | Insert the email content |
Call external API action
This action will send API calls/data to other systems.
Call API action | Field description |
---|---|
Action | Displays the selected action type |
Request type | GET/PUT/POST/PATCH/DELETE |
URL | URL |
Headers | Headers |
Header field | Key |
Header value | Value |
Include OAuth token? | Yes or No |
Request body | Request body |
Create ticket info action
This action will create Ticket info in the Fieldcode work place, which can be customized with Acknowledge and Resolved fields.
Create ticket info action | Field description |
---|---|
Action | Lets you select the desired action |
Type | Lets you select the desired type of action |
Text for ticket info | Lets you insert the desired ticket info text |
Acknowledged tick | Decide if the ticket info should contain a acknowledged tick |
Resolved tick | Decide if the ticket info should contain a resolved tick |
Send SMS action
This Action will send out an SMS to customers.
- Insert the phone number(s) or alias of the recipients.
- Double-check the inserted recipients in the chip list. You can delete recipients directly by clicking on the x on a chip.
- Insert the message for the recipients.