What can we help you with?

Sorry, you do not have permission to carry out this action.
Avolve Software - Powered by Kayako Help Desk Software
What can we help you with?

knowledgebase : FAQs > Publishing

Avolve has investigated the .DWX file format and have found this format type to be produced exclusively by a 3rd party company called CADLock, Inc. (www.cadlock.com). To create a .DWX file, AutoCAD users are required to purchase CADLock’s CADVault Digital Rights Management (only available for the Microsoft Windows operating system) add-on to AutoCAD. The .DWX format that is created “…utilize a proprietary system of adding internal security capabilities…” to the file or group of files. This process is much like putting a password on a .PDF file. If the receiver of these .DWX files do not have a CADVault Runtime license, they are not allowed/unable to open the .DWX file. Because the .DWX is a proprietary file format and the CADVault Runtime application is required to open it, Avolve’s ProjectDox Electronic Plan Review system cannot support this .DWX file format. Avolve also reviewed this with our Brava viewing engine vendor, and they have no future plans to support the .DWX file format.

Description

Creating and Editing Stamps in ProjectDox Step by Step.

Description

ProjectDox generates and stores event information in many different log files as a method for being able to review the information and troubleshoot any issues that may arise.  

  Log File Location Description
1. Web server sites
  •  IIS logs windows/system32/logs
Used to gather error information 500, 404, 403
2. Process incoming email
  • Win2008 path: Program Files (x86)\Avolve\ProjectDox Process Incoming Service
  • win2003 path: Program Files\Avolve\ProjectDox Process Incoming Service
  • Debug.txt in the root of the install
Used for checking incoming email issues into the system. Not tied to teammail, topic and note or workflow emails that are sent.
3. SMTP logs
  • windows/system32/logs
Used for checking all email issues in and out of the system
4. ProjectDox Utility service
  • Win2008 path: Program Files (x86)\Avolve\ProjectDox Utility
  • win2003 path: Program Files\Avolve\ProjectDox Utility
  • Debug.txt in the root of the install
Used for ProjectDox clean up tasks, SSO, workflow sync, JP republish feature and global permissions sync
5. Job Processor
  • Logs to the netitsvc user profile under %user% Local Settings\Temp\IGC)
  •  Logging will need to be turned on from the JobProcessor config. In the root of the installation directory to view the log file. Log file is turned off to save on resources.
  • View the log file on the Job Processor via a browser by typing in http://localhost:7070/logs
Used for troubleshooting publishing issues
  HeartBeat File
  • Located in the UserFilesPublish directory within the destination folder for each published file. Displays detailed information on the processing of the file including error information
Used to troubleshoot Job Processor publishing issues
6. ProjectDox WCF service
  • Win2008 path: Program Files (x86)\Avolve\ProjectDox WCF Server
  • win2003 path: Program Files\Avolve\ProjectDox WCF Server
  • Debug.txt in the root of the install
Used to troubleshoot DB connection issues between web, WCF, and Database.
7. ProjectDox Creator service
  • Win2008 path: \Program Files (x86)\Avolve\ProjectDox Project Creator
  • win2003 path: \Program Files\Avolve\ProjectDox Project Creator
  • Debug.txt in the root of the install
Used to troubleshoot project creation from incoming integration
8. Data Base
  • Data base server event viewer, and MSSQL logs, ProjectDox DB table log reports
The ProjectDox log reports table holds all transactions completed in the system by ID
9. ProjectDox Workflow
  • Win2008 path: \Program Files x86)\Avolve\ProjectDox Workflow Server
  • win2003 path: \Program Files\Avolve\ProjectDox Workflow Server)Debug.txt in the root of the install
This is used to troubleshoot workflow issues and connectivity problems.
10. ProjectDox License Server
  • Windows Event Viewer, on by default via the Admin, Configuration, Log tab, with LogOutput set to 8
This is used to troubleshoot Viewer issues and will show any type of base licensing issues that are preventing viewing of the files in Brava
11. ProjectDox
  • Windows Event Viewer – ProjectDox Event Log
Base ProjectDox application error will display robust information
12. ProjectDox
  • Trace = True, turned on in ProjectDox\web.config file
While Trace will slow down the application, it is an excellent tool for tracking deeper issues such as configuration in the application
13. ProjectDox Viewer Server
  • Windows Event Viewer
Detailed Flash viewing errors
14. Lucene Search Engine
  • C:\Program Files (x86)\Avolve\ProjectDox WCF ServerLuceneUITest.exe
  • Debug.txt
  • SearchEngineLog.log
