Introduction

Users can upload their own files into PhixFlow using actions. This can be done using either a 

• Upload images/files and store them as a record. - Store them of the details of where to access them ?as a record.
• Upload files to be used in an analysis model. These files can be made available for users to download.

Example

In a simple contacts application, it is possible using file uploads to

• Allow an application user to upload their own image against a contact:
  
  Image Modified
  
• Bulk upload Excel files containing multiple contacts to appear within an application.
• Download and files uploaded at a later date. - Note sure this reds as intended? At a later date? Message me about this.files stored on the server. These could be previous file uploads. 

Solution

Images and files are stored on the server when uploaded by a file collector. These files are placed into a standard directory and need to be moved into an appropriate directory which can be accessed by the front end. To find out how to create these directories on the server, see XXX.

Once the new directory has been created, an analysis model is required that contains a File Collector and a Table. An action will then run this model, the user will upload a file, the file collector will move it to the correct folder and the URL to access this file will be stored in an attribute on the table. - can you list this as bullet point steps. Maybe tie the steps to the sub headings below.

Setting up an analysis model to upload and move a file with an action

can all of the description just be combined in the solution section above and have this section jump straight into how to set it up?the following is required

1. an action configured to upload a file
2. an analysis model containing a file collector and a table
3. a task plan that runs the analysis model

This is a worked example to set up a model that collects an uploaded file, moves it, and all the upload subdirectories, to the required new directory using an archive location on a file collector, to tell the collector where to move the file once it has been processed.

When files are uploaded via an action, they are initially stored under the default upload directory:

 /opt/phixflow/data/phixflow/upload 

A subdirectory is created for each uploaded file, in the form:

/opt/phixflow/data/phixflow/upload/[tag]/in/[uploadDate]/[uploadID]/[filename]

where

• [tag] is the tag specified by the action or file collector,
• [uploadDate] is the date of upload represented in a numerical string,
• [uploadID] is a unique string used to identify each file, and
• [filename] is the name of the uploaded file.

When uploading files through the front end, we aim to move the files to a location under (either directly or via soft link) the below directory while preserving these subdirectories in order to uniquely reference each file.

/opt/phixflow/data/phixflow/datalink

1. Creating the action

to upload a file

In the File Upload section, tick File Upload and enter a Tag Expression (e.g. "contact"). The exact tag used does not matter but needs to be used later to reference the upload location. Ticking File Upload means that running the action will trigger a file upload prompt, allowing the user to select a file to upload.

2. Creating the Analysis Model

Create a new analysis model and create a 

Next create a 

On the new table, create 4 attributes with the following settings:

3. Creating the Task Plan

Create a new task plan and create an analysis task which runs the above table. On the created action, in the Run Task Plan section tick Run Selected Task Plan, and add the new task plan.

This means that after the action prompts the user to upload a file,

1. the table will be run,
2. which in turn runs the file collector

1. 1. the file collector

1. 1. finds the file in the upload location

1. 2. moves it to the new directory used to store the filesr
2. the

1. table

1. then

1. pulls through the file details

1. generating its new location in the attribute FileLocation. This attribute can then be used whenever the file needs to be referred to.

Referencing Images on the Server

Once the user has identified the correct directory to store the file, it can be referenced using a URL. This URL must be in the format:

url("[File Location]")

For example: url("https:datalink/MyProject/MyImage.png")

This URL is the value that needs to be stored and is referenced to display the image using CSS properties. Using the above example, the user stores the url of an image against each user in an attribute called 'ContactImage'. You can display this image on an area inside a card container (does it need to be in an area?)  using the following style settings:

• Name: background-image
• Expression: _form.ContactImage
• Name: background-repeat
• Expression: no-repeat
• Name: background-size
• Expression: choose size – could be 100%, 20px, auto (see Image Sizing)

Changing Images on the Server

To change the image displayed in PhixFlow, upload a replacement image with the same name. The new image overwrites the original image. The existing URL continues to work and displays the new image. If the image name changes on the server, you need to update all the URLs that point to it.Mention that

Using an actionflow

Sarah todo when file collector node is complete.

More Information