Version 2020.1 patches

This section details the fixes and enhancements in patch releases for Axiom Software version 2020.1. For assistance with any patch, you can contact Support using Syntellis Central.

Axiom Software patches are cumulative. All fixes and enhancements included in prior patches are included in the current patch.

IMPORTANT: This is not the most recent major version of Axiom. Contact Axiom Support to upgrade to the current version.

Current patch: 2020.1.35

No platform-specific changes were made in this patch. See the separate product release notes for information on any product-specific changes.

Patch 2020.1.34

This patch contains updates to the data query engine.

Patch 2020.1.32 - 2020.1.33

No platform-specific changes were made in this patch. See the separate product release notes for information on any product-specific changes.

Patch 2020.1.31

This patch contains updates to internal tools. No client-facing changes are included in this patch.

Patch 2020.1.30

This patch contains back-end changes intended to improve performance for cloud systems.

Patch 2020.1.29

This patch contains back-end changes intended to improve performance for cloud systems.

Patch 2020.1.27 - 2020.1.28

No platform-specific changes were made in this patch. See the separate product release notes for information on any product-specific changes.

Patch 2020.1.26

The following issues were fixed in this patch:

  • 56651: Launching the Desktop Client may get stuck at the "Validating access rights" step.

Patch 2020.1.25

This patch contains some system configuration enhancements intended to improve performance when refreshing data for an Axiom Intelligence Reporting model.

Patch 2020.1.24

The following issues were fixed in this patch:

  • 51934: An ambiguous column error may occur when running an Axiom query with a configuration that includes column filters and a table with multiple lookups to the same reference table.
  • 54962: Newly created Axiom Intelligence reports cannot be saved.
  • 55263: Performance may be slow for certain Axiom queries that use column filters.

Patch 2020.1.23

The following issues were fixed in this patch:

  • 53446: Executing Save Type 3 causes table caches to be unnecessarily invalidated.
  • 53471: An error may occur when running an Axiom query if the query references a calculated field in the filter and the calculated field consists of more than 400 columns.

Patch 2020.1.22

The following issues were fixed in this patch:

  • 52141: When an import generates an error file, the file is blank and may also cause an error when attempting to open it.
  • 52391: If a calculation in a Data Grid component references a column that has no matching data, the calculation returns zero instead of the expected results.
  • 52406: If a calculated field is used in the data filter of a Fixed Report component, an error occurs attempting to fetch the data.

Patch 2020.1.21

No platform-specific changes were made in this patch. See the separate product release notes for information on any product-specific changes.

Patch 2020.1.20

The following issues were fixed in this patch:

  • 51346: A "method not found" error may occur when running a 2019.x product version in platform version 2020.1.

Patch 2020.1.19

No platform-specific changes were made in this patch. See the separate product release notes for information on any product-specific changes.

Patch 2020.1.18

The following issues were fixed in this patch:

  • 42252: If a sheet name in the File Processing settings is configured to only use a token—such as [Current_Value]—the configuration is erroneously flagged as invalid.
  • 49890: If a calculated field is listed in both the data filter and the field definition of an Axiom query, an "ambiguous column" error occurs.
  • 50720: Exporting a very large formatted grid from an Axiom form to Excel takes much longer in versions 2019.4 and up.

Patch 2020.1.17

The following issues were fixed in this patch:

  • 50072: If a grouping is specified for a file group, the plan files do not display as grouped in dialogs such as Open Plan Files.
  • 50102: If a preferred name for a column matches a database reserved name, an "incorrect syntax" error occurs when running an import that includes the column.

Patch 2020.1.16

The following enhancements were included in this patch:

  • Import behavior was enhanced so that when importing data into a partitioned table, the import only reads the partitions affected by the import. This change is intended to improve import performance for partitioned tables.

The following issues were fixed in this patch:

  • 49615: Data Grid components may fail to render with an "invalid filter" error if the Data Filter on the grid references a process column.
  • 49616: Axiom queries using a post-query filter may fail with an "invalid column" error if the filter references a column that is not on the primary table.

Patch 2020.1.15

The following enhancements were included in this patch:

  • The Copy Plan File Settings are now also available on edit steps of plan file processes, if the system configuration setting ShowCopyPlanFilesActionInProcess is enabled. Previously, the copy options were only available on approval steps.

    Copy plan file action now available for edit steps

  • A new option, Treat as Copy Plan File Target Process, is now available on the Advanced Properties tab of plan file processes, if the system configuration setting ShowCopyPlanFilesActionInProcess is enabled. This option can be enabled on the plan file process of the target file group for a copy plan files action, so that copied plan files are automatically started in the process. For more information, see Copying plan files when a process step is completed.

    New option to treat process as the target for a copy plan files action

  • A new option to specify a grouping column is now available on edit steps and approval steps of a plan file process. If a grouping column is specified, then the tasks for that step display in expandable/collapsible groupings using the values in that column. For example, if the grouping column is Dept.Region, then tasks display grouped by regions such as US West, US East, and so on. This option is intended to be used for steps where users may have many active tasks at one time, so that the groupings can help the step owners identify and complete their tasks.

    New option to show tasks for a step in groupings

    This option only affects the display of tasks in the Process task pane of the Desktop Client (or in any custom task pane using the User Process View command).

    Tasks shown in groups within Process task pane

  • The Delete Rows transform for imports now uses truncate to delete rows when possible.

The following issues were fixed in this patch:

  • 49526: For certain data structures and report configurations, an ambiguous column error may occur when refreshing an Axiom query.

Patch 2020.1.14

The following enhancements were included in this patch:

  • You can now schedule plan file processing for file group scenarios. When configuring a Process Plan Files task in Scheduler, you can use the new Show Scenarios option in the Choose File Group dialog to select a file group scenario for processing.

The following issues were fixed in this patch:

  • 49038: When using a HierarchyFilter refresh variable in the Web Client, an inaccurate filter may be created if a hierarchy node has many items and more than 10 of them are selected for the filter.

This patch also contains security updates.

Patch 2020.1.13

The following issues were fixed in this patch:

  • 48476: In some cases, deadlock errors may occur when performing file group cloning.

Patch 2020.1.12

The following issues were fixed in this patch:

  • 48404: Reports with many column filters may have slow performance.
  • 48532: If a calculated column in a Data Grid or Fixed Report component references another calculated column, the calculation with the reference is omitted from total rows.

Patch 2020.1.11

The following issues were fixed in this patch:

  • 48167: The Desktop Client does not route traffic to the proxy when configured to do so via the Software Manager, resulting in a failure to launch.