Search error will display to the screen running this test tool interactively
15. Reports
  • Error will display in the report UI
 

 

Resource

The table above has been attached for your download convenience. 

 

Revised 02-26-2015

Description

Job Processor logging may be turned on to diagnose any publishing problems that may be occurring with the Job Processor. Avolve may ask you to turn on logging for the Job Processor (temporarily) and to reproduce the problem.

It is advised to turn the logging off when the data has been collected (problem reproduced) as it can cause a minor decrease of performance with the Job Processor.

Solution

To enable logging you must go into the Job Processor directory, which is typically E:\Program Files (x86)\IGC\Brava!\Brava! Enterprise JobProcessor.
From within this directory, open the JobProcessor.config file in a text editor (Microsoft Word is not advised as it may add formatting to the text file that will cause issues with the Job Processor).

You will notice near the top of the file that by default:

     log=off

Please simply change "off" to "on," save the file, and then restart the JobProcessor Service. The "log.size=200" is the default maximum amount of jobs that will be reported in the file. Remember you need to restart the service again when you turn logging off (and save the file) after reproducing the problem.

Further down in the file you will notice this section:

     # Log file
     ProcessMonitorLogFile=%temp%\Informative Graphics Corp\IGCMonitorServiceLog.txt
     ProcessMonitorLogFileMaxSizeInMB=1

The ProcessMonitorLogFile= is the location of one of the log files.

**Please note that this is the location of the %temp% folder for the user that the JobProcessor is running as (should be an Administrator account). This means if you are remotely connected to the machine as a user that is not the JobProcessor service user then you will not see the logs in this location and instead need to navigate to the folder for the JobProcessor User.

Usually it is easiest to find this by going to C:\Users\[Job Processor USER]\AppData\Local\Temp\ and then performing a search for "IGCMonitorServiceLog.txt" without quotes. This is because there could be several folders under \Temp\ that the file could be located under.

Search for RIE_NIE under %appdata% for the Job Processor user's profile. Additional logs should be located inside that folder. Please send the IGCMonitorServiceLog.txt and any files in this RIE_NIE folder to Avolve.

The filesize of the log will not exceed 1MB by default unless you modify ProcessMonitorLogFileMaxSizeInMB= to a higher setting which is usually not necessary unless you change log.size= to more than 200 (jobs).

 

Revised 02-26-2015

Description

This will explain how to resolve the issue where the Job Processor service will not start, but other Brava services will.

This occurs with the following:

     Brava Type: Brava Enterprise .NET 7.1 and earlier

If all Brava services are able to start except the Brava Job Processor, this is usually related to the service account that is being used to logon the service, typically named NetItSvc. This means that the user that installed Brava Enterprise .NET is different from the user being used as the service account.

Solution

In order to resolve this, you will need to either change the service account to the user that installed Brava Job Processor or reinstall Brava Enterprise .NET Job Processor application as the user that will be running as the service account, in a typical installation, the NetItSvc account. 

The NetItSvc and the PD_USR accounts should be created on the machine as a Local Administrators prior to the installation of the Job Processor application.

 

Revised 02-26-2015

To be able to retrieve the Job Processor Log files, each Job Processor must first have logging enabled.  To enable JobProcessor logging, follow the directions listed in the KB below

 

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=62322277&objAction=ArticleView

 

To obtain the JobProcessor logs, search for RIE_NIE_logfile.xml under %appdata% for the JobProcessor user's profile. Additional logs should be located inside that folder. Please send the IGCMonitorServiceLog.txt (if the JobProcessor does not work at all) and any files in this folder. Typically, the folder that has the RIE_NIE_logfile.xml is:

 

 C:\Users\JOB_PROCESSOR_USER\AppData\Local\Informative Graphics Corp

 

The filesize of the log does not exceed 1MB by default unless you modify ProcessMonitorLogFileMaxSizeInMB= to a higher setting which is usually not necessary unless you change log.size= to more than 200 (jobs). You can safely set this up to 32MB.

