Release Notes > Release Notes Version 10

Release Notes - AE Version 10

Highlights


Service Packs

[Highlights][Service Packs] [Notes for Update Installation] [What's New][Improvements][Bug Fixes] [Known Issues]

Service Packs include error corrections. It is possible though, that a Service Pack contains minor changes. If so, they are listed in this section.

Service Pack 7

General

Trace Added for the AE DB Change Utility

You can now set trace in the UCYBCHNG.INI file for the AE DB Change utility.

Service Pack 6

General

Specifying Whether Sync Objects Are Checked When Restarting a Canceled Job Without an Abend Action

The new key SYNC_CHECK_RESTART in the UC_SYSTEM_SETTINGS variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. determines whether Sync objects are checked when restarting a canceled jobAn Automation Engine object type for a process that runs on a target system. without an Abend actionActions are predefined building blocks for recurring activities. They are commonly used for managing third party systems or in deployment scenarios.. It defaults to Y for yes to keep with the v9 behavior.

In previous v10 releases, this variable did not exist and the behavior was that the Sync objectIt synchronizes executable objects based on defined states and actions. A particular Automation Engine object type. was not checked and jobs were restarted immediately.

ServiceManagerA program that facilitates the starts and stops of Automation Engine components. Utility for UNIX No Longer Needs to Be Started with SetUID Bit

Due to a fix added to AE 11.2.0, 11.1.2, 10.0.6, and 9.13.0, the ServiceManager utility for UNIX no longer needs to be started with SetUID Bit.

Service Pack 5

General

Script Function GET_VAR Changed

The behavior of the Script functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… GET_VAR has been re-established. In previous versionsAn application version holds zero or more deployment packages and may have dependencies to zero or more application versions of the same (or to different) applications of the Automation Engine GET_VAR did not resolve recursively. In versions 9SP4 to 10SP4 GET_VAR resolved recursively.
Now GET_VAR does not resolve recursively anymore and the respective key in UC_SYSTEM_SETTINGS has been removed.

New Postcondition Action - ABORT

The new ABORT action is available on the Postconditions tab for workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."] tasks. It sets the task to an abort statusThis represents the condition of a task (such as active, blocked, generating)..

Service Pack 4

General

UC_SYSTEM_SETTINGS

The maximum value for the setting MAX_IMPORT_SIZE that defines the maximum size (KB) of an XML fileA format for imports and exports. An XML file contains object structures. that should be imported has been increased to 30720. This is also important when you want to save files that exceed 3MB. In this case, you also need to define the setting maxMsgSize=4000000 (or more) in the [TCP/IP] section of the CP Server INI file (UCSRVCP.EXE).

OS/400 Agent

This agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host's INI file now uses parentheses () around section names instead of square brackets [].

Script Function ACTIVATE_UC_OBJECT Change

When starting a task out of !SCRIPT from an eventAction that is triggered if particular conditions apply. It can be an Automation Engine object type or an entry in a Policy Orchestrator EventBase. (Time Event) using ACTIVATE_UC_OBJECT, the started job will have the event's run number as PARENT ID (RunIDShort for "run number". It is a number that provides unique information about a task's execution. The RunID can include 7 to 10 digits. It is assigned by the Automation Engine component .).

Script Statement :RSET Change

After a restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts., the script statement :RSET now returns the value of the script variableA placeholder for a value within a script. (as in v8) and no longer a space.

New Job Status Capturing and Tracking Function for OS/400 Jobs

In order to be able to take immediate action, the possibility to query job statuses of OS/400 jobs has been added. Using SQL statements you may not only display a listShows entities in a grid view of jobs that are in the MSGW (=waiting for messages) status, which might require additional actions. You also may get detailed information about the execution and status of the jobs in question.

New Parameter Available for z/OS Agent

For the configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. of the z/OS agent a new parameter is available: "jobSubmitContext=" can be set to one of two values, AGENT or USER, whereby the Job will be submitted to the internal reader either in the agent context or in the context of the userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management., who has been specified in the Login objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task of the Job.

Service Pack 3

General

Script Function CONV_DATE Changes

