Welcome to the Fieldcode Manual

Type a term in the box to instantly list helpful topics. Category filters help to narrow down search results.

Last updated:

How to use the Quicklaunch component

Copy the URL link to this section to share

When it comes to Field Service, ticket processing and ticket tracking are important tasks that need to be resolved. This is usually achieved by back-office persons.
These duties include tasks like scanning documents after the ticket has been created, tasks like scanning documents after the ticket has been reported, and more tasks where bulk-action and bulk-editing is required to fulfill the requirements. 

The Quicklaunch component is capable of helping back-office persons with those tasks as it features the required functionality.

The Quicklaunch component displays the current active form, which is based on the status of the ticket. Also supported are Custom Forms.

USE CASE EXAMPLE

You are a back-office agent, that needs to prepare tickets from the "General tab" to fulfill a given company standard. Let's assume that the company standard is that every newly created ticket requires an internal code (provided by the back-office person) in the problem description of the ticket. This code is used by engineers to quickly process and solve problems. This is achieved by an internal document that only the engineer can access.
You, the back-office agent, would preferably use a view where the Ticket Pool component and Quicklaunch component are side-by-side.

  1. The back-office person clicks on the Views editor inside the Fieldcode Work Place.
  2. The back-office person creates a view with the Ticket Pool and Quicklaunch.
  3. The back-office person saves this view with the name “Quicklaunch”.
Example of a Quicklaunch view that can fulfill the needs of back-office agents.

The back-office agent now wants to edit ticket details one-by one to fulfill his job.

  1. The back-office agent clicks on the first ticket.
  2. The back-office agent scrolls to the problem description.
  3. The back-office agent enters the new required details.
  4. The back-office agents proceeds in the same way with the next tickets.
Example of an back-office agent editing tickets quickly one-by-one with Quicklaunch.
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