...
| Info |
|---|
About AgilePort
The administrative settings defined in the AgilePort tab only apply to MetaField client companies who also subscribe to AgilePort.
If your company does not subscribe to AgilePort, the tab will still be shown, but it will not function.
If your company does subscribe to AgilePort, a Publish feature will appear in the Delivery portion of the application. In order for the Publish feature to work successfully, the default location of your portal must be defined on the AgilePort™ tab. This URL will be provided at the time your subscription to AgilePort is configured. Simply copy and paste this URL into the Default Publishing Location field and select Save.
Settings
- The URL entered for the Default Publishing Location will serve as the default portal for all projects.
- If custom portals have been configured, additional publishing URLs will be provided. Add those publishing locations and the corresponding Project Code in the Custom Publishing Locations list.
Report Mappings
When AgilePort™ publishing functionality is used, published reports are automatically arranged in a series of folders, organized by project number. However, by default, all reports for each project are placed in the same project folder, regardless of what type of report is being published. The Report Mappings tab allows administrators to separate each different report type into its own folder within the project folder. Using the fields on the Report Mappings sub-tab, you can specify what the name of the folder should be for each type of report that can be created in MetaField™.
| Info |
|---|
This will only impact reports published to the default publishing location. Projects that have custom publishing locations configured will not be affected. |
AgilePort Plus
...
AgilePort administrators should refer to AgilePort Help for details on the configuration settings available in MetaField. |