For the script function CONV_DATE changes of SP2 have been reversed. To ensure compatibility with version 9 of the Automation Engine and the script function WEEKDAY_XX, the weekdays will again be delivered in two uppercase letters based on German.

 

 

Service Pack 2

General

UI Plug-in

The Automation Engine plug-in for the Enterprise Control CenterAutomic's web application that provides a single, browser-based interface for the ONE Automation platform. is no longer included with Automation Engine. Reason: From Enterprise Control Center Version 2.1 and higher, all plug-ins (and also the AE UI plug-in) can be found in ECCAbbreviation for the Enterprise Control Center's WAR file. The configuration instructions and UI plug-in Release Notes have been removed from the documentation and can now be found in the ECC installation documentation.

 

Documentation
ClearView has been renamed to Process AnalyticsAn Automic graphical analysis tool that displays the activities, statistical data and forecast data per Automation Engine system client in a bar diagram and that can be used to calculate the critical path. [Formerly called "ClearView," "Graphical Workload Analyzer," or "JobMonitoringStudio (JMS)."].

Documentation: File Name Change

The names of the files that are used to access the documentation have changed. The new names are as follows:

  • HtmlHelp: help.chm
  • WebHelp: help.htm
  • Message documentation: Messages.chm/Messages.htm

Renaming of Documentation Chapters

The following chapters have been renamed as follows:

As a consequence, the names of the supplied CHM files have also changed in the HtmlHelp documentation. The new names are as follows: AutomationEngineScriptGuide.chm, InsideAutomationEngine.chm, BestPracticesGuide.chm, ProcessAnalytics.chm.

Service Pack 1

This Service Pack contains no changes.


Notes for Update Installation

