Welcome to the Fieldcode Manual

Tip: Start typing in the input box for immediate search results.

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

  1. Click on the plus button to open the New condition form (or click on an item in the list to edit it).
  2. Decide if your new or existing condition should be set to active in the system.
  3. Insert a name for your new or existing condition.
  4. (Optional) Insert a description for your new or existing condition.
  5. Select a project from the drop-dow for which the condition should be applied.
  6. Insert a time in minutes in the Warning timer field.
  7. Insert a time in minutes in the Critical timer field.
  8. Select a Monitored Field from the drop-down. The timers will use this field as a reference.
  9. (Optional) Make your condition dependent on ticket status.
  10. Click Save.
Form fieldsDescription
Active toggleSelect whether your new condition should be set to active or not
Description(Optional) Insert a description of your new condition
Warning timerInsert a time frame (in minutes) after the warning state triggers
Critical timer Insert a time frame (in minutes) after the critical state triggers
Monitored fieldThe condition time frame starts from this selected time event
Ticket Status(Optional) Make your condition dependent on a ticket status
Monitored field nameExplanation
Fixed appointment end timeEg. 24th Dec. 2020 17:00 - Time stamp of fixed ending appointment time. (Agreement with the customer!)
Fixed appointment start timeEg. 24th Dec. 2020 08:00 - Time stamp of fixed beginning appointment time. (Agreement with the customer!)
Due dateEg. 24th Dec. 2020 23:59 - Time stamp of ticket's due date. The ticket should be solved before this time.
Ticket creation timeEg. 24th Dec. 2020 10:01 - Time stamp of when the ticket was created
Ticket status entry timeEg. 24th Dec. 2020 10:03 - Time stamp of when a ticket has entered a selected status
Dispatch appointment end timeEg. 24th Dec. 2020 13:15 - Time stamp of dispatch appointment end time. (Agreement with the engineer!)
Dispatch appointment start timeEg. 24th Dec. 2020 12:15 - Time stamp of dispatch appointment start time. (Agreement with the engineer!)
Monitored fieldIllustrationExplanation
Ticket creation timeCounts outgoing from the creation time. To make the warning condition appear first, set the critical time higher than the warning time.
Ticket status entry timeCounts outgoing from the status time. To make the warning condition appear first, set the critical time higher than the warning time.
Fixed appointment start timeCounts 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 timeCounts 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 timeCounts 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 timeCounts towards the dispatch appointment end time. To make the warning condition appear first, set the warning time higher than the critical time.
Due dateCounts towards the due date. To make the warning condition appear first, set the warning higher than critical.

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.

Here’s how to do it:

  1. Open an existing condition from the list by clicking on the condition itself.
  2. Go to the Advanced tab.
  3. Add one or more extensions according to your use case.
Example 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.
Was this article helpful?
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents