Fieldcode Manual

Tip: You can use filters for better results

Every ticket and appointment in Fieldcode follows a workflow. Fieldcode provides a default workflow, so you only need to configure this page if you want to change the actions available to users or automate tasks that are currently performed manually.

At each step of the workflow, the system determines which actions are available and displays them as buttons. For example, a dispatcher working with a new ticket may see the Schedule button, while an engineer who has arrived on site may see Start Work and Complete. Selecting an action moves the ticket or appointment to the next step and can also trigger automatic actions, such as changing a status, sending an email to the customer, or updating a field.

Because the workflow controls which buttons appear and when, everyone follows the same process, and the routine steps happen on their own.

Access to Fieldcode features depends on your pricing plan. See the plan comparison for a full overview of what each plan includes.

 Workflow Permissions:

You can configure the permissions for the Workflow Page via:
Permissions/Select Role/Security Resource/Admin panel/Navigation menu: Automations/Page: Workflows

Column Customization:

  • By default, not all information is displayed inside the workflow table because not every user may require it. Therefore, if you want to invest in a deeper understanding of workflows, we recommend turning all columns on.
  • You can adjust the columns to your needs by clicking on the column button inside the Workflows list.
Tracing Tickets/Objects:
 
In the upper-right corner, you can find the Trace button. Trace allows you to locate the which workflow an object is running on, which version of it, and which node the object has currently reached. Use this button to locate any object in Fieldcode by its unique ID.
  1. Click on the Trace button in the upper-right corner of the workflows list.
  2. Select a object.
  3. Enter a object reference. For example, this could be the CNI of a ticket. The information found will be displayed as shown in the screenshot below.

  4. This way, you can troubleshoot individual tickets.
  •  

These are the default workflow objects:

Identifying iconObject nameWorkflow NameDescription
InterventionFMAFMA appointment related workflow object is containing the default FMA appointment flow.
ItemFMA_ITEM FMA Parts related workflow object, is containing the FMA parts flow.
PUDO AppointmentFMA_PUDOPUDO related workflow object, is containing the the PUDO appointment flow + FMA Settings.
ResourceFMA_RESOURCEFMA User related workflow object, is containing the My Day flow + FMA settings.
TicketBASICThe default ticket related workflow object is containing the default ticket workflow.
Need Help?

Our solution engineers can help you design workflows tailored to your business needs. Contact Fieldcode Support for assistance.

Yes, a workflow can be assigned to more than one project. 

  • Use the draft version and test it in a staging environment (if possible).
  • Test it against objects (can be done inside the Workflows Designer directly).

The button or action will not be shown or executed.

Was this topic helpful?
5 out of 5 stars

1 rating

5 Stars 100%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
How can we further improve this topic?
Please provide the reason for your vote. This will help us improve this topic.
Navigation