HTML Publishing Facts

  1. We cannot implement on demand HTML publishing only, we must pre-publish. If there is a file on the system that has been deleted from the DLCache, we will publish on demand.
  2. When the client uploads or makes the request for an HTML file and the HTML is not published, the DLCache is populated with folders. This can be misleading because folders appear in the DLCache but they are not populated. These folders are the job that the job processor is grabbing in order to publish the HTML
  3. Once the job has been published, render-vector complete folder has the heartbeat.txt, as do other folders in the published set
  4. When you delete the DLCache, you must restart Apache and the Job Processor. Apache holds a record of the contents of the DLCache so it must be cleared.
  5. In order to test html publishing outside of the ProjectDox integration, use this URL http://HOSTNAME:PORT/BravaSDK/HTML/samples/themes/desktop-full-black.html (the SDK must be installed for this test)
  6. If you ever receive an error like unable to view files because its format is not licensed when testing the HTML viewer, it is because either port 8080 or 8443 is not open from the internet to the web server

 

TROUBLESHOOTING #1

  1. Allow the file to fail in Chrome
  2. View source and copy the config provider

 /configprovider.aspx?FileID=3417&UserID=4&ViewList=&igcmethod=GetConfig

    3. Control-n for a new web page then paste the above text into the Address

    4. Append the following to the copied source address using the URL for the client

https://<<URL>/projectdox/integration/bravaplugin/htmlclient

https://qatest1.avolvesoftware.com/projectdox/integration/bravaplugin/htmlclient/configprovider.aspx?FileID=3417&UserID=4&ViewList=&igcmethod=GetConfig

    5. Confirm the XML has not errors

TROUBLESHOOTING #2

  1. Allow the file to fail in Chrome
  2. Open the Developer Tools and bring the focus to the console using Ctrl + Shift + J

 

 

Contributed by: Lora Benedict

Contributed on: 2/19/2017

Problem:

 

After saving a PDF from Microsoft Internet Explorer that was opened from the PDF Converter Professional Web Viewer, the PDF file does not appear in the specified save location.

 

 

 

Cause:

 

This issue may occur if the "Enable Protected Mode" option is enabled within Microsoft Internet Explorer. With this Internet Explorer option enabled, all files saved from Internet Explorer are actually saved to a "Virtualized" folder instead of the specified folder. For example, if a PDF file is intended to be saved to the Windows Desktop, the PDF is actually saved to the following virtualized folder instead:

 

C:\Users\%username%\AppData\Local\Microsoft\Windows\Temporary Internet Files\Virtualized\C\Users\%username%\Desktop

 

 

Solution:

 

Please disable the "Enable Protected Mode" option within Microsoft Internet Explorer by following the steps below:

 

Open Microsoft Internet Explorer.

Go to the "Tools" menu.

Click "Internet Options".

Go to the "Security" tab.

Disable/uncheck the option to "Enable Protected Mode".

Click "Apply", then "OK".

Restart Microsoft Internet Explorer.

Now PDF documents that are saved from the PDF Web Viewer will be saved to the specified location.

REPUBLISHING FILES

In the event that files uploaded by a user do not successfully publish there are two methods available to republish the file in ProjectDox.  The ProjectDox Utility Service and the ProjectDox SystemConfig.aspx republish options are not related or dependent on each other. The systemconfig.aspx has no timeout, dead considerations, or max retry restrictions.

ProjectDox Utility Config File Values

<add key="SecondsBetweenInvoke" value="300"/> <!-- how many seconds between when web services/processing are invoked, recommended is 300 - 600 seconds (5 - 10 minutes) -->

               <add key="RepublishMaxRetryCount" value="2"/> <!-- Maximum # of times to attempt to republish a file. This service will try to republish the files every time the service executes based on the [SecondsBetweenInvoke] setting in this config file. If the file hasn't been attempted to be republished the first time before [SecondsBetweenInvoke] comes again then it won't immediately try to republish the file. Instead, it will wait until the file fails the second time and then republish again [RepublishMaxRetryCount] times. -->

               <add key="TicketConsideredDeadMinutes" value="240"/> <!-- Maximum # of minutes before a ticket is considered dead. This is required in the case where the Job Processor fails to notify ProjectDox of success/failure of the publishing (i.e. Job Processor critical error, network problems, ProjectDox down, etc) . The minute count is measured from when the ticket was originally submitted. For example, if you submit 10 files for publishing then the Job Processor server takes those 10 tickets into memory to publish the files. If the Job Processor server dies while processing the 10 tickets without being able to ping ProjectDox on the file publish status then after [TicketConsideredDeadMinutes] minutes it will resubmit those tickets for publishing. -->

