Monthly Release Notes - May 2017

Jump to:

Automate


Automate Schedule

Version: 4.1
  • Job purging: A new ‘Days to Keep’ option was added to the job purging settings. When automatic purging of job and job suite history is enabled, you can set the number of days to keep the history before it’s purged. You can set this globally under the System Settings (under Job Defaults), or for an individual job or job suite (under Job History Purge).
  • Oracle Concurrent Request print options: Print options were added to the Oracle Concurrent Request command builder. You can choose the printer that the output should be sent to, the number of copies to be printed, the print style used for the output (this depends on your system and printer setup), and the print language.
  • SQL Server integration: The integration with Microsoft SQL Server has been enhanced as follows:
    • When using the SQL Server Job command builder in Automate Schedule, you can specify a specific SQL Server (from a cluster) that you want the command to run on.
    • Automate Schedule can be configured so that its agents and jobs work in a SQL Server cluster failover environment.
  • Automate system types: The system types that are available when you’re creating an Automate system definition have been updated. Besides Automate 10 and Automate BPA Server, you can now select Automate 11 or Automate Enterprise Server.
  • Universal Connector 1.1 enhancements: The Universal Connector now supports the following the following Amazon web services: Amazon EC2, Amazon EC2 Container Service (ECS), AWS Lambda, and AWS S3.
  • The installer was enhanced so that when updating from Skybot Scheduler to Automate Schedule, on a system where Skybot was not installed into the default directory, the original install path is retained in the update.
  • Support for additional SFTP ciphers was added to prevent a file transfer failure with the following error: “Could not login into SFTP server, cause:Algorithm negotiation fail.”

Back to Top

 

Document Management (RJS)


Webdocs Windows

Version: 1.9.1
  • Fixed an issue with the REST API where it would fail to remove checkout status after a checkin
  • Fixed an issue with the REST API where retrieving the checkout status failed
  • Fixed an issue with the search index failing to process
  • Added a compatibility setting for LDAP authentication against Novell’s eDirectory server
  • Improved performance and SQL memory usage when utilizing the search functions
  • Browser cookies for user UI preferences are now always set to HTTPS-only when running under HTTPS

Back to Top

 

GoAnywhere


Version 5.5.2
  • Enhanced the Audit Log event ID generation to only allocate an event ID when needed. This removes the overhead of ID allocation for events that are skipped by using the Log Exemptions.
  • Enhanced the Execute Native Command task to allow specifying the Executable Directory.
  • Added validation to the Agent Names to ensure only characters supported by most operating systems are allowed.
  • Added Agent support to conditions and actions for Triggers.
  • Added the Agent Service to the Service Status, Active Session - Details, and Active Sessions - Summary Dashboard gadgets.
  • Added compression and message batching to various Agent notifications to help prevent rejections that could occur when messages are too large.
  • Updated the reply for Keep Alive requests from Agents to be logged in Debug log level instead of Info.
  • Updated the Agent Files to ensure the properties of the file are updated when the file is changed.
  • Updated the Switch Domain process to properly clear Agent permissions.
  • Updated the View Job Log link to not be rendered if a Job Log does not exist for a Project execution. This could occur when running a Project on an Agent that is not connected.
  • Added a confirmation step when deleting Agent and Agent group permissions.
  • Fixed the Agent message notification queue where an unnecessary limit was placed on the queue which could cause rejected notifications in environments with slow processing speed.
  • Fixed an issue where Modify, Count, and Validate RowSet tasks were not properly included in the Standard Agent feature set.
  • Fixed a potential NullPointerException that could occur when submitting a project to an Agent that is not connected.
  • Fixed an issue with the Switch Domain operation for an Agent where Agent Projects and Resources could become inaccessible after the Domain switch.
  • Fixed an issue where executing a Project could fail if an IF component was the first component in a Project. This was introduced in 5.5.0.
  • Fixed the Secure Form REST dynamic help text to describe the proper HTTP method to use for each supported operation.
  • Fixed an issue when adding a Web User virtual folder to an Agent where the Domain access was not properly being validated.
  • Fixed an issue when listing an Agent directory with a large number of files, where the message separation was not properly separating the list into multiple messages.
  • Fixed an issue where the Upgrade Agents button wasn't properly refreshed in all cases after Agents were upgraded.
  • Fixed an issue where an Agent could still run a Monitor action even after it had been disabled.
  • Fixed an issue where Agent and Agent Group permissions could be granted to an Admin User that do not belong to the same Domain.
  • Fixed an issue where the Save button was not being enabled while performing a Switch Domain for an Agent Group.
  • Fixed an issue where changing the original owner of a GoDrive file would fail when using PostgreSQL.
  • Fixed a formatting issue on the Secure Forms Access tab that could cause the SOAP and REST URL links to wrap to the next line.
  • Fixed an improper validation that occurred when REST and Web Client are enabled on the Secure Form Configuration page, but not SOAP.
  • Fixed an issue where the Agent registration process was not properly monitoring for read timeouts.
  • Fixed an issue where the View Project Folder was not properly working for Agent Schedules.
  • Fixed a validation issue on the Secure Form configuration page where the Secure Form could be saved when REST Enabled was selected but the Form URI was not specified.
