Welcome to our Knowledge Base
Enter your search terms below.
Release Notes steadyPRINT 7.6
steadyPRINT Additions, Modifications and Bug Fixes in version 7.6
Additions
| Additions | Description |
| Configuration of private print templates | The user is now able to create templates for VPD printers on his/her own via the Agent. This enables the user to create templates with his/her desired printer settings without having to contact the administrator every time. |
| Driver support for private print templates | A driver enhancement has been made so that the private print templates can even be used during printing. |
| Workflow as direct printing (vDirect) | So far it has only been possible to select and carry out a workflow via the vPrinter. A workflow can now be made available to the user as a separate printer. This allows a direct execution of a workflow out of the print dialog of an application. |
| Adjustment status window | The final status window after running a workflow, which informs about the results of the respective actions, has been revised. Now it only appears in case of an error and can be completely disabled via the Agent profiles. |
| Print job view | Saving documents | The print job view now offers the possibility to save documents that have already been printed again as PDF, DOCX and XPS files. |
| Dashboard | Loading the status information from database | The dashboard of version 7.5 queries all status information “live” from the respective printer. In large environments, this may lead to a waiting time until all information on the respective printer appear in the dashboard. The stored information from the database might now be displayed via a switch. |
| Tags for different levels and views | The Center now enables the display of tags on folder, print server and printer levels. This way administrators can assign tags on folder and print server level which are also copied to the underlying objects. |
| Tag search (# search) in Center, Agent and vPrinter | The new tag search allows the search for tags created in the applications steadyPRINT Center, Agent and vPrinter. Printers can thus be filtered and searched for according to their functions. |
| Restricted visibility of print server and folders on the basis of AD objects | In version 7.5 the restricted visibility was introduced on printer level which is now also available on print server and folder level. It allows an inheritance of the defined visibilities to underlying objects. |
| Current default printer of user in session view | Occasionally, the administrator has the problem that he/she doesn’t know exactly which default printer is currently set for the user. The printer specified by the administrator might have been modified by users. Depending on the application, this will then lead to a support case. The session view now supports the administrator in displaying the current default printer of the user in the respective session. |
Modifications
| Modifications | Description |
| Revision of template, feature and finishing management | The management of templates, features and finishing options for VPD printing has been completely revised. It simplifies the administration and offers a better overview. |
| vName with selection dialog for several assignments | It is possible to define several assignments to a vName printer. If the user starts a printing process to this printer, a dialog is displayed due to the assignment not clearly specified which offers a selection of all available printers. This dialog has been revised so that the user gets the look&feel of the vPrinter printer. |
| Adjustment of the template selection | The display and selection of the template in the vPrinter has been simplified and designed more intuitively. |
| Accelerated setting of security settings for VPD printers | During the creation of a VPD printer, security settings for the printer are being set. They include e.g. which user has access to the printer and whether it is visible in a terminal server session. The latter is important for each user to see only those printers in his/her session that have actually been assigned.
The necessary implementation has been revised resulting in a considerable performance gain. |
| Merge of printer settings (VPD to manufacturer) | Merging VPD and manufactuer’s settings (PrintTicket) for a print job has again been improved. |
| Revision of the display of network printers in the integrated Agent | In the integrated Agent it has so far not been possible to differentiate network printers from local printers. The display has now been improved so that a direct differentiation is allowed. |
| Accelerated view of assignments | The assignment views in the Center have been revised making a considerable performance improvement noticeable especially in large environments. |
Bug Fixes
| Bug Fixes | Description |
| No display of Workflow assignments in Agent | The Agent partly did not show any workflow assignments.
This problem has been fixed. |
| Change of icon via the design profile not possible | The icon for the Agent could not be adjusted via the design profiles.
This problem has been fixed. |
| When opening the Agent, user gets wrong license errors | After opening the Agent, license errors are erroneously displayed.
This problem has been fixed. |
| Tile for “Add printer” cannot be disabled via Agent profile | If all possible assignment types are disabled for being added, the tile for adding printers is still not disabled but displayed furthermore. The window for adding printers opens and only here the button for connecting a printer remains disabled.
This problem has been fixed. |
| After adding a printer a license error is displayed | Error description (user view): I wanted to add a printer for which I stored a new CAL via the Center. Then I opened the Adding window for printers in the Agent and added the desired printer. Subsequently it was properly connected, but an error message was displayed saying that I didn’t have a valid license. Only after closing the Agent and opening it again, the error was no longer there.
This problem has been fixed. |
| Opening the view “Adding printers” takes a long time | If you have more than 100 custom icons for individualizing the print server and folder symbols in the tree views, it takes several minutes to open the window for adding a printer from the Agent.
This problem has been fixed. |
| Center needs a lot of memory by loading computer information | The Center uses a high amount of memory by loading the computer information.
This problem has been fixed. |
| The same backup server for different master servers covers several licenses | If the same backup server is added to several master servers, it will cover several licenses.
This problem has been fixed. |
| Printer management does not allow multiple deletion | Error description: The printer management allows deleting drivers, ports and printers. They can, however, only be deleted separately. This is really unfortunate for clearing work which may take a rather long time with an individual selection.
This problem has been fixed. |
| The window for “Importing print servers” displays “empty” printers | The window for importing printers might display “empty” printers (lines without content). In this case the printers were read out by the fallback via the registry. This happens if the GetPrinter method based on Win32-API does not send back the requested printers within 3 seconds. After a timeout the fallback routine mentioned above reads out the registry in order to successfully display the printers. So far a validation has been missing checking the printer information for completeness.
This problem has been fixed. |
| License display shows wrong number of used licenses | If the number of installed CALs should not correspond with the number of CALs available in the license, the license view will not be properly displayed.
This problem has been fixed. |
| Reporting URL for errors outdated | The stored URL for reporting errors from the Center is no longer current. It has been updated. |
| Report shows wrong data | The reports “printed page per month” and “license overview” might result in display problems. There are e.g. monitoring data until October 2018. However, it occurs that data until November 2019 are displayed in the report.
This problem has been fixed. |
ID: 22180 | Zur deutschen Version