CONCLUSION

  • The JPQueueTicket database record is always created when a file is uploaded with the JPSuccess column as 0 until the Success Notification is received which changes the value to 1.

  • Files that are stuck in “Processing” are in the JPQueueTicket table and will continue to show JPSuccess column as 0. After 240 minutes the file will timeout. The next time the Utility runs, there will be an attempt to publish. It will continue the attempts per the RepublishMaxRetryCount value in the Utility.

  • Once the PublishAttemptCount column equals the RepublishMaxRetryCount, no other action will be taken.

  • If the file completes with an error, it no longer shows “Publishing” in the user interface, then the error is written to the PublishResult column of the JPQueueTicket table.

    • Example: Primary error: publish_error, Error # 0: Unrecognized output format: .dwf, Error # 1: DWF output format is no longer supported.

  • Failures to publish will have a single file, a Heartbeat.txt file, in UserFilesPublish folder with details of the failure.

  • In some instances, in the case of a bad license, the SecondsBetweenInvoke at 300 seconds, (5 minutes) for 2 RepublishMaxRetryCount may not be enough time to resolve the problem and the attempts will hit the max.

    • You can take advantage of the systemconfig page in this scenario.

    • Or, you can increase the RepublishMaxRetryCount by 1 and restart the Utility.

  • When a file is republished via the Utility or the systemconfig page, the process updates the existing JPQueueTicket, it does not create another JPQueueTicket or record in the shared queue folder.

  • If you select 1 file to republish from the systemconfig page, the code retrieves up to 500 files that are ready for publishing and sends them all to the Job Processor, it is generic method that is called.

  • HTML publishing failure, it is not part of the republishing tool or the ProjectDox Utility.

    • ActiveX must successfully publish first in order to publish the HTML

    • The HTML rendition will republish only when the HTML file is clicked on

Test Case

  1. Stop the ProjectDox Utility Service

  2. Stop the Job Processor service

  3. Stop the Brava License server service

  4. Stop the Apache service

  5. Replace license files on both servers with an expired IGCKey.lic

  6. Restart the Brava License server service

  7. Restart Job Processor service, then the Apache

  8. Upload 3 files

  9. Review the Heartbeat file in UserFilesPublish

  10. Review the JPQueueTickets table for the failures

  11. Stop the Job Processor, Brava License, and Apache services

  12. Replace license files in the JP and Brava License folders with a valid one

  13. Restart the 3 services

  14. Do not start the ProjectDox Utility Service

  15. Login to the systemconfig.aspx page

  16. Select 1 file of the 3

  17. All 3 will publish

If you encounter the error "There was a failure downloading the Integration Dll! Please check the IntegrationUrl BravaXParam," there may be an issue with the User Account Access. For troubleshooting steps, see attached document.  

The following characters are invalid as file or folder names on Windows using NTFS:
/  ' ? < > \ : * | ” and any character you can type with the Ctrl key

In addition to the above illegal characters the caret ^ is also not permitted under Windows Operating Systems using the FAT file system.

Under Windows using the FAT file system file and folder names may be up to 255 characters long.

Under Windows using the NTFS file system file and folder names may be up to 256 characters long.

Under Window the length of a full path under both systems is 260 characters.

 

Revised 02-18-2015

Description

Customers with anti-virus installed on the ProjectDox Servers must enable the following exclusion rules in any scanning utilities installed to prevent issues with the function of the software.  Avolve recommends that only the PdoxTemp folder be scanned in real-time.  All other ProjectDox application folders and supporting folders, including all sub-folders, should be excluded from anti-virus applications real-time scanning.  A nightly scan of the directories is acceptable.  It is not recommended to have anti-virus installed on the Job Processors.  Avolve cannot guarantee the operation of the Job Processors with anti-virus installed on the servers and, in the event issues occur with publishing, the first recommendation will be to remove the anti-virus application from the Job Processors and perform a full reboot.  Perform testing after the Job Processor has been rebooted to see if the issue is resolved.  

Solution

Avolve recommends setting up exclusion rules for the folders specified below on the ProjectDox servers indicated.  Assuming the Operating System is installed on the C:\ drive and the ProjectDox, related services and Brava applications are installed on the E:\ drive, you would want to exclude the following folders, including any sub-folders, on the ProjectDox servers.  A list of common Share Folder Names used by ProjectDox is provided below.

  • UserFilesSource or UFS - Stores original files uploaded by users
  • UserFilesPublish or UFP - Stores published ActiveX version of files uploaded by users
  • DLCache - Stores published HTML version of files uploaded by users
  • Queue - Stores Job Tickets created for publishing requests for the Job Processors
  • PdoxLogs or Logs - Stores Archive PDFs if using ProjectDox Archive Feature
  • PdoxExport or Export - Stores Exported Projects until retrieved by EDMS solution
  • WFlowDLLCache - Stores ProjectFlow workflow instance DLLs for active workflows
  • PdoxTemp - All uploaded files are stored in this folder first before being moved to the UserFilesSource folder.  This folder should not be excluded as it is the single point of entry for any new files uploaded to ProjectDox and should be scanned in real-time.

NOTE:  Some anti-virus applications may need an additional exclusion rule enabled for .rtf file types.  If you experience trouble with missing Markups or Changemarks within the workflow, then please try adding the exclusion rule for file types of .rtf and see if that resolves your issue.  Markups and Changemarks are saved to the PdoxTemp folder temporarily and some anti-virus applications will false alert and remove the .rtf file causing saved Markups and Changemarks to not show up in the workflow.

Job Processors

     C:\Windows\system32\spool\PRINTERS\  

     C:\Windows\Temp\  **  (see additional info below)

     C:\Users\NetItSvc\AppData\Local\Informative Graphics Corp\

     C:\Users\NetItSvc\AppData\Local\Temp\

     C:\Users\NetItSvc\AppData\Roaming\Informative Graphics Corp\

     C:\ProgramData\IGC\  (Brava 16.2 and 16.4)

     C:\ProgramData\OpenText\  (Brava 16.6 and up)

     E:\Program Files (x86)\IGC\   

     E:\Program Files (x86)\Avolve\    

     E:\Program Files\IGC\   

     E:\JPTemp\  **  (see additional info below)

     E:\ProjectDoxSupportFiles\  or  E:\PDSF  (see note below)


Web Server

     w3wp.exe Process

     E:\ProjectDox\     (Superion customers may see E:\EPR instead of E:\ProjectDox)

     E:\ProjectDox.Web.API

     E:\ProjectDox.Web.UI

     
E:\Program Files (x86)\Avolve\   

     
E:\ProjectDoxSupportFiles\  or  E:\PDSF  * (see note below)


Application Server

     
E:\Program Files (x86)\Avolve\

     E:\ProjectDoxSupportFiles\  or  E:\PDSF  * (see note below)



NOTE *

ProjectDox file share folders may exist on any ProjectDox server, Network Storage Device or stand-alone File Server. 
The PdoxTemp folder is the single entry point of new files to the server and therefore it is recommended to scan this folder only in real-time.  A nightly scan can be performed of the folders if desired.
Exclude all share folders with the exception of PdoxTemp from real-time scanning. 



ADDITIONAL INFO **

     If you are unable to exclude C:\Windows\Temp on the Job Processors, you can update the system output path of the IGC Writer Print driver and use a different directory for example E:\JPTemp.


To do this:

  1. Create a folder on the E:\ drive named JPTemp
  2. Grant Full Control under the Security Options for the folder, to the PD_USR and NetISvc accounts
  3. In the Control Panel Printers and Faxes panel, right-click on the CSF Writer printer and select Properties
  4. Select the Advanced tab
  5. Click the Printing Defaults... button
  6. Select the Filename Generation tab
  7. Change the Output Directory path to the following:  E:\JPTemp
  8. Click OK to save your settings.

Then add an exclusion rule for the E:\JPTemp folder on the Job Processors in place of the C:\Windows\Temp folder



SQL Server

Antivirus exclusion on SQL files:

When you configure antivirus software settings, make sure that you exclude the following files or directories on SQL Server machine from virus scanning. Doing this improves the performance of the files and helps make sure that the files are not locked when the SQL Server service must use them. However, if these files become infected, your antivirus software cannot detect the infection. 

  • SQL Server data files (.mdf, .ndf, .ldf files)
  • SQL Server backup files (.bak, .trn files)
  • Full-Text catalog files
  • Trace files (.trc files )
  • SQL audit files for SQL Server 2008 or later versions (.sqlaudit files)
  • SQL query files (.sql files)
  • The directory that holds Analysis Services data
  • The directory that holds Analysis Services temporary files that are used during Analysis Services processing
  • Analysis Services backup files
  • The directory that holds Analysis Services log files
  • Directories for any Analysis Services 2005 and later-version partitions that are not stored in the default data directory
  • Filestream data files (SQL 2008 and later versions)
  • Remote Blob Storage files (SQL 2008 and later versions)
  • The directory that holds Reporting Services temporary files and Logs (RSTempFiles and LogFiles)

Processes to exclude from virus scanning

SQL Server 2016

  • %ProgramFiles%\Microsoft SQL Server\MSSQL13.<Instance Name>\MSSQL\Binn\SQLServr.exe
  • %ProgramFiles%\Microsoft SQL Server\MSRS13.<Instance Name>\Reporting Services\ReportServer\Bin\ReportingServicesService.exe
  • %ProgramFiles%\Microsoft SQL Server\MSAS13.<Instance Name>\OLAP\Bin\MSMDSrv.exe

SQL Server 2014

  • %ProgramFiles%\Microsoft SQL Server\MSSQL12.<Instance Name>\MSSQL\Binn\SQLServr.exe
  • %ProgramFiles%\Microsoft SQL Server\MSRS12.<Instance Name>\Reporting Services\ReportServer\Bin\ReportingServicesService.exe
  • %ProgramFiles%\Microsoft SQL Server\MSAS12.<Instance Name>\OLAP\Bin\MSMDSrv.exe

SQL Server 2012

  • %ProgramFiles%\Microsoft SQL Server\MSSQL11.<Instance Name>\MSSQL\Binn\SQLServr.exe
  • %ProgramFiles%\Microsoft SQL Server\MSRS11.<Instance Name>\Reporting Services\ReportServer\Bin\ReportingServicesService.exe
  • %ProgramFiles%\Microsoft SQL Server\MSAS11.<Instance Name>\OLAP\Bin\MSMDSrv.exe

SQL Server 2008 R2

  • %ProgramFiles%\Microsoft SQL Server\MSSQL10_50.<Instance Name>\MSSQL\Binn\SQLServr.exe
  • %ProgramFiles%\Microsoft SQL Server\MSSQL10_50.<Instance Name>\Reporting Services\ReportServer\Bin\ReportingServicesService.exe
  • %ProgramFiles%\Microsoft SQL Server\MSSQL10_50.<Instance Name>\OLAP\Bin\MSMDSrv.exe

SQL Server 2008

  • %ProgramFiles%\Microsoft SQL Server\MSSQL10.<Instance Name>\MSSQL\Binn\SQLServr.exe
  • %ProgramFiles%\Microsoft SQL Server\MSSQL10.<Instance Name>\Reporting Services\ReportServer\Bin\ReportingServicesService.exe
  • %ProgramFiles%\Microsoft SQL Server\MSSQL10.<Instance Name>\OLAP\Bin\MSMDSrv.exe
If you back up the database to a disk or if you back up the transaction log to a disk, you can exclude the backup files from the virus scanning.

You can run antivirus software on a SQL Server cluster. However, you must make sure that the antivirus software is a cluster-aware version. If you are running antivirus software on a cluster, make sure that you also exclude these locations from virus scanning:

  • Q:\ (Quorum drive)
  • C:\Windows\Cluster

Please refer the article for more information: https://support.microsoft.com/en-us/help/309422/how-to-choose-antivirus-software-to-run-on-computers-that-are-running



Description

Neutral Formats Extension
Portable Document Format PDF
Content Sealed Format CSF
Tagged Image Format TIFF/TIF

CAD Formats Extension
000 HPGL Plot File 000
906/907 Plot File 906/907
AutoCAD Drawing (2D) (through version 2014) DWG
AutoCAD DXF (through version 2014) DXF
AutoCAD Web Format (through version 2014) DWF
CADKEY PRT
Computer Graphics Metafile CGM
GTX Group III, IV G3, G4, CG4
GTX Runlength RNL
HP CAD ME10 (through version 13) CMI, MI
HPGL Plot File PLT
IGES (2D) (version 5.2) IGS, IGES
Inventor (2D) (versions 5.3 - 2013) ** IDW
MicroStation Drawing (through version 8.11, including XM, V8i) DGN
MicroStation Group IV CIT
MicroStation Runlength RLE
MYRIAD 3D View Sets MVS
OrCad (version 10) DSN
Solid Edge Drawings (2D) (versions 8 - ST5) DFT
SolidWorks Drawings (2D) (versions 97 - 2011) SLDDRW

Imaging Formats (additional formats available*) Extension
CALS (Group IV) CAL, CG4, GP4, MIL
EDCARS EDC
Encapsulated Postscript PS/EPS
GIF GIF
ISO 8613/CALS ISO, CAL
JPEG Compressed Image JPG, JPEG, JP2
Portable Network Graphic PNG
Tagged Image File TIF, TIFF
Windows Bitmap BMP

