Project
Purpose of use
A project is either a design concept (an internal product development initiative) or a customer-related project (delivery project), aiming to consolidate related documents and other objects into a single entity.
In an ERP system, a delivery project is typically established only after receiving an order from a customer. However, in the Flow system, a project is beneficial even during the proposal phase: proposal phase documents such as customer emails, proposal documents, and internal meeting notes can be linked to the project. This ensures that proposal phase documents are kept organized and can be referred to later if the customer proceeds with the purchase after a long period.
When integrating with an ERP system, it's worth considering the integration of project data in addition to the transfer of items and structures. This helps avoid extra work and reduces the risk of typos.
Subprojects allow the delivery project to be divided into parts. This also aids the principal's information management: the subcontractor can be given access rights only to a specific entity defined by the subproject.
In Flow's Web Interface
You can select a base project for the project, allowing Flow to copy specified documents under the project and create links to them.
You can later link documents, changes, and comments to the project.
Functions
Project objects are searched, added, and managed in the same way as all other objects.
See Object Management and its subpages
Object Search Functions
Access Rights
Project-Related Instructions
The visibility of projects and their content is managed with general access rights and project-specific role-based rights.
Project-Specific Roles and Rights
Project Import
General functions
Look at page Handling objects and its subpages.
Instructions related to the project
Tools
For project-related objects, add a connection to the project object.
Look at Connection between objects
Links to general instructions