Version: 5.5.1
New Features
  • Added the ability to safely embed Secure Forms in external sites without exposing the Web Client to clickjacking attacks. New global and individual form settings were added to control which forms can be embedded and from which websites if so.
  • Added the ability to use a remote GoAnywhere Agent as a Virtual Folder or Home Directory location on a Web User account.
  • Added the ability to configure a Custom URL for Amazon S3 resources to connect to non-standard service endpoints.
  • Integrated transfers to and from Agents into the Active Transfers page.
  • Updated transfers to and from Agents to properly adhere to bandwidth throttling restrictions.
  • Added a Refresh button to the Agent Manager page.
Product Enhancements
  • Enhanced the Agents Service configuration page to ensure the SSL Protocol and Enabled SSL Protocols are configured with valid values.
  • Enhanced the automatic redistribution of Agent connections to be less disruptive when a new GoAnywhere MFT system joins the cluster by ensuring no work is being performed before an Agent reconnects.
  • Improved the upload and download transfer speed when transferring files to and from an Agent.
  • Enhanced the styling to properly wrap long values on the Project Variables tab of the Add/Edit Schedule pages.
  • Enhanced the validation when accessing Agents and Agent Groups to test Resources or browse files by ensuring Agents are connected and enabled.
Other Issues
  • Updated validation to properly check for unique Agent Group names when adding or editing an Agent Group.
  • Updated the Agent to save a Monitor definition even if the snapshot fails, allowing the monitor to keep running and notifying the admin user on failure.
  • Updated the error message when loading the Project browser for an Agent or Agent Group that is not connected.
  • Updated the Edit Agent page to properly audit changes made to the Contact, Location, or Feature Set fields on an Agent.
  • Updated the restart process for an Agent by ensuring the job queue runtime is properly shut down.
  • Updated the JSESSION_ID cookie name to be unique between the Administration and Web Client interfaces.
  • Updated the Agent and Agent Group permissions pages to have a notification that is more clear to users when permissions are modified.
  • Enhanced the Secure Form validation when submitted via a RESTful web service request.
  • Updated the Agent Installer to require an alias for folder permission, which is required for an Agent to startup.
  • Updated encrypted UI fields by removing the variable dialog button when variables are not applicable to the field.
  • Updated the help text link in the Agents service configuration page to link to the proper Agents Configuration help page.
  • Updated the ID of an Agent notification record to be a Long data type to avoid hitting an avoidable limit of notification messages.
  • Updated the Job Log purge process to include cleaning up Agent Group execution log entries.
  • Updated the permission scheme for Agents to ensure Admin Users with the Agent Manager role can access the proper functionality on Agents and Agent Groups.
  • Removed the default constraint on the Created On field in the Agent notification table to allow support for older versions of MySQL that did not allow defaults on datetime field types.
  • Updated the Agent Manager list page to show Domain as the second column and Yes/No for the Connected value instead of a green/red icon.
  • Fixed an issue where purging job logs could fail in certain cases when job log files do not exist on the file system.
  • Fixed an issue where the Last Modified date of an Agent was not being updated when an Agent was modified.
  • Fixed an issue where the Expire Request setting on a Secure Mail File Request was using settings defined for sending a Secure Mail package.
  • Fixed the startup process for Agents where an Agent could shutdown instead of retrying the connection when certain failures occur.
  • Fixed an issue where the Submitted By column on the Completed Jobs page was a link for Agent jobs when it should have been basic output text.
  • Fixed an issue where Active Jobs ran by a user would not show when that user logs in with a different user name case than what is defined for their user account.
  • Fixed an issue where restarting an Agent could generate unnecessary error logs in the Agent log file.
  • Fixed an issue where the Write CSV task was not failing the Project when file system failures occurred. This issue was introduced in 5.0.0.
  • Fixed an issue where GoAnywhere MFT was not properly detecting a disrupted connection between the Agent and GoAnywhere MFT.
  • Fixed an issue in the Agent deletion process to properly unregister the agent before removing it from GoAnywhere MFT. This allows the agent to be reused if necessary.
  • Fixed an issue where the JSON Read task was failing to log the name of the RowSet variable created during execution.
  • Fixed an issue where renaming an Agent while an Agent Monitor is active could result in a Project failure when GoAnywhere MFT tries to access the files on the Agent.
  • Fixed an issue where Agent transfers could time out when the transfer takes over 60 seconds.
  • Fixed an issue where very large file paths for Job File auditing can cause the database transaction to fail.
  • Fixed an issue where Projects could not be deleted if the Project XML file was missing. This issue was introduced in 5.5.0.
  • Fixed a minor style issue on the Edit Agent page where word count assistance on text area fields were improperly bold.
  • Fixed a syntax issue in the GoDrive Search page that was causing searching to fail. This issue was introduced in 5.5.0.
  • Fixed an issue where importing a Trigger could fail in certain cases when comparing Conditions for Admin audit logging.
  • Fixed an issue where scheduling a Project with compile errors on an Agent fails to update the Schedule resulting in the job running every minute instead of adhering to the defined schedule.
  • Fixed an issue where Monitors were failing to run when more than one Monitor was defined for an Agent or Agent Group.
  • Fixed an issue where sending a Secure Mail message from the GoAnywhere HTTPS task required the Web User account to have Secure Folders access.
  • Fixed an issue with the File Chooser when working on an Agent Project where an invalid file path could be generated.
  • Fixed an issue on the Cluster Manager page where the 'Systems in Cluster' count does not properly update when a new system joins the cluster.
  • Fixed an issue where the FileInfo function available in Projects was accidentally removed in version 5.5.0.
  • Fixed an issue on the Add/Edit Secure Forms page where the REST help link incorrectly loads the SOAP WSDL URL.
  • Fixed an issue where the working directory on the Execute Native Command task was not resolving properly when running on an Agent.

