Once the Project structure is complete, you must build the output so that it can be published on the network or sent by email. Building the output creates a view of the data at that point in time. The output is viewed using the Project Viewer, which most people will have access to.
Build the Project Output
Any previously-created output for this project in the same output folder will be deleted - a warning is displayed before this happens.
- From IFP Home select Projects / Dashboards > Project Manager.
- Select the required Project and double-click or select Properties to open the Project Editor.
- Click the Build button. The Project Build Options are displayed.
- We recommend that you use the default Single File output, as this is easier to manage / send by email.
- If required, the Project Output can be password protected - anybody viewing the output must enter the correct password.
- When you click Build, the Project contents are validated to check for any missing package files; these are highlighted in the editor. Any missing packages must be resolved before continuing. Refer to Common Issues Found when Building Project Output for more information.
- Once the Project contents validate OK, IFP runs each package or dashboard in turn, reporting success or failure to the output window.
- When complete, a message "Build Complete" is displayed in the output window. If you selected Open the Project when the build completes, the Project Output is opened in the Project Viewer.
- Notify other users that the Project Output has been created, passing them the network location (path). They can view the output in the IFP Project Viewer.
- You can also send the Project Output file (ProjectName.ifpp) by email. Note that users opening this will require database access permissions for all databases in the Project.
Projects are secured in the following ways:
The Project Output can be password protected - anybody viewing the output must enter the correct password.
Even without passwords, anyone viewing the Project Output must have access to all databases used in the Project. This means that even though you may find that the default Project Output folder contains information from many databases, you can only view the output that you have access to.
Similarly, anyone editing a Project must have access to the database(s) used in that Project.
A user has access to Database A and Database B. They would like to view Output from a Project that uses 5 packages from Database A, 7 packages from Database B and 1 package from Database C.
This user will not be able to view the Project Output as they do not have access to Database C.