Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Introduction

The File Display component is used to facilitate the uploading of and displaying of files in PhixFlow. It requires a specific Table type to hold the file information which can be added using an ERD where it can be associated to a table(s) via a Relationship(s).

The File Display component can be found in the Serene Grey palette under Basic Layouts and in the route of the Standard PhixFlow Labelled palette.

Initial Setup

In order to store an uploaded file the following must be completed:

  1. Directory
    1. On your server setup a directory where the files will be uploaded.
    2. In PhixFlow, from the  Administration menu, open System → Configuration.
    3. In the System Directories section, add the address of the directory setup in the first step e.g. C:\Tomcat\webapps\phixflow\data\images
    4.  Save your changes.
    5. All uploaded files will be placed in this directory.
  2. File Table
    1. On your ERD diagram, add a new  File Table
    2. If required create a relationship between this table and your desired table.
    3. Data can now be saved directly to this table or via a relationship.

Uploading Files

File Display components work in the same way as all Form Field, the must have a backing attribute and the data needs to be saved.

To setup a File Display

  1. Drag the File Display Component from the Serene Grey palette onto your screen.
  2. Add a backing attribute by right-clicking on the component and selecting Add Backing Attribute.
    1. Select the Primary Key from your File Table if you are saving directly to the table or use the relational attribute on your related table.
  3. Now with your screen lock you can drag files onto the File Display component to populate the data. This populates the field.
  4. Ensure the File Display form field is added to your save mechanism, like with all form fields, so the data is saved.  


  • No labels