Before you start any PhixFlow project, it is important to take time to understand your data and what you need to do with it.
For this example, a sales team is using an Excel spreadsheet to manage a list of Business contacts. The data represents business customers (location, turnover) and people (names and addresses). The spreadsheet has the following tabs.
Businesses tab:
Contacts tab:
The data in the two tabs is connected by the the business name.
customer businesses and associated contacts. You want to make it accessible and maintainable by more than one person. You also want to add some simple CRM functions, so that you can for example, to add descriptions about the business.
Placeholder Video
Multimedia | ||
---|---|---|
|
How To
Expand |
---|
The first step is to create a PhixFlow application. Everything you create will belong to this application.
<video>
- In the repository, right-click on Application and select
.Insert excerpt _add _add nopanel true - PhixFlow opens a properties tab for the application. Enter the name:
Unique-name
- Click
.Insert excerpt _save _save nopanel true - When prompted to load the application, say yes.
Expand | ||
---|---|---|
| ||
Scroll down the properties tab. If you scroll down to the Grid section, you can see that there is a Grid Header Style. This means that whenever PhixFlow displays data in a grid (table), the table header will always have the same colour, font size and style. You can see there are lots of options where you can set data format and style defaults for the application. If none are set here, then PhixFlow uses defaults that are set for the system. This means that, all your applications have a consistent base line for the data and its styles, or you can apply defaults per-application, if you want them to look different. |
...
Expand | ||
---|---|---|
| ||
Before you start any PhixFlow project, it is important to take time to understand your data.
Remember that you can:
You can represent your data and requirements in an Entity-Relationship Diagram (ERD); see Wikipedia. It can help you to understand the data entities, their attributes and relationships. An ERD shows you the data architecture. As well as clarifying the data you already have and what you need to calculate, an ERD can help you identify:
Within PhixFLow it is a good idea to be consistent, at a minimum within an application. You can use prefixes to distinguish CRUD or control data from static data. During the planning phase you can set up a naming policy. | ||
Expand | ||
| ||
Before you start any PhixFlow project, it is important to take time to understand your data. . |
...