Welcome to the Fieldcode Manual

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

Last updated:

What are projects?

Copy the URL link to this section to share

Each ticket in your Fieldcode work place belongs to one project, whereas you are allowed to create as many projects as required to display and structure your delivery. Projects can reflect contracts with different customers to split tickets by category or other features. That depends on your preferences and use cases. Nonetheless, splitting tickets by customer gives you the best way to analyze KPIs and keep Service Level Agreements in focus.

How to create & edit projects

Copy the URL link to this section to share
  1. Inside the Fieldcode admin panel go to Process -> Projects
  2. Click the plus button right next to the search bar to add a new project.
  3. Fill in or edit the following tabs: Basic, Data security.

1. Basic tab

Copy the URL link to this section to share
  1. Decide if your new or existing project should be set to active in the system.
  2. Insert a name for your new project. The name of existing projects cannot be changed afterward.
  3. Select a workflow from the drop-down that you want to use for your project.
    By default, you can choose between Basic I and Basic II.
    (For beginners, we suggest: Basic I).
    Basic I: Default ticket statuses
    Basic II: Default ticket statuses + an additional report/validation step.
  4. Select a Ticket source for your new or existing project.
    By default, you can choose between Manual & Interface and Interface only
    (For beginners, we suggest: Manual & Interface).
    Interface + Manual: Tickets can be created inside the Fieldcode work place and an external interface for having tickets delivered into the system can also be used.
    Interface only: Tickets can only be created by an external interface.
  5. Select if your new or existing project should consider a skill-based selection of engineers.
  6. Select if the Parts tab should be available for your new or existing project.
  7. Select if tickets for this project are not allowed to violate the LSDT.
    LSDT violation means that tickets are allowed to expire the LSDT.
  8. Click Save.

2. (Optional) Data security tab

Copy the URL link to this section to share

The anonymization functionality allows you to overwrite certain data fields inside Fieldcode work place after the retention days have passed to give you the option to comply with GDPR and data security regulations.

The blind text box can be left blank if you do not want to think about a word or phrase and it will still show no text.

  1. Select if you want to enable data anonymization for this project by turning the toggle right.
  2. Insert a number of days in the retention days window if you want to set an offset of days until resolved tickets should get anonymized.
  3. Select the fields you want to anonymize by toggling the items you want to anonymize to the right.

Let’s say you want to anonymize the Affected person’s company and the Affected person’s primary phone number.

What you would do is toggle those two toggles to the right and insert a blind text in the right blind text box with a text that should be displayed instead (e.g. PRIVATE).

The blind text box can be left blank if you do not want to think about a word or phrase and it will still show no text.

3. (Optional) Enduser not reached tab

Copy the URL link to this section to share

(Optional) Enable Strike Count

The strike count assists you to apply business conformities into the system and perfectly assists dispatchers in their daily job.

The strike is visible for the dispatcher while scheduling tickets and while clicking Callback Required and while reaching the limit.

  1. Toggle the switch to the right.
  2. Insert the number of strikes (Default: 3) that should be applied for this project.
  3. (Optional) Set a message that should appear for the dispatcher when the count reaches the limit.
  4. (Optional) Translate this message to other languages.
  5. Click Save.

(Optional) Enable Waiting Duration

You can configure a custom waiting duration to establish how long tickets should be moved to the Clipboard tab.
After the waiting duration has passed for the ticket, it will move back from the Clipboard tab to the Dispatch tab.

The Waiting Duration is visible for the dispatcher while scheduling tickets and while clicking Enduser not reached.

  1. Toggle the switch to the right.
  2. Insert a duration. You can set minutes, hours, and even days.
  3. Click Save.

4. (Optional) Value Sets tab

Copy the URL link to this section to share

If your company uses custom values you have the option to activate and deactivate them from the Projects tab. This can also be done directly in the Value Sets and the functionality behaves the same.

  1. Activate or deactivate values to your specific project needs by flipping the Active toggle accordingly.
Was this article helpful?
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Tags:
Table of Contents