[Highlights] [Service Packs] [Notes for Update Installation] [What's New] [Improvements] [Bug Fixes] [Known Issues]

Make sure that your IT environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. complies with the system requirements of the Automation Engine version in question before you start the installation process. You will find a PDF list of supported platforms and versions in the Automic Download Center.

Important note: As of v10, components that run under Windows require the Microsoft Visual C++ Redistributable Package Version 2010.

As of v10, the agent for OracleApplications will no longer be supplied. Note that the job templatesPre-defined 'workflows' for specific components/tasks, e.g. Tomcat, SubVersion. will still be available.

As of v10, file transfers will be processed asynchronously, which improves performance. This improvement has been achieved by changing the default values of the settings FT_ASYNC_QUIT_* in the variable UC_HOSTCHAR_*.
In v9, the default values of these settings had the effect that file transfers were processed synchronously. Note that they will still be processed synchronously after an update to v10. To change this behavior, you need to specify the required settings in the  variable UC_HOSTCHAR_*.

The AE.WebInterfaceDeprecated Term. is no longer supplied or supported as of Version 10. All the related documentation topics have been removed.
For handling the Automation Engine via a web browser, you can now use Enterprise Control Center.

Oracle versions 9, 10 and 11g1 are no longer supported. For the Automation Engine and the utilitiesUtilities support the execution of administrative tasks in an Automation Engine system (such as reorganizing and archiving the Automation Engine database)., this means that the library ucuoci is only provided for Oracle version 11g2. The upside is that there is no need to rename this during the installation process.

IBM DB2 versions 9.1 and 9.5 are no longer supported for the AE databaseA database is an organized collection of data including relevant data structures. and the Database Agent.

The UNIX agent and the utilities for HP-UX are no longer provided for the PA-risc architecture.

The UNIX agent is no longer supported for SCO Unixware.

As of version 10, the INI-file parameters "reorg_mode=", "suppress_output=", "max_rt_number=" and "show_stats=" of the utility AE DB.Unload are meaningless.
The reason is that this utility now uses only the new deletion method.
In the new deletion method it is essential that no REORG files are created during the database reorganization process. This is the same behavior as with the parameter setting suppress_output=1 which always suppresses the generation of REORG files.
So far, you could define the method for deleting data by using the INI-file parameter reorg_mode= ([REORG] section; old method: reorg_mode=0, new method: reorg_mode=1). The old deletion method consumed a lot of memory and could eventually cause performance problems.

The folderTop level entities such as Environment, Deployment Target, Activity, … are stored in folders. The permissions a user has on an entity depend on the permissions that are set on the folder for the entities. structure of the supplied documentation has changed. The folders "uc4" (this includes "htmlhelp") and "unix" are now located in the directory "Guides" . The new folder "Release Notes" includes the Release Notes for Automation Engine and the UI plug-in as PDFs.

As of v10, MS SQL Server 2005 is no longer supported for the AE database, the utilities, and the Database Agents.

The MBean for SAP ACC is no longer supplied or supported. The related documentation topics have been removed.

The databases Microsoft Access and SAP MaxDB are no longer supported for the Database Agent.

The components AutomationEngine, ServiceManager, agents and utilities for Windows and Linux are no longer supported on Itanium processors.

Workflow tasks that are waiting for their starting time now appear blue in the monitor.

Java Application Interface: The measurement unit for the method DeactivateCondition.setDelay(n) has been changed from days to minutes. To indicate a delay of one day, you must now specify the value 1440 instead of 1. Keep in mind that you must adjust existing Java codes correspondingly.

The names of the files that are used to access the documentation have changed. The new names are as follows:

When upgrading from v8 to v10, object variablesPlaceholder for values that are stored in an object's "Variables & Prompts" tab/section. (:PSET, PASS_VALUES) may not correctly be inherited when the workflow- or task-generation process has already started in v8 and continues in v10 (generating at runtime, for example). Automic recommends setting such workflows inactive before starting the upgrade process.

Rollback function restricted: Since "Deactivate (forced)" has now been enabled for sub-workflows, a workflow's rollback function will fail for sub-workflows, which have already been deactivated by the "Deactivate (forced)" function, as the sub-workflowA workflow that is part of a different workflow. is no longer available in activitiesDeployment-related activities.

In previous releases, the CANCEL_UC_OBJECT script function could be used for ended tasks to triggered a deactivation. This is not possible any more. Now you need to use the DEACTIVATE_UC_OBJECTscript function instead.

As of v10, to use PromptSets within an activityAn activity (or task) is an entity that can be planned, assigned to a user or a team and tracked with respect to their plan and state (started, cancelled, suspended, completed)., users has to have "X" execute permissions defined for PromptSet objects in their User objects' Authorizations tab

As of v10, the Webhelpsplitter tool is no longer supplied or supported.

As of v10, if a task uses a sync and has a START and END action defined, but no ABEND action, then during a restart on abend, it does not execute the START action again. This is because no END action has been executed.

Instead of the former term "Modification Archive", AE now uses "Release Notes" in all languages. This applies to the Automation Engine documentation, the supplied files, and the Automic Download CenterThe Download Center (http://downloads.automic.com/) is the place where you find everything you need to know about your Automic solution to make sure you are using our products to their fullest potential..

The folder "Docu", which is part of the supplied disk image, has been renamed to "Documentation".

As of v10, object variables and PromptSet variables can be used within the bind parameters of SQL SECURE-type and SQLI SECURE-type VARA objects.

As of v10, it is possible to redefine variables with :DEFINE that are already defined by :SET.


New Functions

General

New Automation Engine versioning

As of Version 10, a Automation Engine version number is composed of the following characters:
x.y.z-pre+build.nnn

Example of a complete version number:
10.2.1-dev+build.234

For more detailed information, refer to the chapter Automation Engine Version Indicators.

 

Executable Objects Now Include the New Option "Active"

The new option Active, which is available in the Header tab of executable objects, lets you make tasks inactive through their object definition. When the option Active is not set, a task's execution will be skipped and it obtains the new status ENDED_INACTIVE_OBJECT (return code1925).

A new query is available in the UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."] (Inactive Workflow Tasks). You can turn this on or off in the settings. This query appears when you try to insert an object into a workflow despite it having been made inactive in its object definition (= the option Active in the Header tab is not set).

A subsequent change of the Active option does not affect active long-running tasks (such as Schedule objects, RemoteTaskManagers, and groups).

 

Allowing Specific Characters within the Alias Names of Workflow Tasks

You can now use the new setting ALIAS_SPECIAL_CHARACTERS in the variable UC_CLIENT_SETTINGS to allow the use of specific characters in the alias names of workflow tasks. Characters that are usually not allowed (such as "-") can now be used in alias names.

 

New Predefined Variables

  • &$MRT# - The object's maximum runtime in seconds.
  • &$RUNTIME# - The task's current runtime in seconds.
  • &$SRT# - The object's minimum runtime in seconds.
 

New Object Type: Dashboard

The new Dashboard object can exclusively be used with the product Enterprise Control Center (ECC), which is a web interface that allows you to access various products. The Dashboard object does not provide functions for the Automation Engine and only includes a Header tab and a Documentation tab.

To use dashboards in ECC, simply create them in the Automation Engine and assign the relevant rights.

 
New Functions
 
 

 

UserInterface

Activity Window: Filter for Remote Status

With the new Filter option, you can reduce the contents of the Activity Window to a specified remote status. This applies to SAP jobs, database jobs, RA jobs, and the SAP RemoteTaskManagerIt monitors and controls external Jobs that were not started by the Automation Engine (AE). An AE object type. [Formerly called "QueueManager."].

 

Output Scan Tab: New "Status Text" Column

The Output Scan tab (available in jobs, file transfers, and the RemoteTaskManager) now includes the new column Status Text. Here, you can enter any value that will be used as the task's remote status when the filter definition applies.

 

PromptSet Objects: New Property "Custom field"

All elements of PromptSet objects now include the new property Custom field. You can enter any text of your choice in this text field; it will not affect any of the functionality.

You can even read this text by using the new script element PREP_PROCESS_PROMPTSET.

 

Selective Statistics: New "Remote Context" Tab

With the new "Remote Context" tab, you can filter the statisticsThis is a list of a task's previous runs. for RA attributes and specific parameters of the SAP Solution Manager. For more information, see the tab's documentation.

 

RA - Connection Objects: Traffic-Light Symbols Signal Connection Status

When you open RA Connection objects, the system now verifies whether a corresponding agent is active and whether a connection is possible. The new traffic-light symbol now shows the connection status in the specific CONN-object tab.

 

 

SAP Agent

New Script Elements R3_IMPORT_CALENDAR and R3_IMPORT_JOBS

You can now use the new SAP functions R3_IMPORT_CALENDAR and R3_IMPORT_JOBSto transfer jobs and calendarsShows a calendar overview of activities, releases or reservations. from a SAP system to AE.

R3_IMPORT_JOBSimports all jobs from SAP that have been selected via the script element R3_GET_JOBS. In addition to SAP Job objects, you can also create Workflow objects and Login objects.

R3_IMPORT_CALENDARtransfers the days of a specific SAP factory calendarAn Automation Engine object type that defines a set of days based on calendar keywords. or holiday calendar to a Calendar object.

 

Script Element R3_GET_JOB_SPOOL: New XLS Format for Output File

The parameter FORMAT= in the SAP script element R3_GET_JOB_SPOOL now includes the new option "DAT". Use this to save the output file (FILE=) in XLS format (table).

 

SAP Forms: Long Names of Output Files Displayed

The Forms tab for SAP jobs now shows the long name of the selected output device (parameter DEST[INATION]=) and is available in R3_ACTIVATE_REPORT, for example. The long name is displayed to the right of the text field, provided that the Forms are connected to the SAP system.

This is an additional view in the Forms. You can still use the output device's short name as a parameter value.

 

R3_ACTIVATE_JOBS - New Parameter NO_DATE

The parameter NO_DATE is now available in the SAP script elements R3_ACTIVATE_JOBS and R3_ACTIVATE_INTERCEPTED_JOBS (to date only available in R3_GET_JOBS). You can thus start jobs without specifying a start time.

 

R3_COPY_VARIANT - New Parameter PROTECTED

Use the new parameter PROTECTED= in the script element R3_COPY_VARIANT  to set or keep the protected flags of copied variants.

 

SAP BW: New Variable for the Number of Automatic Restarts of Process Chains

In SAP jobs with BW chains, the agent now creates the script variable &@restart_count# for each childA subordinate task (such as a task that runs in a workflow). process. This script variable stores the number of automatic child process restarts that have been made. You can also use the variable &@sap_bw_max_restart_count#, which includes the maximum number of restarts. This variable and its value appear in the Detail Window of the tasks.

 

R3_MODIFY_VARIANT - New Parameter MERGE=

The new optional parameter MERGE= is now available in the SAP script element R3_MODIFY_VARIANT. Use this to determine whether non-defined variant parameters should be kept (YES) or reset to a blank value (NO). By default, this script element does not change non-defined fields (same behavior as in previous versions). When you specify MODE=APPEND, the parameter MERGE= is automatically always YES.

This parameter is available as of SAP Note 1702115.

 

R3_ACTIVATE_REPORT and R3_SET_PRINT_DEFAULTS: New Print Parameters

The following new optional print parameter are available in R3_ACTIVATE_REPORT and R3_SET_PRINT_DEFAULTS:

  • SUPPRESS_SHADING= Suppresses colors and shades.
  • WITH_STRUCTURE= Includes structured information.
  • DEFAULT_SPOOL_SIZE= Limits line width to 255 characters.
  • PRINTER_MAIL_ADDRESS= The address of an email printer.
  • SPOOL_PAGE_FROM= The page from which to start printing.
  • SPOOL_PAGE_TO= The page until which to print.

The UC4 Interface is no longer required for the following parameters:

  • TEXTONLY=
  • FRAMES=

Note that the above parameters can only be used with a specific SAP version or higher. SAP Note 1678864 provides further details about this.

 

BW_ACTIVATE_INFOPACKAGES: New Parameter LOG=

With this new optional parameter, you can print the log messages of InfoPackages to the job reportA report provides more detailed information about a task's execution or a component.. For compatibility reasons, the default setting for these messages is that they are not logged.

 

BW_GET_INFOPACKAGES: New Parameter JOB_STATUS=

The new optional parameter JOB_STATUS= can be used to select jobs that have been started by InfoPackages according to their status.

 

 

ApplicationInterface

ExecuteObject - New Method "putPromptBuffer"

The new method putPromptBuffer allows you to set PromptSet variables for the started object. For an example, see the related topic in the ApplicationInterface.

 

 


Improvements

General

Changed Deactivation Behavior

The following changes and improvements have been made:

  • Workflows that include active tasks cannot be deactivated. The same rule applies for the tasks of all sub-workflows.
  • Tasks that have been started by a workflow can only be deactivated by deactivating the top workflow (for which the above rule applies).

The deactivation process will fail if one of the above rules is not fulfilled.

The new command "Deactivate (forced)" is now available for finished workflows. When you apply the "Deactivate (forced)" command, the finished workflow will be deactivated even if the workflow or a sub-workflow below it contains active tasks.

The "Deactivate (forced)" command can only be applied on top level workflows.

The commands "Deactivate" and "Deactivate (forced)" always deactivate workflows including their subordinate tasks.

Time-delayed automatic deactivation is now specified in minutes (previously in days). Values in the database are converted automatically during update.

Tasks can now also be deactivated via script. The new script element DEACTIVATE_UC_OBJECT is available for this purpose.

 

Preventing Multiple Restarts

Tasks can only be restarted once their previous restart has finished. You cannot restart tasks while there is still an active restart instance.

 

Workflow tasks: Preconditions and the Value *OWN for Agents

Previously, an error occurred when the conditions of the Preconditions tab were being processed if:

  • the value *OWN was set in the condition for an agent (=using the task's agent),
  • the workflow task was generated at runtime, and
  • the task ran in an AgentGroup.

This has been changed; the condition no longer fails but uses the AgentGroup's first active agent.

 

Restarting Tasks with SYNC Object Conditions

The Sync object will no longer be checked in restarted tasks that include SYNC object conditions when no abend action has been defined in the Sync tab. The Sync object will be checked as usual when one or several abend actions were defined before the task was restarted.

 

Login object - Selecting the RA SolutionA solution that is based on the Rapid Automation Technology that allows the Automation Engine (AE) to access an external system / application / platform. The RA Solution is supplied as a JAR file that must be loaded into the AE Database and connected with an RA Agent. The specific RA objects (such as Jobs, Connections, Agent) are available in the AE system as soon as the solution has been loaded.

In Login objects, the column "Type" now lists the names of all loaded RA Solutions. The value "CIT" is no longer available.

In the loginAn Automation Engine object type that stores account credentials used by agents on target systems. entries of RA agents, you can now select the relevant RA Solution as the type.

Note that "CIT"-type login entries will not automatically be adjusted when you update your system.

 
Extended Functionality  
ACTIVATE_UC_OBJECT - To define a maximum runtime for the started object. The task will abort and/or a new task will start when the specified time is exceeded.  

SAP BW: Data for Chain Steps Published as Script Variables

In SAP jobs with BW chains, the agent creates several script variables for each child process. These variables and their values are available automatically in the (child) post process tab, and appear in the Detail Window of the tasks. For the list of variables and their values at the Chain, Step, and Step Job levels, see SAP BW: Data for Chain Steps Published as Script Variables.

Previous release included the E_TYPE_TEXT and E_VARIANT_TEXT script variables, which are now renamed to &@sap_bw_type_text and &@sap_bw_variant_text.

 

 

UserInterface

Activity Window: Grouping several restarts of the same task

For the sake of a clearer overview, all the restarts of a task will now be grouped together in the Activity Window. The last task restart represents the main node. When you expand this, you will see all the task's previous restart runs (provided that they have not yet been deactivated).

Task grouping is only available in the hierarchical view of the Activity Window.

 

SAP Forms: Script Element Names Now Displayed in Selection Menu

The Forms tabs of SAP jobs now additionally display the name of the SAP element (in brackets) in the selection menu.

 

SAP Forms: Check-Box and Radio-Button Parameters Remain Unchanged

Editing script elements via the Forms tab no longer affects check-box or radio-button parameters that were not changed. Previously, these parameters were automatically replaced by a valid default value when the Forms modifications were saved.

You can now set variables for all these parameters via script; these will be kept even when the modified Forms are saved.

 

SAP Forms: Defined Script Elements Numbered and Displayed in a User-Friendly Format

Defined script elements are now listed in numbered form in the left part of the SAP Forms tab according to their order in the script.
A short description of the function is now displayed instead of the name of the script element.
Example for R3_MODIFY_VARIANT: Protect variant "STANDARD".

 

Improved Order of Job Report Options

In previous versions, the Job Report options Generate on error only and Is generated by script (to be found on the platform-dependent tab of Job objects) appeared to be linked to the File option. This has been corrected to a more user-friendly order, as these settings affect the file as well as the database report.

 

Detail window: Links in Variable Values

You can now open links (texts starting with http://) provided within the values of listed object variables. When you click on the link, it will open in the default browser. This is the same procedure as for links that are provided in the Documentation tabs.

 

Agents

SAP

R3_ACTIVATE_REPORT: The print parameters TEXTONLY and FRAMES are now also available in the standard interface.

Script element R3_ACTIVATE_REPORT: The print parameters TEXTONLY and FRAMES are now also available in the XBP Interface (previously only in the UC4 Interface).

 

BW Process Chains: Last Start Time Available in Reports

The PLOG reports of SAP jobs include the start date and the start time of process chains and now also their last start time.

 

 

Documentation

WebHelp in new HTML5 format

The WebHelp is now based on HTML5 and has a new, improved AE-style design and a user-friendly interface.

The left WebHelp area now shows the content tree and a Glossary area, which includes all the glossary terms as well as their definitions. The search field is now provided in the header line (previously in the left area).

 

Documentation as PDFs

You can now choose between Automation Engine documentation in HtmlHelp format, in WebHelp format, and as PDFs. Note that as of now, the PDFs provided in the Automic Download Center will always be up-to-date.

The supplied documentation folders are "htmlhelp", "webhelp", and "pdf".

 

Bug Fixes

 

For an up-to-date list of bug fixes and known issues for a product version, go to the Automic Download Center. Click Advanced Mode, then select the applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity. and version, and check Bug Fixes.

 


Known Issues

 

For an up-to-date list of bug fixes and known issues for a product version, go to the Automic Download Center. Click Advanced Mode, then select the application and version, and check Known Issues.

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH