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
How to configure conditions
Conditions can be set up and determined according to the project’s requirements. When a ticket reaches a defined condition (status) that you have configured with the help of the monitored field, warning signs and/or critical signs can be triggered for the ticket inside work place. To decide when the condition should trigger, you configure thresholds.
Inside the Fieldcode Admin Panel go to Process → Conditions
How to create & edit conditions
- Click on the plus button to open the New condition form (or click on an item in the list to edit it).
- Decide if your new or existing condition should be set to active in the system.
- Insert a name for your new or existing condition.
- (Optional) Insert a description for your new or existing condition.
- Select a project from the drop-dow for which the condition should be applied.
- Insert a time in minutes in the Warning timer field.
- Insert a time in minutes in the Critical timer field.
- Select a Monitored Field from the drop-down. The timers will use this field as a reference.
- (Optional) Make your condition dependent on ticket status.
- Click Save.

Understanding the condition form
Form fields | Description |
---|---|
Active toggle | Select whether your new condition should be set to active or not |
Description | (Optional) Insert a description of your new condition |
Warning timer | Insert a time frame (in minutes) after the warning state triggers |
Critical timer | Insert a time frame (in minutes) after the critical state triggers |
Monitored field | The condition time frame starts from this selected time event |
Ticket Status | (Optional) Make your condition dependent on a ticket status |
Understanding the monitored fields
Monitored field name | Explanation |
---|---|
Fixed appointment end time | Eg. 24th Dec. 2020 17:00 - Time stamp of fixed ending appointment time. (Agreement with the customer!) |
Fixed appointment start time | Eg. 24th Dec. 2020 08:00 - Time stamp of fixed beginning appointment time. (Agreement with the customer!) |
Due date | Eg. 24th Dec. 2020 23:59 - Time stamp of ticket's due date. The ticket should be solved before this time. |
Ticket creation time | Eg. 24th Dec. 2020 10:01 - Time stamp of when the ticket was created |
Ticket status entry time | Eg. 24th Dec. 2020 10:03 - Time stamp of when a ticket has entered a selected status |
Dispatch appointment end time | Eg. 24th Dec. 2020 13:15 - Time stamp of dispatch appointment end time. (Agreement with the engineer!) |
Dispatch appointment start time | Eg. 24th Dec. 2020 12:15 - Time stamp of dispatch appointment start time. (Agreement with the engineer!) |
Understanding the condition behavior
Monitored field | Illustration | Explanation |
---|---|---|
Ticket creation time | ![]() | Counts outgoing from the creation time. To make the warning condition appear first, set the critical time higher than the warning time. |
Ticket status entry time | ![]() | Counts outgoing from the status time. To make the warning condition appear first, set the critical time higher than the warning time. |
Fixed appointment start time | ![]() | Counts outgoing from the fixed appointment start time. To make the warning condition appear first, set the critical time higher than the warning time. |
Fixed appointment end time | ![]() | Counts towards the fixed appointment end time. To make the warning condition appear first, set the warning time higher than the critical time. |
Dispatch appointment start time | ![]() | Counts outgoing from the dispatch appointment start time. To make the warning condition appear first, set the critical time higher than the warning time. |
Dispatch appointment end time | ![]() | Counts towards the dispatch appointment end time. To make the warning condition appear first, set the warning time higher than the critical time. |
Due date | ![]() | Counts towards the due date. To make the warning condition appear first, set the warning higher than critical. |
How to extend conditions
You are able to extend conditions with additional checks by using the Advanced tab inside the Condition editing form. Extending a condition means giving it more/other triggers to actually initiate. For example, you can run additional checks to monitor the SLA field and/or Subcategory field with personalized warnings and critical timers.
- Open an existing condition from the list by clicking on the condition itself.
- Go to the Advanced tab.
- Add one or more extensions according to your use case.
You have a condition that gives out warning and critical alerts in Work Place when a ticket sits too long in Appointment status. You now want to extend that condition for tickets of a certain project to also consider Service Level Agreements like being worked on after one business day at the latest. Therefore you would add that condition by toggling the SLA switch on and selecting 1BH. Then you set the warning timer and the critical time to your wished thresholds. You could also narrow that particular condition down to also consider only a certain subcategory. With this precise configuration, your condition would trigger with the settings in the Basic as a base always and also in case the conditions of the Advanced tab are met.

Where and when are conditions displayed?
Conditions are used for highlighting tickets. Therefore they are indicated by warning and critical symbols inside the Ticket Pool.
Configured conditions are visible in the header of Ticket Details, in the Condition and Indication tabs (under the Overview tab in the Ticket Details), and in the Ticket Pool (all in Fieldcode Work Place). Indications are visible in the Info/Alert row of the Ticket Pool.
User-defined work hours are used for the calculation (Users -> Working Hours tab).
Example: User John McNeill works from 09:30 to 17:30 from Monday to Friday. The condition (eg. warning/critical) is set to 720 minutes (12 hours).
The ticket is placed at 10:00 o'clock. 17:30 is the "cut-off" time. The pre-calculations continue from the next day on to reach the 12 hours. The ticket displays the condition (eg. warning/critical) at 10:30 o'clock the next day. Bank holidays are considered in the calculation (if configured), and so are the weekend days (if configured).
5 out of 5 stars
1 rating
5 Stars | 100% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |