Tip: You can use filters for better 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 use the Ticket Clipboard tab
- 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/from partners
- How to manage parts
- How to show tickets on Map
- How to open tickets in a new tab
- How to use container tickets
-
-
- How to use the Optimizer
- How to schedule tickets
- How to publish/unpublish tickets
- 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/from 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
- How to clone tickets
- How to edit private notes
- How to add & remove skills
-
Admin Panel
-
- How to connect with ServiceNow
- How to create test tickets
- What are aliases?
- What does workflow mean?
- What are appearances in context of workflows?
- What are buttons in context of workflows?
- What are automations in context of workflows?
- What are guides in context of workflows?
- What are actions in context of workflows?
-
- What is the Process menu?
- What does workflow mean?
- What are appearances in context of workflows?
- What are buttons in context of workflows?
- What are automations in context of workflows?
- What are guides in context of workflows?
- What are actions in context of workflows?
- How to create & edit projects
- How to create & edit custom forms
- How to create & edit lists
- How to customize the Customer Portal
- 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 value sets
- How to create & edit SLA Profiles
- How to repair tickets with Ticket Workflow Monitoring
-
Fieldcode FMA app
-
- Fieldcode FMA app
- How to download the Fieldcode FMA app
- How to login
- 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
-
-
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 Admin Panel go to Process → Conditions
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 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 or hours or days in the Warning timer field.
- Insert a time in minutes or hours or days in the Critical timer field.
- Decide if you want to apply the SLA Profile calculation for your condition.
Please note that you can apply the SLA Profile calculation for each condition individually. - Select a Monitored Field from the drop-down. The timers will use this field as a reference.
Please understand the monitored fields first and how conditions behave, before configuring your condition. - (Optional) Make your condition dependent on ticket status.
- Click Save.
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 can use minutes or hours or days as timer values.
Please stick to the condition behavior rules when configuring the values.
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 Work Place). Indications are visible in the Info/Alert row of the Ticket Pool.
If user-defined work hours are configured for the calculation (Users -> Working Hours tab) the user-defined work hours will be the basis for calculations.
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).
If the admin has an SLA Profile configured (Process -> SLA Profiles) the SLA Profile will be the basis for calculations.
Example: Warning timer 15 minutes, Critical timer 30 minutes. Warning is due on Friday 14:50 and Critical is due on 15:05. As the Critical timer exceeds the SLA Profile operational time, the critical warning will be displayed on Monday at 07:05 instead of 15:05.
5 out of 5 stars
1 rating
5 Stars | 100% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |