the TXT API should be able to be set so that it will always generate the .ok and .err files in the TXTAPI folder(s). This is critical for medical practices where multiple offices are sharing a single server and need to use the fr= command to control which line the fax is sent out over. Unfortunately, in using that, the generation of the .ok and .err files is turned off. These files are essential for interfacing with Allscripts Pro EHR.1 vote
There is a need for re-prioritizing outbound faxes. There are many occasions where an important fax gets submitted and there's a large outbound queue. Admins should be able to re-prioritize (and specify lines to use) so that the fax gets out at the next available instance.1 vote
For some customers it is absolutely important to have the ability to deposit their company letterhead as an image file for all outgoing fax messages!
All predefined reports at their ERP systems are configured to be printed out either on a pre-printed company paper or as a fax optionally. For this reason the reports do not have their own company letterhead on it.
Unfortunately our customers are not willing to customize all their reports because of the missing option at the fax software ;-)
Markus Schultz1 vote
We need to be able to email-to-fax "read-only" recommended documents from an EMR system to GFI FaxMaker via the Email2Fax Gateway. These are system generated MS Word documents.
More information on read-only recommended:
Attached example document showing the prompt for "read only" recommended.1 vote
I would like to see the possibility to being able as the title says, to embed an attached file in a cover page. Because this is not possible, images embedded in e-mail signatures (from users that are sending the faxes) are not converted on the cover page, but on a new page.
Images that are embedded in the e-mail signatures of users, are always send as an attachment with the e-mail, therefore not shown on the cover page.1 vote
GFI Application changes 0 to + while sending SMS to mobile nos.
Routing ID: [ ref:_00D80ZQDU._500C0ko61d:ref ]1 vote
In version 2015, there are several options missing that were available in prior versions. We need details on whether or not these are still relevant and how to handle if customers ask about them.
- Allow non-AD users to send faxes
- Only allow users in the Licensed users list to send faxes
- Do not cache users on startup
- Disable batch processing. (recommended if not using modems)0 votes
Why is there no QOS for fax senders? I have 3000 faxes log jammed and 1 users sends a fax, get to the back of the line! The 3000 faxes are a company announcement and now the user has to wait until the 3000 faxes are done before it goes out. That'll be next week Tuesday :p.
HELP! What kind of a product has no QOS? Get some!
P.S. 'Campaign"? What is that? Just noticed that was 'PRODUCT" who is developing this site?0 votes
I suggest you add the ability to "synchronize" FAXmaker configuration among NLB nodes of a highly available fax solution, as this can be implemented according to KBID002892.
This will very much improve the management and resiliancy of such solution, especially when the number of nodes is greater than 2.
Alternatively, a centralized management console, as separate module, could be used to add this extra functionality, along with the ability to install it only when needed.0 votes
In a DID/DTMF routing scenario we need to be able to autoprint the fax reports on specific printers. It would be best if one could define the printer on a per user basis.0 votes
- Don't see your idea?