Additional Document and Image Formats* Extension
Corel Draw CDR
Corel Presentations SHW
DataBase Formats DBF
DocuWorks XDW
FAX CITT Group 3 Fax FAX
Hangul Word Processor HWP
Hyper Text Markup Language HTML, HTM
Microsoft Email MSG
Microsoft Excel XLS, XLSX, XLSM, XLSB, XLTX, XLTM
Microsoft PowerPoint PPS, PPT, PPTX, PPTM, PPSX, PPSM, POTX, POTM
Microsoft Visio VSD, VST, VDX, VSX, VTX
Microsoft Word DOC, DOCX, DOCM, DOTX, DOTM
Microsoft Works WDB, WPS, DOCX, XLSX
PageMaker P65
QuattroPro WB1, WB2, WQ1
Rich Text Format RTF
Samna Word SAM
Windows Write WRI
WordPerfect WP5, WP6, WPD, WPF
WordStar WS

Video Formats***
Brava supports any video format supported by the Adobe Flash Player.

  • Sorenson Spark
  • On2 VP6
  • H.264 (MPEG-4 Part 10) with the following subsets¹:
    • ISO/IEC 14496-3 (Audio AAC): AAC Main; AAC LC; SBR
    • ISO/IEC 14496-10 (Video AVC): Base (BP); Main (MP); High (HiP); All levels are supported
    • ISO/IEC 14496-12 (Container): 1 Audio Track, 1 Video Track
    • 3GPP TS 25.245 (Timed Text Format): Full Support

¹Flash Player plays files containing H.264 and AAC that are derived from the standard MPEG-4 container format such as F4V, MP4, M4A, MOV, MP4V, 3GP, and 3G2.

 If you are using versioning in ProjectDox, we recommend that the maximum file length be 25 characters or less.

If you are not using versioning, we would recommend 70 characters.

We have successfully uploaded and tested over 100 characters; however, sometimes there is an issue with the length of the folder structure because Microsoft has a 246 character limit.

Here is an example of a file called 12345.pdf as it versions 3 times:

 

e:\ProjectDoxSupportFiles\UserFilesPublish\12345.pdf\12345.pdf =57Characters

e:\ProjectDoxSupportFiles\UserFilesPublish\12345.pdf\12345-v2.pdf\12345.pdf =70 Characters

e:\ProjectDoxSupportFiles\UserFilesPublish\12345.pdf\12345-v2.pdf\12345-v3.pdf\12345/pdf =82 Characters

 

Dynamic Stamp Tokens

 PROJECT TOKENS

FILE OWNER TOKENS

USER TOKENS

%ProjectName

%ProjectID

%ProjectDescription

%ProjectStatus

%ProjectLocation

%ProjectContact

%ProjectEmail

%ProjectCellPhone

%ProjectPager

%ProjectSourcePath

%ProjectPublishPath

%ProjectURL

%ProjectCreateDate

%ProjectEndDate

%Date

%Time

%OwnerUserID

%OwnerUserName

%OwnerCompany

%OwnerTitle

%OwnerAddress1

%OwnerAddress2

%OwnerCity

%OwnerState

%OwnerCountry

%OwnerZipCode

%OwnerWorkPhone

%OwnerCellPhone

%OwnerPager

%OwnerFax

%OwnerEmail

%OwnerLastLogin

%OwnerSignupDate

%OwnerUserLanguage

%UserID

%UserName

%Company

%Title

%Address1

%Address2

%City

%State

%Country

%ZipCode

%WorkPhone

%CellPhone

%Pager

%Fax", RequestingUser.Fax);

%Email

%LastLogin

%SignupDate

%UserLanguage

FILE TOKENS

FILE METADATA

USER METADATA

%FileID

%FileAuthorID

%FileName

%FileSize

%FileSourcePath

%FilePublishPath

%FilePublishURL

%FileUploadDate

%FileVersion

%FileSheetSize

%FileSquareFeet

%FileFriendlyPath

%FileErrorCode

%FileErrorMessage FOLDER TOKENS

 

%FolderID

%FolderParentID

%FolderName

%FolderSourcePath

%FolderPublishPath

%FolderCreateDate

 

 

%FileMetadata1

%FileMetadata2

%FileMetadata3

%FileMetadata4

%FileMetadata5

%FileMetadata6

%FileMetadata7

%FileMetadata8

%FileMetadata9

%FileMetadata10

%FileMetadata11

%FileMetadata12

%FileMetadata13

%FileMetadata14

%FileMetadata15

%FileMetadata16

%FileMetadata17