Back to Top

 

Intermapper


Version: 6.1.4
  • [BUG FIX] In Device Notifiers view, the 'Count' column value now updates properly.
  • [BUG FIX] The Device Status icon in List View and Device Notifiers View is now updating properly.
  • [BUG FIX] Controls in Link Notifiers view update properly when the same map is edited by a different client.
  • [BUG FIX] Status is displayed correctly for all maps in Map List.
  • [BUG FIX] When a notifier delay has not been reached, preventing other alerts from being sent, OK notifications are also not sent.
  • [BUG FIX] InterMapper now sends SMS notifiers properly.
  • [BUG FIX] Device notifier listing in Device Notifiers context menu now displays properly.
  • [BUG FIX] When viewing only certain interfaces on a map, the hidden and shown interfaces now remain selected.
  • [BUG FIX] Intermapper no longer sends false ping probe notifications when running on OS X 10.12.1 Sierra.
  • [FEATURE] A new logging mode, activated through Telnet, has been added to support web security penetration testing. For more information see the Knowledgebase article, “Activating Web Security Logging”.
  • [BUG FIX] Flows processing now supports 32-bit interface IDs. Indexes in the Interfaces window and the Flows window now match.
  • [BUG FIX] When you right-click a link and view the Interface Notifier window, selections are now saved properly.
  • [BUG FIX] Restoring a map from a scheduled backup now works properly.
  • [BUG FIX] A problem with dropped client connections has been fixed.
  • [BUG FIX] When target server uses Server Name Indication (SNI), HTTPS Probe now connects properly.
  • [BUG FIX] A problem preventing display of the scroll bar in Link Notifier view has been fixed.
  • [BUG FIX] The Detection Map now opens properly after upgrade to 6.1.4
  • [BUG FIX] When attempting to save an Intermapper Flows report to a location for which the user doesn't have access permissions, a more informative error message appears.
  • [BUG FIX] Removed an incorrect error message about hiding of links.
  • [BUG FIX] NPE: com.dartware.util.INDEXABLE_OBJECT$HashSortedList.getInsertPosition
  • [BUG FIX] Viewing a chart from the web UI no longer causes the service to stop.

Back to Top

 

Powertech


Power Admin

Version: 2.10

