Monthly Release Notes - July 2017

Jump to:


Automate and Automate Enterprise (formerly Automate BPA Server)

Version: 11.0.1
  • [16352] When loading a WebSMC page on machines running Windows Server 2003 or 2008, a moving-arrow loading animation has been added.
  • [16774] When editing a Sharepoint trigger, the pencil overlay now shows appears on the Sharepoint icon.
  • [18770] The Print activity no longer gives an incorrect error message when attempting to print more than one page.
  • [18900] TLS 1.2 implementation is now compatible with Office 365.
  • [19692] Web Server Management Console folders are no longer accessible to users without proper permissions by double-click.
  • [20351] When using the Database - SQL Query activity, an Oracle Query that contains a space after the final semicolon no longer returns an error.
  • [20535] When configuring the Database - Open SQL Connection activity, a timeout value of zero (0) now results in no timeout, as indicated by in the description.
  • [20831] The IF - Folder exists activities now return correct values when a mapped drive (such as “Z:”) is used as the folder name.
  • [20873] In the File System - CSV to dataset, when referencing a multi-row dataset, an "Index out of range" error is returned when you reference an invalid row of a dataset.
  • [20892] When using the Excel - Get Cells activity and a cell contains a quotation mark ("), values are now returned correctly.
  • [20899] The File System - CSV to dataset activity now loads the dataset properly when a quotation mark (") is next to a LF (line feed) character.
  • [20952] Powershell - Run Script now runs even if a decimal is set to a comma.
  • [21040] You can now use a regular expression to exclude a file from processing when using the Compression - Decompress activity.
  • [21113] In Task Administrator, when using Database Logging, the accuracy of timestamps in database logs has been improved.
  • [21133] Workflow folders in Server Management Console now sort correctly when moving between environments in the Tasks, Conditions, Processes, Agents, Process Agents, Agent Groups, Users, User Groups folders.
  • [21158] The IF - Folder exist action's path no longer requires a '\' at the end of its path in order to work properly.
  • [21317] Fixed issues with setting values in multi-dimensional arrays.
  • [21360] The If - Condition activity now evaluates 2 or more variables correctly.
  • [21434] When Holiday Exclusion is set for a Workflow, Task, or Condition in Global Settings, and you create a Workflow with exclusions, the job now runs properly after you remove the exclusion.
  • [21484] The File System - CSV to dataset activity now converts files correctly when the final column of the final row is empty and is not followed by a line break.
  • [21553] The visual description of the 7-zip type in the Compression - Compress activity now says "7zip" instead of "SevenZip".
  • [21554] When using the 7-zip type in Compression - compress activity, you can now append to an existing archive.
  • [21627] The Email - Send message activity no longer fails when an attachment's name contains a semi-colon (";").
  • [21645] When configuring an On Task Error email in Task Builder, the PC Name length can now be 15 characters or more.
  • [21685] The Release function has been removed from the Expression Builder's Extended Functions section.
  • [21686] The Email - Send message activity now allows users to specify a proxy.
  • [21750] When you use a File System trigger to detect a change to a file or folder, changes in subfolders are now detected properly.
  • [21762] Workflow Designer no longer requires shared variables to be in a specific order.
  • [21768] When using POP3 protocol with the Email - Create Session activity, TLS encryption using SSH4 is now supported.
  • [21805] The Email - Get messages activity can now access emails from the specified "Current Folder" field.
  • [21964] The GetChar function has been removed from the Expression Guilder's Function section. Use the Mid function for similar functionality.
  • [22210] The Task name is now displayed at the top of the Task Builder window.
  • [22246] When using the Twitter action, correct error messages are now issued when a tweet has already been sent or when the message exceeds 140 characters.
  • [22260] Daylight Savings Time is now handled properly when using the Schedule trigger with Specfic Days of the week.
  • [22274] Expressions entered into the On Error or Error Causes pages of the Action Properties dialog are now parsed correctly for all activities.
  • [22276] The Automate action group is no longer enabled in Automate Enterprise.
  • [22283] When you click the Stop Task button in a task window, the task now stops correctly with no errors.
  • [22285] The title of the Management Console application has been changed to "Automate Enterprise 11 Management Console" in the Windows Start menu.
  • [22286] The "Launch BPAEM.exe" option was removed from the Windows Start menu..
  • [22287] When executing a task that references an invalid variable, the error message now says "Invalid variable reference."
  • [22288] When importing a task from Version 10 to Version 11, regions are now defined properly and include the end region.
  • [22294] In the Database - Open SQL Connection activity, you can now connect to an IBM DB2 without specifying a provider.
  • [22310] When executing a task containing a step that should cause the task to fail now stops correctly even when followed immediately by a comment now.
  • [22312] The Basic Script IDE now scales the IDE window correctly when maximized.
  • [22313] In Expression Builder, the extended function FirstDateOfDayInMonth() now returns the correct date.
  • [22314] In Expression Builder, the extended function FirstDateOfDayInQuarter() now returns the correct date.
  • [22315] In Expression Builder, the extended function FirstDateOfDayInYear() now returns the correct date.
  • [22323] Variables in tasks can now contain ']]>'.
  • [22325] When using Task Builder, you can now paste steps that contain a variable value.
  • [22326] You can now open a Version 10 .AML file that contains <![CDATA[]]> in a variable value.
  • [22328] The Automate version number now appears in the Task Builder window title bar.
  • [22329] In Expression Builder, extended function CreateODBCDateTime() now displays time in 24-hour format (matches Version 10).
  • [22330] In Expression Builder, extended function CreateODBCTime() now displays time in 24-hour format (matches Version 10).
  • [22331] In Expression Builder, extended function DriveAvailableSpace() now returns actual available hard drive space.
  • [22333] In Expression Builder, extended function DriveExists() now returns correct results for valid and invalid drive letters.
  • [22334] When using the Basic_Scripting activity's Execute action, extended function DriveExists() now returns correct results for valid and invalid drive letters.
  • [22335] The ExtractFilePath() extended function now returns only path. The file name has been removed.
  • [22336] When you run Version 10 task that uses the FileCount() extended function, it no longer returns an error.
  • [22337] The GetAutoMateVersion() extended function now returns the correct version number.
  • [22338] The GetCurrentTagText() extended function now handles ']]>' properly withn an AML tag.
  • [22341] The GetIPAddress() extended function now returns the IP address in IPv4 format.
  • [22342] The GetManagedTaskInstanceID() extended function no longer gives the "Variable or function does not exist" error message.
  • [22343] The GetProductName() extended function no longer gives the "Variable or function does not exist" error message.
  • [22344] The GetProgramsDirectory() extended function now returns the relevant program file location.
  • [22346] The Is64BitOS() extended function no longer gives the "Variable or function does not exist" error message.
  • [22347] The Is64BitTask() extended function no longer gives the "Variable or function does not exist" error message.
  • [22348] The IsActionSupported() extended function no longer gives the "Variable or function does not exist" error message.
  • [22349] The IsAM() extended function no longer gives the "Variable or function does not exist" error message.
  • [22350] The IsBPA() extended function no longer gives the "Variable or function does not exist" error message.
  • [22351] The LastDateOfWeek() extended function now returns to the last date of the current week.
  • [22352] The LastDayOfMonth() extended function now returns last day number (1-7) of the month instead of last date.
  • [22353] The LastDayOfQuarter() extended function now returns last day (1-7) of the quarter instead of last date.
  • [22354] The LastDayOfYear() extended function now returns last day (1-7) of the year instead of last date (31) of the year.
  • [22378] The GetWorkflowName() extended function is now returning with the workflow name.
  • [22379] The Exchange - Get Objects activity now lets you to retrieve a Contact list that contains groups.
  • [22384] When running a task within Task Builder, reference to a constant no longer returns an error.
  • [22385] The Compression - Compress activity now works properly in Automate Enterprise.
  • [22386] The Json - Decode activity no longer fails when called in more than one task step.
  • [22409] When you use the Variable - Create activity to create a read-only variable (READONLY="yes") an error message is no longer returned.
  • [22410] Create Variable when type is set to number now has values.
  • [22411] The Terminal - Disconnect activity now works correctly.
  • [22412] Fixed connection when using a predefined SQL.
  • [22413] Email activities using Exchange System connection now run correctly.
  • [22414] When you enter valid credentials for an Exchange server in the Server Management Console's Options -> Default Properties -> Default Task Agent Properties -> Email, (Automate Enterprise) it now connects properly.
  • [22416] When using Task Builder, you can now select and delete multiple steps even some of the selected steps do not appear in the Task Builder window.
  • [22427] If an IF condition evaluates to true, has an ELSE condition, and is looped multiple times, the loop now executes correctly.
  • [22428] You can now run a Terminal activity to connect to an IBM Power I System in Automate Enterprise.
  • [22429] The hundred-thousand-row limitation has been removed from the results of an execution_event GET call in the REST API.
  • [22456] Date and time parsing now uses a culture invariant format, reducing the number of entries in the app event log.
  • [22466] If you install only the Server Management Console's Development Tools on Windows 10 x64, the Task Builder now runs properly.
  • [22467] Functions no longer require you to pass all parameters (including optional ones).
  • [22468] AMCredProvider.dll now installs in the correct directory on Windows 10.
  • [22469] When using the Database - Open SQL Connection activity to connect to an Access database, you no longer get an error message.
  • [22470] The AM_TIMEOUT parameter now works properly when an error is encountered.
  • [22485] Task Triggering now behaves as intended when enabling it from the System Tray.
  • [22486] When you install Version 11 without removing previous versions, Automate no longer presents an error message about the connection to localhost.
  • [22489] You can now copy a variable in the Variables pane by right-clicking and choosing Copy Variable.
  • [22491] You can now restart an Automate Enterprise server without restarting Process agents that are connected to it, and the Process agents connect and execute processes correctly.
  • [22493] When using the Text - Find activity to search text containing two or more percent (%), the find now works correctly.
  • [22494] The Text - Find activity now returns an index of 0 if the search text is not in the target string, instead of an "Index out of range" error.
  • [22500] Task Administrator task logging now works properly.
  • [22504] The Text - Find activity now returns an index of 0 if the search text is a period (.), instead of an "Index out of range" error.
  • [22523] When you run a task with AM_ONERROR="Continue" set, tasks now continue when an error is encountered.
  • [22525] The Database - Open SQL connection activity now connects using an ODBC driver.
  • [22526] A task copied from a sub-workflow (Automate Enterprise) is now copied correctly.
  • [22529] When the Process Agent activity disconnects but is not shut down properly on a Linux machine, Automate Enterprise now recognizes the disconnection.
  • [22530] In Task Builder, when you open an existing step in the Action Editor within a task that creates a dataset or structure, expanders are no longer removed from the Variable pane.
  • [22533] When using the Loop - Break activity in a loop, subsequent loops in the same task are now handled correctly.
  • [22545] Task Builder now runs properly when adding a Database - SQL query action that contains a curly bracket ( { ) in the query.
  • [22575] When using Task Builder, you can now enter a multi-line value in the Task Variable value field.
  • [22579] When using an If statement to compare strings in AML, you can now use single-quoted expressions.
  • [22596] When using the Variable - Set activity, a trailing percent (%) character now results in an Invalid expression error.
  • [22597] The Go To Step error configuration option now takes the user to the correct step.
  • [22600] When using a File System trigger with the file modified prerequisite, network shares trigger only once when a file is modified.
  • [22603] The Timeout option now ends a task correctly.
  • [22606] You can now run a subtask in Task Builder when only dev tools are installed.
  • [22607] Text activities no longer fail when the target text contains two or more percent (%) symbols.
  • [22608] When System and Default Email settings are set to require Explicit or Implicit TLS/SSL, the Email - Send Message activity now requires that a certificate be specified.
  • [22609] When using File System Size, a file will now activate the trigger when it is less than 2kb different from the set size.
  • [22611] In Task Builder, when using the Json - Decode activity, structure and array properties are now available in Expression Builder unless expanded in the Variables pane.
  • [22614] You can now loop over a structure or array of structures created from the Json - Decode activity.
  • [22620] In Server Management Console, workflow exclusion of a sub-workflow is now respected by the parent workflow.
  • [22627] AML expressions now handle escaped percent (%) characters.
  • [22628] When using Visual view while setting the OnStepError event, the view now shows the correct choice after you change it from Continue to another option.
  • [22638] The %CDate()%expression no longer fails with “Type mismatch” error.
  • [22639] When the Stop Task action is set to success, it now stops the task and produces the correct message.
  • [22643] In the Database - SQL Query activity, Oracle queries now return search results when using INSERT.
  • [22655] In the Database - SQL Query activity, you can now use tasks containing datasets that were created in previous versions of Automate.
  • [22656] In the Database - SQL Query activity, you no longer have to create a dataset when running a stored procedure.
  • [22664] A workflow can now see shared variables after a sub-workflow has run
  • [22666] When using an SQL statement in a script step, you no longer have to create a dataset.
  • [22669] When running a task in Task Builder, you can now copy steps when regions are present.
  • [22671] The GetAgentName() extended function now works as expected.
  • [22708] When using the Variable - Increment activity, an empty value now increments to 1.
  • [22719] When you import a workflow in Automate Enterprise, the folder focus now remains on the current Workflows folder.
  • [22722] When using the Dialog - Message activity, escaped percentage (%%) characters are handled properly. This was fixed by #22627 above
  • [22723] The Sharepoint - Upload activity now works properly with 64-bit Automate.
  • [22738] When using the Loop - Files activity, you can now exclude a subfolder.
  • [22741] The Sharepoint - Upload activity no longer returns an "invalid characters" error when uploading from Automate Enterprise.
  • [22742] Variables now accept HTML special characters.
  • [22752] The Text - Find activity no longer gives an incorrect error message when the Start index is set to 1.
  • [22756] In Expression Builder, Filter search now works in the Local Variables (default) folder.
  • [22760] In Expression Builder, the folder content now sorts alpha-numerically.
  • [22770] The Excel - Select Cells activity now selects the correct cells.
  • [22779] When using the Action Editor to create a variable containing HTML using the Variable - Create action, load time has been sped up considerably.
  • [22781] When setting a variable using the Variable - Set activity based on the result of an expression containing specific HTML content, the expression is now evaluated properly.
  • [22782] The Database - SQL Query activity now times the connection string contains an invalid server name.
  • [22796] The Text - Find activity now returns the correct value and index.
  • [22797] When using Text - Find, numbers ending in zero are now found correctly.
  • [22802] When using the Select - Begin Case activity, the case actions continue to work in subsequent nested loop actions.
  • [22818] Expressions entered into the On Error or Error Causes pages of any activity are now evaluated correctly at runtime.
  • [22823] The Database - Stored procedure activity no longer adds spaces to SQL commands in the procedure that use the varchar variable type.

Back to Top



Stand Guard Anti Virus for IBM i

Version: 7.3
  • Stand Guard Anti-Virus now uses the new McAfee 5900 Anti-Malware Engine, which includes the following:
    • Enhanced support of JavaScript malware detection
    • Enhancements to DAT content to improve predictability of content processing
    • A new high-performance executable packer (MPRESS) to decompress executables
    • Dotfuscator .NET obfuscation functionality for string obfuscation
    • Improved support of OLE file format Platform enhancements
    • Deployment functionality has been added to Stand Guard Anti-Virus, including the ability to stage the product installation.

For more information, visit the McAfee website.

Back to Top


Document Management (RJS)

IBM i Office Integrator

Version: 1.35.1
  • Added the AUTHORITY parm in the CPY used in the OFCIFSSND command. This is not front facing but is controlled by a dtaara called OFCCPYAUT. It has three values: *OBJ (default), *INDIR, and *INDIROBJ.

Webdocs Windows

Version: 1.9.2


  • Significantly improved performance of the search indexing resulting in faster index rebuilds and quicker appearance of document results for newly added documents.


  • Fixed an issue with the “Contains” search type behaving as a “Starts With” instead
  • Fixed an issue with the “Title” column not being selectable by users to set show or hide preferences

Webdocs Tray Capture

Version: 2.0.22


  • Removed “Select Scanner” from context menu to simplify configuration.
  • Updated Tray Capture to use Microsoft .Net Framework 4.5.2.
  • Updated Tray Capture to use GdPicture 14.
  • Simplified the WebDocs logon process so it doesn’t prompt for user and password, since it’s specified in Settings.


  • Fixed issue with job logs on the System I not ending when performing “Log Out”.
  • Fixed the order of the User and Password in settings so that the User setting comes before the Password setting.
  • Fixed Scan button so that it disables when the WebDocs user is logged out.

Back to Top



Version 5.5.7
  • Fixed an issue with the Custom Report Task that was preventing it from running. This issue was introduced in 5.5.6.
Version 5.5.6
  • Updated the GoAnywhere database upgrade process to share a single database connection for all changes across all upgrade versions.
  • Updated the Admin Revision History Report Task to properly validate when no components are selected.
  • Fixed a database transaction lock issue that was encountered when updating an Agent.
  • Fixed a NullPointerException that could occur when running a project with the Admin User Activity Details report from the Scheduler or GoAnywhere Command.
  • Fixed an error when loading the Project History page that would occur when the project no longer exists.

Back to Top



IBM i Level 1 to 4 Product Suites inclusive

Version: 7.0

(PTF 2017.069_2)

  • The Job Log Monitor had a very high I/O to some Halcyon files. This has been corrected.
  • Export from 'Work with Rules' (WRKRULES) for an *ALL output Queue or Job Queue Group would fail as it incorrectly used *ALL for the Group rather than *GRPALL. This has been corrected.
  • Message Communicator would reject an inbound email address if the system was set to a non-USA CCSID due to translation issues with the '@' symbol. This has been corrected.
  • Message Monitor was incorrectly handling a message from a third party application. This has been corrected.

Back to Top



Version: 1.14

Back to Top



Version: 6.1.5
  • The Device Notifiers window now refreshes correctly.
  • OK status notifications without a prior alert
  • Changes to maps and background images are now reflected in the Splunk app.
  • Background images now appear correctly when you print a map.
  • The Splunk app now displays events counts correctly.
  • Printing of the Summary of Notifcations in the Splunk app has been improved.
  • The Splunk app Devices menu has been removed from the Splunk app. All access to devices is available from the Device List page.
  • When Devices are associated with multiple probes, the Splunk app's Device List page now shows the status of each of the device's probes correctly.
  • Notifications in the Splunk app are now in sync with Intermapper notifications.
  • Intermapper now installs a more secure version of Java 8 Runtime Environment.
  • When starting Intermapper Datacenter on a new installation, the database is created correctly on all platforms.
  • Intermapper Flows server now starts properly after installation on all platforms.
  • The Flows window can now be closed after the Flows server has been stopped.
  • An issue with opening Link Notifiers View on certain maps in Intermapper Remote Access has been fixed.
  • The Splunk app no longer shows devices from the Detection Map.
  • An issue with sorting in the Device Notifiers view has been fixed.
  • Flows window is now disabled when the Flows Server is stopped.
  • Apostrophes in device names are now supported fully.
  • The Device Notifier view now works properly with the Detection Map.
  • To eliminate confusion, the Detection Map is no longer available through the Intermapper Web Server.
  • Probe groups now save changes properly when in Device Notifier view.
  • Delay and Repeat setting in Device Notifiers view are now saved correctly.
  • The specified default map (if it exists) is now displayed correctly in Splunk.

Back to Top



Access Authenticator

Version: 1.0

Access Authenticator has been released. Access Authenticator allows you to implement multi-factor authentication across your IBM i environment.

Key Features:

  • Comprehensive Authentication Manager. Access Authenticator is administered from the HelpSystems Insite web interface. The authentication manager is a powerful tool that makes it easy to configure multi-factor authentication to meet your organization’s needs.
    From here, you can import users from Active Directory, invite users to the self-service portal, and activate or deactivate multi-factor authentication for users and groups. Users can also be disabled without removing them from the database altogether.
  • Intuitive User Portal. The self-service portal allows users to complete the Access Authenticator registration process. This easy-to-use portal is also where users maintain their authentication credentials and update their options.
    In compliance with PCI DSS 8.2.2, which requires users to verify their identities before modifying any authentication credentials, users must verify their usernames and passwords before making changes to their accounts.
  • Multiple Authentication Methods. Access Authenticator allows administrators to select from several different methods of authentication for your users’ convenience and to meet your organization’s security requirements including:

    • YubiKey integration

    • One-time password generation

    • Push notifications

    • Biometric fingerprint scanning

See Access Authenticator for more product details.

See Access Authenticator Reference Manual for product documentation.

Stand Guard Anti Virus for IBM i

Version: 7.3
  • Stand Guard Anti-Virus now uses the new McAfee 5900 Anti-Malware Engine, which includes the following:
    • Enhanced support of JavaScript malware detection
    • Enhancements to DAT content to improve predictability of content processing
    • A new high-performance executable packer (MPRESS) to decompress executables
    • Dotfuscator .NET obfuscation functionality for string obfuscation
    • Improved support of OLE file format Platform enhancements
    • Deployment functionality has been added to Stand Guard Anti-Virus, including the ability to stage the product installation.

For more information, visit the McAfee website.

Power Admin

Version: 2.11

Power Admin Fixes:

  • Power Admin now automatically corrects objects that are known to occasionally become damaged (User Index; Data Queue).

Central Administration Fixes:

NOTE: These are the Central Administration fixes accompanying this Power Admin release. Central Administration is Powertech's central management console designed to allow one security officer the power to create, manage, distribute, audit, and enforce policy for many systems throughout an organization from one central location.
  • A job’s library list is now returned to its original state after Central Administration processes a user profile function that was processed by Power Admin's exit point programs.
  • The PPLCMNSVR monitor job had a built-in feature that was acknowledging the QSTGLOWLMT system value. That feature was added to better handle an IBM i system defect that at one time was not in all base OS releases. That PTF is now included in all base releases, so this built-in feature has been removed.
  • Event processing and integrity improvements have been added.
  • Entering the History Browser no longer results in Message ID CPF2419 and/or CTL0001 in the job log.
  • The PPLCMNMON monitor job is no longer unable to start due to the /tmp directory being so large that the Unix stat function fails with error “Object is too large to process”. The stat function has been replaced with stat64, which is specifically designed to handle larger objects.

Crypto Complete

Version: 3.54
  • Enhanced the External Key Manager to work with Key Managers that use the Key Management Interoperability Protocol(KMIP) standard. Crypto can work with external key managers that use the encoding types TTLV or XML. Crypto can also connect to servers that use SSL over TCP or HTTPS connections.
  • Enhanced the Create Symmetric Key (CRTSYMKEY) command to add a new option Create External Key (CRTEXTKEY) when using either type *KMIP or *VORMETRIC. This allows the key to be generated on the *KMIP or *VORMETRIC server if the key does not already exist.

Back to Top





New Features

  • Advanced Datasource filters for 'out-of-the-box' SQL Server User Logons Datasource Template within Alignia Business Security module.
  • A new Database Generic Query Errors Check for Business Applications.


  • 2-60132590 - When deleting a used credential it was not possible to reconfigure the asset. This has been fixed.
  • 2-60570816 / 2-60182141 - Stopping the Orchestrator service caused a message to be displayed stating that the Orchestrator service had ended unexpectedly. This was caused by exceptions of the type: Unhandled exception at 0x58DE7963 (MDB_Server.dll) in MdbServer_MiniDump_20170322.dmp: 0xC0000005: Access violation reading location 0x00000004. The issue has been corrected and the Orchestrator service can be stopped normally.
  • 2-60250631 - Some Online Business Services monitors in Alignia ThinkServer caused an unlimited growth of database user connections as the number of connections was not limited. This meant the number of connections could grow unchecked resulting in an impact on the performance of the database engine. This has been fixed.
  • 2-58419492 - Support has been added for writing multi-byte characters to databases with multi-byte collations. This is disabled by default to improve performance. To enable this feature, add the parameter <supportMultiByteCharacterDatabases> to T4BD.config. Messages collected by EventLog monitors that contained multi-byte characters would sometimes fail to be written to databases with collations that support multi-byte characters.
  • Some Device elements were monitored as having 'No Core' assigned even if they were configured as 'Role Core'. Therefore, potential issues with Device Core health were not reported as they should have been. This has been fixed.
  • The availability percentage shown in the Business Applications Availability Manager page was different to the one shown in the report created by using the link "Create Report" from the same page. For periods not ended, the report availability percentage was being calculated using the whole time period rather than just the period up to the current time. This has been fixed.
  • A 'Maximum request length exceeded' error message was generated when importing a file greater than 20 MBs into Alignia Business Applications. Furthermore, in some cases the import process failed due to a Microsoft SQL Server deadlock. The issue was caused by the web.config file having a maximum file size limit of 20 MB. This has now been increased. The SQL Server deadlock problem was caused by some queries that were blocking the database.
  • The creation and/or modification of Business Views in SmartConsole and of Monitors in ThinkServer has been improved whenever the user performs any change in an asset. Issues that arose when synchronizing monitors with remote ThinkServer have been resolved. Currently the changes are evaluated sequentially in a queue. The process has been improved to synchronize each asset and evaluate when there are multiple pending evaluations.
  • Online Business Services alerts did not work correctly for KPI, Real & Simulated Experience definitions with some "All" values defined for Channel, Function and Consumers. If the summary definitions contained at least one value of 'All' and aggregate data from more than one specific business instance, this aggregation was not performed correctly. This has been fixed.
  • 2-61778871 - When editing a macro, if the user clicked on a date in the calendar, the "Save" button did not appear. The issue has been fixed.
  • 2-61792221 Online Business Services response time alerts may not have reported correct values for the number of transactions and average response time for both Real & Simulated Experience data. For example, zero transactions and response times may have been reported when transactions actually existed. This issue has been fixed.
  • When selecting columns to be displayed or hidden in the OBS Summary table, the change was not processed and after saving, the selection did not take effect. The selection engine of the columns in the OBS summary table reported a problem when selecting columns to display or hide. This has been fixed.
  • The data recollection process for Linux physical and virtual memory has been changed. The Linux monitors for physical/virtual memory and CPU usage would sometimes fail if the monitored asset was running a very old version of procps.
  • Windows EventLog Agent. When using Automatic Recollection to retrieve EventLog messages and the Datasource recollection fails, the reported error (in Alignia Web and ThinkServer Configurator) was always: 'Exception in EvLgDataSource::RecollectData. Operation: RecollectEvents Error: Exception while retrieving EventLog events'. In order to see the full details you needed to open the actual log file. The error was correctly recorded in the log file but instead of including the actual information in the generated exception, a generic message was always used instead. This has been fixed.
  • The Job name did not appear in any of the normalized variables of the "User Activity > User Statement > Command execution" event retrieved during the audit of IBM i systems CD journal entries. This information has been added into the Application normalized variable.
  • 2-56177007 - The links generated for the "Execute again" feature did not contain the original start time of the macro. This resulted in the reports, whose date range was relative to the current date, being executed with a different date range to the one that originally failed. The issue has been fixed and now the links contain the original start time of the macro.
  • 2-62069203 - When using Database Settings Administrator and loading the PMDB tab (under the Maintenance section), an error page was sometimes displayed. This issue has been fixed.
  • 2-61945153 - If the user resets the filters in the grid on the Forensic Analysis page, the headers of the columns to which filters were applied are displayed as though the filter is still active. This issue has been fixed.
  • A fix has been applied so that the correct labels for the Architecture section are displayed when adding or editing a Connectivity Group within Business Applications. The issue was caused by the text labels not being updated.
  • Copying an asset that is being monitored creates the copied asset as active. This results in the same asset being monitored twice, creating lot of duplicate events and data. Furthermore, there was an issue with Security assets because the enabling of the asset monitors was not performed, so the monitors in ThinkServer were not created. When copying an asset, only Processes were created in a deactivated state. From this version onward, all copied assets will use this behavior. Furthermore, another issue existed whereby the copied asset was not then processed.
  • When importing an XML that included an asset with an unexpected attribute, the full import process failed with a message error such as: Exception importing Entities. Error: The attribute type 'attribute_type' is not applicable to assets of type: 'Asset_type'. When importing assets, a check is made that all the attribute types can be imported. If any of them failed then the full import process was canceled to avoid an inconsistent status. Now, if the attribute type is not valid for an asset, it is ignored and the import of the remaining attributes and assets continues.
  • When importing an asset, existing templates assignments were not removed but templates defined in the imported file were added. The correct behavior should be that in cases where the imported file indicates that an asset has templates assigned only these templates should be included after the importing process is complete. Any previous template assignment should be removed. Previously, imported template assignments were added to existing assignments. Any existing template assignments are now overridden.
  • Sometimes when starting Orchestrator, and the SQL Server was temporarily unavailable or starting, Orchestrator didn't operate properly even when the SQL Server started. The easiest way to check if this was happening was by trying to use Alignia Business Applications Configuration because the list of Devices or Applications was never retrieved from the server. In some cases there was a deadlock when the ODBC connection was reset so it never recovered from this status condition. This has been fixed.
  • The Analysis tab of websites in Alignia, now shows the Transfer Start Time graph instead of the Transfer Total Time. The description of the graphs has been changed to avoid confusion.
  • 2-57624461 - Creating a report from the Availability Manager page resulted in the percentage value in the report being different to the one displayed on-screen. This error occurred because the report didn't use the calendar associated with the Asset. The SLA calculation now uses the appropriate asset calendar.
  • 2-61322801 - There was an error accessing "Management > General Settings" from the SmartConsole Web Client. The Security model for SmartConsole Web Client was not being created correctly. This has been fixed.
  • Orchestrator failed to start if was unable to connect to SharedObjects. Orchestrator would start even if a connection to SharedObjects could not be made. It would then crash at the first attempt to access any object that needed to be loaded from SharedObjects. This has been fixed.
  • The user custom templates for ThinkServer Monitors messages were lost after an upgrade due to a defect in the installer. This has been fixed.
  • The content of the folders "ThinkServer\ts_shared_referentials\Business Consumers" and "ThinkServer\ts_shared_referentials\Integrations" were not maintained after an upgrade due to an issue in the installation routine. This has been fixed.
  • 2-61617502 - When editing a Security Asset, switching to the "Actions to Audit" tab and enabling monitoring of the asset while the tab is still loading resulted in the monitoring request not being actioned. This issue has been fixed.
  • A bug in Inspector, the Event Control Engine, caused operations-related events (including Business Processes events) to be stored out-of-sequence. This caused SmartConsole based products to behave unexpectedly as the status of a monitored asset depends on sequentially generated events. This has been fixed.
  • An error in the VMWare 'out of the box' template in Alignia for Business Security caused the permissions addition to a role to remain undetected. This issue has been corrected.
  • The single sign-on utility did not work on SmartConsole WebClient and SharedObjects. The product asked for credentials even when the user had previously signed-on to another Alignia Web application. This has been fixed.
  • Architecture Load Balancer is not shown when editing an Application or a Connectivity Group. This was due to an issue in the Application and Connectivity Group edition and the asset was always shown as "Non Cluster".
  • 2-62257181 - Attempting to change a scheduled task macro that was running resulted in a programming error message being displayed. The issue has been fixed and now the correct error message is now displayed.
  • A single event can match multiple security controls. When a controlled event was opened on the Forensic Analysis page in order to view its details, the subsequent Event Details page displayed the details for the first controlled event instead of displaying the details for the event that had a higher security Impact. A code error resulted in the first event always being selected. This has been fixed.
  • A Python code error on Alignia for Business Security Oracle 'out-of-the-box' template:Health has changed to Monitoring error due to some errors in the script. This has been corrected.
  • Business Security. When the user changes the Security Regulations of an asset, the existing ThinkServer Monitors change to monitor "LocalHost" instead of the correct Device. Furthermore, these monitors were not deleted when Security monitoring is deactivated. The change in Security Regulation was not processed as a change in the Device. which caused issues during the creation of ThinkServer Monitors. This has been fixed.
  • PostgreSQL standalone application metrics were not displayed (No data was displayed instead) as the metrics definition was not created properly. This has been fixed.
  • 2-63112701 - Business Applications IBM i Job Activity Monitor was not detecting an inactive job due to an error in the active jobs count. This has been fixed.
  • Events were not correctly arriving in the SmartConsole from environments with multi-byte characters. This has been fixed.
  • Devices created within Business Security contained a wrong value if the Device was then renamed. Devices created in previous versions would have a wrong value assigned in the 'NetworkInterfaceUsedForMonitoring' attribute if they were later renamed because the previous value was retained. Both issues have now been fixed. In some instances, the processing of the 'NetworkInterfaceUsedForMonitoring' attribute was wrong. Additionally, possible wrong values in the database were not corrected.
  • 2-62450541 - Business Security Windows Eventlog Custom collector was not filtering by subaction. The subaction filter was not being executed and therefore all the events were bypassing all of the subaction filters. This has been fixed.
  • After creating a Connectivity Group Cluster, a renaming action displayed a pop up window asking if you wanted to change the asset model. A bad reference to the entity tree made the editor think that the type had changed. This has been fixed.
  • Sometimes, reports based on the Custom Event List template were displaying graphs that were unreadable. This behavior was caused by the values of the X axis being too large to properly fit the display and has now been fixed.
  • Errors were found when importing assets whose relationships with another assets were a subset of the relationships already defined in the Database. In these instances, the existing dependencies were used instead of being overridden by the imported ones. For example, if an exported security asset has a security regulation "A" assigned and is imported when the existing asset had regulations "A" and "B" assigned, then the existing values are used, instead of just "A". There was an issue processing asset relationships that has now been corrected.
  • 2-63299204: When using Internet Explorer, the Forensic Analysis grid was unfiltered when opened. This has been fixed.
  • After upgrading Alignia from pre-Business Security versions, the Event Control Service was not able to insert events in the database. When upgrading from previous versions that used a database schema version older than v7 (i.e. Pre-Alignia Business Security versions), the database model upgrade procedure failed. As the database model was not up-to-date, events could not be inserted. This has been fixed.
  • 2-62137937 - There was an inconsistency of SLA percentage between Availability Manager, Dashboards and Reports. Availability Manager was calculating the SLA percentage using only the period up until the current time and Dashboards and Reports were using the full period. This has been fixed.
  • In Business Processes, when a Task had a Datasource assigned (as defined in the Data Collection tab) that used a specific credential, it was not read from the configuration. When the Process was reloaded, the credential used was "Monitoring node default credential (inherited from process)". The configuration routine didn't read the credential section from the configuration file. It always used the default setting "Monitoring node default credential (inherited from process)". This has been fixed.
  • It was not possible to modify the interface where the Syslog listener was attached. Sometimes the datasource was retrieving wrong values from the DeviceIP, and returning the following error: "Error in UDP syslog listener. ErrorCode: -1 Error message: Error opening UDP port. Probably the UDP port is being used by another application". A Syslog credential selection has been added for the datasource. It now works in exactly the same way as the basic Syslog ThinAgent, which takes a device and a credential. Selecting the proper listening interface, port and protocol in the credential now resolves the above issue. For existing installations; apply this patch, and then assign a proper Syslog credential.
  • A timeout error in Business Process Configurator existed when resetting a Business Process. In the PMDB log file, an error was logged containing the message "An expression of non-boolean type specified in a context where a condition is expected, near ')'.". The SQL sentence used to delete records was incorrect and furthermore, the Orchestrator code continued to wait for the operation to end, even when the error had been already reported. This has been fixed.

Back to Top



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