The custom field ideology
Let's take a look at the ideology behind custom fields. We'll use adding a "Customer order" entity to the system as an example. According to the Planfix's philosophy, a customer order is a task that has additional properties. In order to get the most out of the Planfix task toolkit, we set up a separate template for orders:
- Create a new task template with the name "Customer order"
- Add the fields that are characteristic of an order (the type of product or service ordered, product size, delivery address, etc. — these will depend on your company).
- Hide fields that you don't need when working with orders.
- When a task is created using this template, employees will be able to fill in the task fields with order data.
- Down the line, order tasks can be selected using filters, displayed in reports, and displayed in Planner lists.
- Selecting by a field that's specific to orders comes in handy when you need to be sure that you're selecting only tasks for orders.
This approach gives you the ability to use one Planfix account for what are essentially multiple business processes, simply by dividing tasks into separate sections and using the tools built into the system.
Custom fields that are created can be put to use in any Planfix task where they are relevant. For example, the custom field "Vehicle number" can be used in "Client order" tasks, "Purchase" tasks, and "Technical operations" tasks. This lets you gather comprehensive statistics on the field as needed. For example, you can display the total usage of transport in a report, grouping by type of use, project, etc.