New Features:

  • Power Admin now allows you to import data from CSV files in order to expedite the process of creating People and Profile Templates. For details, see Importing a CSV File.
  • Alerts now appear when Power Admin has encountered an unexpected condition, or a condition that is handled by a deviation from normal processing. For more information, see Working with Alerts.

Fixes:

  • Deleted User Profiles in Balanced Profile Pools are now recreated with the same settings as at the time of deletion.
  • Extra History records are no longer created for the “Formatting message file” each time a Power Admin Configuration Setting is changed.

Network Security

Version: 7.12
  • PIV0013 error "Object is in use" for LNSUSA02 and LUSER01 during installation has been resolved.
  • When creating a new Object List Rule, if a User or Location Rule already exists, a message is now sent and the Object List Rule is set to Inactive.

Data Thread

Version: 3.12
  • Entering of keys for record selection when submitting to batch is now allowed.

Back to Top

 

Robot


Robot Alert

Version: 5.69
  • We increased the size of Robot Alert’s message history files
  • You can now decide what you want included in the subject line of Alert messages. This includes the ability to remove the message ID, pager name, and system name from the subject line

Robot Console

Version: 6.10
  • When creating a new child resource, we check the parent’s hold status and set the resource to pending if the parent is held
  • The Traffic Manager and Console Status update programs have been revised to only send an info message to Robot Network once
  • You can now use the REPEAT, REPEATJOB, REPEATMSG, and REPEATSET OPAL variables in the same OPAL message sets
  • We increased the size of the Robot Console’s data queues from 25,000 records to 200,000 records

Robot Save

Version: 12.23
  • An issue where IFS archive data couldn’t be created if the outfile from a SAV command was greater than 2GB has been fixed.
  • Updated support for displaying media definitions with tape devices and volume identifiers.

Robot Schedule

Version: 12.12
  • An issue with Robot Schedule’s export functionality has been fixed.
  • Prerequisite jobs only display their run date and time when the job is local
  • Robot Schedule’s EVERY job interval has been updated. It can now run from 1 minute to 1429 minutes.
  • Forecast recalculations are submitted with the forecast object's original description.
  • An issue with adding commands to a job in the GUI has been fixed. If you add a library to the library list, the GUI will now successfully add commands from that library to a job.

Robot Schedule Enterprise

Version: 1.41
  • Robot Schedule Enterprise can now use TLSv1 to communicate with a Robot Network host if no other options are available.
  • We updated the Robot Schedule Agent Transponder to allow for a dynamic number of SIDs instead of a fixed maximum of 100 SIDs.

Robot Space

Version: 3.39
  • Robot Schedule job names created in the Robot Space GUI automatically correct to uppercase.

Easy View

Version: 8.34
  • We removed some unnecessary data from the EVPDFTS file and cleaned up the CHGSYS panel.

Back to Top

 

Safestone


DetectIT

Version: 14.4.8

User Profile Manager

  • General Enhancements
    • The password is no longer retrieved using Work With Export Profiles. Instead, the password is shown as “*SAME”.
  • Process Global Profile Parameter Templates by Group Profile. Global Profile Parameter Templates may now be maintained and processed using a Group Profile name. The administrator is able to maintain templates for the following ‘Profile Types’:
    • Specific Profile Name
     
    • Main Group
    as used on GRPPRF parameter
    • Supplemental Group
    as used on SUPGRPPRF parameter
  • Template Related Messages Sent to Logs. Messages are sent to DetectIT logs relating to the Profile Parameter Template processing:
    • ALC3243
    Parameter Template &2 type &3 used for profile &1
    Identifies the template name and associated (Profile) type
    • ALC3244
      type &4
    System &1 parameters updated for profile &2. Template &3
    Indicates which system record has been processed
    • ALT2310
    No suitable Profile Parameter Template found for profile &1

    For Message Id’s ALC3243 and ALC3244 a ‘Profile Type’ is included, by default to help identify the type of template used:

    • PROFILE
    Specific profile name
    • GROUP_MAIN
    Main Group Profile (i.e. based on CRTUSRPRF, GRPPRF parameter)
    • GROUP_SUPP
    Supplemental Group (i.e. based on CRTUSRPRF, SUPGRPPRF parameter)

Multiple Systems Administrator

  • Inactive Profiles Remain Enabled on HA/DR System. When a password is changed/updated within the network, the ‘Last used date’ of the IBM i profile on each remote system, is set to the current date. This prevents DetectIT from disabling the profile on a HA/DR system.
  • General Enhancements:
    • References to Older IBM Terminology Replaced. References to ‘AS/400’ and ‘OS/400’ have been replaced with ‘IBM i’ for some reports and interactive screens. The references that have been replaced were identified when reviewing the software as an end-user.
      • Message File, ALTMSGF01
        • Replaced ‘AS/400’ and ‘OS/400’ with ‘IBM i’
        • Replaced ‘PCM’ with ‘RCM’ (Message Id MLT0866)
      • DetectIT Message Id, ALT2301
        • Replaced ‘AS/400’ with ‘IBM i’
      NOTE: For a DetectIT upgrade, with ‘Transfer Data’ set to ‘Y’, the change to the DetectIT Message Id, ALT2301 is made to the stored version of the message text, not the user editable version.
  • Progress Messages for Background Jobs. Progress messages have been introduced for some background jobs. This allows operations and/or the administrator to confirm the status of specific jobs. Separate DetectIT Message Ids have been created to assist with the review:
    • ALC3245
    Start of Daily Reporting - &5. Job &4/&3/&2
    • ALC3246
    End of Daily Reporting - &5. Job &4/&3/&2
    • ALC3247
    Start of Data Collection - &5. Job &4/&3/&2
    • ALC3248
    End of Data Collection - &5. Job &4/&3/&2
    • LC3249
    A Start of Reporting - &5. Job &4/&3/&2
    • ALC3250
    End of Reporting - &5. Job &4/&3/&2
    • ALC3251
    Start of House Keeping - &5. Job &4/&3/&2
    • ALC3252
    End of House Keeping - &5. Job &4/&3/&2
    • ALC3253
    Start of Frequency Update - &5. Job &4/&3/&2
    • ALC3254
    End of Frequency Update - &5. Job &4/&3/&2
  • In-Line Processing for @MS File Reorganize. The menu option processing to reorganize physical files in @MS has been changed to prevent potential issues with file locks.
    Jobs are still submitted for each file with deleted records. However, instead of submitting 3 main jobs, all the required routines are run ‘in line’ within a single program. Previously, after the reorganize jobs had been submitted, the menu option processing would start both DetectIT subsystems. This could cause issues with file locks.
  • Documentation Updated for Version 14.4.8. All the shipped DetectIT documentation has been reviewed and updated to be compatible with version 14.4.8. This includes replacing the older IBM terminology such as AS/400, OS/400 etc., where applicable, with the current term(s).

Powerful User Passport

  • General Enhancements:
    • Message Action Item Visa Name Now Mixed Case: The Visa Name may now be entered in mixed (upper and lower) case within Message Action Item.

Bugs Fixed

  • Message Monitor indicates Action Item if message control is the only change from default values. Within the Message Monitor, a message would be shown as having an ‘Action Item’ even when ‘Message Control’ was the only value that was different from the defaults. ‘Message Control’ on its own does not determine a Message Action Item.
  • CPF3770 received by MSC326B at *N. The DSTALRTOBJ command processing program was not monitoring for CPF3770 when attempting to distribute an object that does not exist within the @MS library.
  • MSP77000 'DLTUSRPRF Values for Auto Deletion' does not delete all selected entries. When selecting Option 4 = Delete, the incorrect ‘Level’ value could be passed to the deletion API. This resulted in the API attempting to delete a non-existent entry.
  • Create new profile using Base On results in Error Message when QPWDLVL set to 3. When using the ‘Base On’ feature, the password for the new profile is cleared. With the way the password was processed, the password validation API was receiving a blank password instead of the user profile name.
  • Excessive amount of ALC2401 gets written into MSF192* files for file monitor open/close. A previous change to the file monitor data collection caused the File Open Message Id, ALC2401 to be written for every transaction that had at least one field change. It needed to be written when a change of file name was encountered.
  • Issue with updating timestamp for ALERTF2 job when using file monitor setup with user’s own journal. If the DetectIT default journal ALERTFILES, did not exist, the File Monitor data collection starting timestamp was not being updated.
  • Message about Backup DHM when attempt to delete system that is not the backup. Incorrect message displayed when attempt to delete a system that was not the Backup DHM.
  • ALERTF1 - CPF4128 Not able to allocate objects needed. The ALERTF1 could sit on MSGW due to Message Id CPF4128. This situation would occur if the Daily Reporting job ended before the submitted Reorganize Physical File job had completed.

Back to Top

 

 

Copyright © HelpSystems, LLC.
All trademarks and registered trademarks are the property of their respective owners.
Last Published: 201812060924