Fieldcode Manual

Tip: You can use filters for better results

Inside the Workflow menu you can view all workflows for your account in detail. 
We call the lifecycle of the ticket the workflow. The workflow reflects all possible steps available for a ticket and determines which actions are available. Initially, we provide you with a basic workflow that covers all standard Field Service Management use cases and helps you understand what is going on in every phase of the ticket.
With future Fieldcode updates, you can expect to one day fully customize and create your own workflows which will give you an immense new layer of flexibility. 

Inside the Admin panel go to Process → Workflows

What is a Workflow?

The lifecycle of a ticket is called workflow.

Learn more about workflows here
Worfklows only move horizontally, not vertically

Knowing that workflows only move horizontally back and forth is essential for understanding how workflows work at all. The Workflow path view section lists all the paths in a alphabetical order (think of the file structure of folders on your desktop for a better picture) with all their nested items. It is important to know however that a workflow doesn't follow a path in alphabetical order, it rather starts from a path point from right to left or left to right (horizontally).

The workflows menu contains all configured workflows in the first list view and all the nodes of a workflow when you click on a particular workflow.

The first thing you see when you open the Workflow menu is all the workflows configured for your account. When you click on a workflow, you open the workflow path overview, which shows all the paths your workflow takes and allows you to understand a workflow in detail.
  • Workflow Parameters tab: The parameters tab allows you to set basic options, such as how the currently selected workflows is named, which version of the workflow you are currently watching, the object type of the workflow and eventually a detailed description of the workflow.

  • Workflow Treeview/Workflow Listview: You can check all the configured workflow paths for a selected workflow in this section.

  • Workflow node search: Gives you to the option to search for a specific workflow node by entering a search keyword.

  • View changer: Gives you the option to change between a workflow node tree view and workflow node list view. The Workflow path tree view gives you a better understanding of how a selected workflow can move around by displaying children, siblings etc.

  • Workflow node view: You can check all the workflow paths of a selected workflow, configured settings for each workflow node, workflow node creation dates, workflow node creators, workflow node last edit date and times, and which user last edited a certain workflow node in this section.

  • Settings tab: The setting tab displays the path of the selected item, allows you to initiate a jump to another node/step, can display the button label, can display the form, and can display the alert. Furthermore, you can check Appearances, Buttons, Automations, Guides, and Actions of a workflow node.

  • Translations tab: The translation tab gives you the option to edit workflow path localizations for different languages. What you can do with it for example, is to add translations for the history tab as when a workflow changes in some way it is always displayed inside the History tab.

  • Audit info tab: The audit info tab summarizes by whom a workflow path was created initially and who last edited it.

A workflow node/step is a reference point on the workflow path (eg. a ticket status) which can be customized in various ways (Coming with later updates).

The InterventionWait node which has the Basic Workflow node as a start point and connects also to the CancelAppointment node.

As mentioned above the workflow always moves horizontally back and forth (never vertically) between workflow nodes/steps.
Understanding this is crucial when it comes to defining oww workflows, which will be feature that is planned to be released in later versions of the Workflow Designer.

Tree view with a horizontally moving workflow.
Workflow objectIcon nameDescription
ResourceEngineer related workflow object, is intended for engineer form types.
InterventionIntervention related workflow object, is intended for intervention form types.
TicketTicket related workflow object, is intended for the ticket form type.
ItemParts related workflow object, is intended for the part form type.
PUDO AppointmentPUDO related workflow object, is intended for PUDOP appointment form type.
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 submit the reason for your vote so that we can improve this topic.
Navigation