webCOMAND 2.41 Released

2.41 adds web interface improvements and new functionality for COMAND Script developers.


COMAND Solutions today released webCOMAND 2.41. New COMAND Script functionality has been added to enable developers to produce custom publication errors, improve publish efficiency, debug content dependencies and access environment variables.

  • New #ERROR COMAND Script statement can be used to produce a custom publication error and prevent file publication.
  • The #SQL COMAND Script statement has been enhanced.  Developers can "SELECT" predefined fields in their query to provide webCOMAND with additional meta information that improves dependency change detection.
  • Environment variables are now available to dynamic COMAND Scripts through the Perl $ENV hash, from within #PERL blocks.
  • Detailed information about content dependencies is now available from standard Publish Reports.  Hover the mouse over the new information icon displayed next to each published file for the reason for publication.  Click the information icon for a comprehensive list of all publication dependencies.

The web interface has also been enhanced to more gracefully handle requests to a busy webCOMAND server.  If the server is too busy to handle a request quickly, a friendly message is displayed and the request is automatically retried until it can be serviced.  If files were uploaded in the original request, they are preserved and do not need to be re-uploaded.


A number of bugs were also fixed:

  • The override button is displayed properly for administrators who attempt to open content locked by another user (bug introduced in version 2.40).
  • Number of destinations displayed to the right of a publication in the folder tree could be incorrect for users with certain access restrictions.
  • Import/Export Procedures produce an SQL error in certain circumstances when exporting from a Content Type.
  • Publication Procedure dependency checks could produce incorrect URLs, which are cached for re-use during publication.
  • Publication Procedure Filenames preceeded by a slash (/) produced a double slash in URLs in Publish Reports and #LINK results.