Objects: Difference between revisions
From Planfix
No edit summary |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 16: | Line 16: | ||
In every account, there is at least one object. Typically, it represents the standard form and life cycle of a task in its most common comprehension — as a task: | In every account, there is at least one object. Typically, it represents the standard form and life cycle of a task in its most common comprehension — as a task: | ||
https://s.pfx.so/pf/ | https://s.pfx.so/pf/pQ/YIwxwu.jpg | ||
If you need to add a new entity to Planfix, for example, a Deal, Meeting, or Knowledge Base — create a new Object. | If you need to add a new entity to Planfix, for example, a Deal, Meeting, or Knowledge Base — create a new Object. | ||
| Line 32: | Line 32: | ||
[https://www.youtube.com/watch?v=bqvLtfDeEyg Watch on YouTube] | [https://www.youtube.com/watch?v=bqvLtfDeEyg Watch on YouTube] | ||
In the [[Settings in user cards| | In the card settings of [[Settings in user cards| employees]] or [[External users|external user contact with Planfix access]], you can [[Default task template|choose a default Object (task template)]] that will be used when creating tasks. | ||
== Important == | == Important == | ||
The object is a relatively new construct for Planfix. Before | *The object is a relatively new construct for Planfix. Before it, adding new entities and configuring business processes was done by separately creating [[Task templates]], which were responsible for the form, and [[Task processes]], and contained sets of statuses, scripts, and buttons. | ||
*The old way of setting things up is left untouched for backward compatibility, and you may encounter references and training materials that demonstrate its use. | |||
The old way of setting things up is left untouched for backward compatibility, and you may | *However, if you want to work more comfortably and have access to all Planfix features, we recommend using objects. | ||
== Go To == | == Go To == | ||
*[[Feature Description]] | *[[Feature Description]] | ||
Latest revision as of 12:05, 1 September 2025
Object — is a digital twin of a real-world physical object or process in Planfix.
Each object describes a particular type of task that will be processed in Planfix. Examples of objects:
- Contract
- Meeting
- News
- Knowledge Base Article
- etc.
In every account, there is at least one object. Typically, it represents the standard form and life cycle of a task in its most common comprehension — as a task:
If you need to add a new entity to Planfix, for example, a Deal, Meeting, or Knowledge Base — create a new Object.
Creating an Object
To add a new object to Planfix, go to "Account Management" — "Objects".
An object in Planfix has:
- Object form — a set of Fields that you can use to describe the actual properties of a physical object or process. For example, for a contract, you will most likely need to enter the customer's name and budget into the form; for a meeting, you need to enter the time, place, and participants. For a knowledge base, you need to enter tags.
- Set of statuses — a list of status state that the object can be in. For example, for a contract — negotiation, contract completion, awaiting payment.
- Automatic scenarios — triggered by changes in field values.
- Buttons — automate a set of actions and are available in certain states.
Video tutorial
In the card settings of employees or external user contact with Planfix access, you can choose a default Object (task template) that will be used when creating tasks.
Important
- The object is a relatively new construct for Planfix. Before it, adding new entities and configuring business processes was done by separately creating Task templates, which were responsible for the form, and Task processes, and contained sets of statuses, scripts, and buttons.
- The old way of setting things up is left untouched for backward compatibility, and you may encounter references and training materials that demonstrate its use.
- However, if you want to work more comfortably and have access to all Planfix features, we recommend using objects.