%FileMetadata18

%FileMetadata19

%FileMetadata20

%FileMetadata21

%FileMetadata22

%FileMetadata23

%FileMetadata24

%FileMetadata25

 

%UserMetadata1

%UserMetadata2

%UserMetadata3

%UserMetadata4

%UserMetadata5

%UserMetadata6

%UserMetadata7

%UserMetadata8

%UserMetadata9

%UserMetadata10

%UserMetadata11

%UserMetadata12

%UserMetadata13

%UserMetadata14

%UserMetadata15

%UserMetadata16

%UserMetadata17

%UserMetadata18

%UserMetadata19

%UserMetadata20

%UserMetadata21

%UserMetadata22

%UserMetadata23

%UserMetadata24

%UserMetadata25

 

 

Brava Stamp Tokens

 

%Date Inserts the date the print was spooled. If the tags are viewed on screen, the time at which the screen was last refreshed displays.

% SysDatePlusDays(x) Inserts a date the specified number of days past the system date. Replace "x" with the desired number of days. Negative numbers of days may be entered. Be sure to close the parenthesis when you add the number of days.

%Time Inserts the time the print was spooled based on a 12 hour clock (AM/PM). If the tags are viewed on screen, the date on which the screen was last refreshed displays.

% MilTime Inserts the time the print was spooled based on a 24 hour clock.

%Title Inserts the name of the document.

%Page Inserts the page number.

% TotalPages Inserts the total number of pages.

%batespgno(x) Bates Number - This tag is used to indicate the starting page number and the number of digits to use. For example, %batespgno(0002) would place 0002 on the first page, 0003 on the next page, etc.

%Login (or %User) - Specifies the user name of the person who issued the print.

%Hostname - Specifies the hostname of the machine that issued the print.

%IPAddress - Specifies the IP Address of the machine that issued the print.

%% - Inserts a single % character.

© - Inserts the copyright symbol.

® - Inserts the registered trademark symbol.

 

%prompt("Label_String") Used in a token expression when creating a stamp template. When set, a prompt dialog displays to the end-user prompting them to manually edit a markup stamp's text string during review process. When this token is used, the prompt dialog displays when a user initially inserts the markup stamp and at any time the stamp is double clicked. The dialog contains a text entry field value which can be updated at any time before the markup is finalized through publishing. Unlike %DBUpdateString, the %prompt tokens will NOT be sent to the integration database for resolution and may not be customized for integrations.

Note that a ":" character will be automatically added to the end of LABEL_STRING in %prompt(LABEL_STRING) when displaying the caption to the user. For example, %prompt(Enter amount) means that the user will see a prompt box with the caption "Enter amount:" and a text entry field to type in the requested information.

%DBString(x) This tag is used to resolve custom tags for products that integrate with Brava!. Replace "x" with any printable character except a right parenthesis, ")". See notes below.

%DBUpdateString(field label) Used when creating Stamp Templates to resolve custom integration values during the review process. This tag inserts a corresponding field label value (Priority, Status, etc.) from the integration's database tables when a user either inserts a markup stamp, or double clicks on a markup stamp containing a %DBUpdateString token in the markup text string. The method for resolving these tokens is determined by the integration's needs, and can include using a dialog or a non-interactive method. If %DBUpdateStrings are not resolved, they are given a default answer which is displayed with the resulting markup stamp.

 

 

Notes:

  • Tag values are case insensitive. Also, all the tags except %% and %SysDatePlusDays(x) must be followed by a non-alphanumeric character (such as a space, a %, a comma, a slash) otherwise, they are interpreted as text strings.

  • A Bates Number is considered to be both the prefix and the page number WITH leading zeros. To create a Bates ID, you can add text preceding the tag. For example, Smith vs. Jones%batespgno(00001) would result in Smith vs. Jones000001 being printed on the first page, Smith vs. Jones000002 printed on the second page, etc.

  • Using the %DBString(x) macro allows you to incorporate database attributes into your ISO Banner and watermarks. For example, the following show the resulting printed string of various typed input:

 

Input: This document was created on %DBString(r_creation_date) by %DBString(owner_name).

Output: This document was created on 11/15/2011 by John Johnson.

 

Input: Document "%DBString(object_name)” was modified by %DBString(r_modifier) on %DBString(r_modify_date).

Output: Document "neo.doc” was modified by Pat McDonald on 1/12/2012.

 

Input: Reviewed and Approved, Version %DBString(r_version_label)

Output: Reviewed and Approved, Version 1.6