Sustainable Enterprise Reporting And Management

Release Notes

  

Release Notes for "Banker" (Build 2573)

Improvement 94178: Drag and drop editing of report blocks

In the report definition editor, blocks can now be dragged and dropped for moving or copying (with CTRL key).

Feature 52320: Implement report builder

A new module "Reports" has been added to SERAM, and the ability to define and execute reports added.

The report definitions are a hierarchy of nested blocks which are used to define the report output. There are basically two categories of blocks: control flow and content.

The control flow blocks implement loops as well as ordering. All blocks also have optional conditions which control when these are to be processed.

Content blocks render content into the output Word document. The blocks support outputting document sections, headers and footers, table of contents, rich text with placeholders and footnote support, tables, native Office charts (even mixed), breaks etc.

Definitions can have typed variables which are presented to the user with a UI when running the report. These variables can, for instance, query structures, indicators, times or plain text to be used in the report.

Reports are rendered in the background, and are stored for download.

Feature 96559: Allow users to create new structures from within the Dashboard

By granting the Structures:CreateChildNode function, users without access to the (administrative) Structures module can be enabled to add new child structures from the Dashboard (pending Data Entry) or the Data Entry module.

When users create structures like this they are automatically presented with the Data Entry for the new structure node.

Feature 96588: Allow exporting any DataGrid component content to Excel

Any data table can now be exported to Excel by using the "xlsx" link (close to the Filter).

Feature 96969: Implement importable Period Structure Indicator Excel report

A invariant version of the Period Structure Indicator can now be downloaded by pressing the SHIFT key when clicking the link. This report contains all language versions and some other columns as the default version of the report and is suited for verification purposes.

Feature 96975: Early display formula editor syntax problems in expressions, predicates, queries and XML

When editing expression, predicate, query formulas or XML code, the syntax is checked at apply time and problems are reported right away including position information.

Feature 98214: Allow setting permissions for children only (InheritedButNotSelf)

Permissions can now be granted to "Children only" (InheritedButNotSelf) in addition to the "This object" (Self) and "This object and children" (Inherited) permission levels.

Also the permissions dialog has been adjusted to allow for more granular setting of permissions by subject and object.

Bug 95038: Initial load of the application with Windows Integrated Authentication may not receive all client settings from the server

The endpoint for the settings accepts unauthenticated requests where only a subset of settings is returned to the client in order to avoid information disclosure.

Some browsers would, however, not send Kerberos authentication information on the first call to the service even when the user was authenticated before, thus an incomplete set of client settings would be received. This has been fixed by passing a parameter to the setting service whether the call comes from an authenticated source or not.


Release Notes for "Baluchi" (Build 2176)

Improvement 88896: Include factor indicators in completeness computation

Factors did not provide a completeness value, therefore a value could be shown as complete despite missing a factor in a calculation. For better consistency the factor indicators now also provide completeness information.

Improvement 89913: Show previous value of boolean indicators as Y/N in Data Entry

The previous value is always a number and a comment, however in order to make the appearance more user-friendly it is now displayed as "Yes" or "No" in Data Entry for any indicator which is a boolean value.

Feature 88019: Show previous year comment as tooltip in Data Entry

The Previous Value in Data Entry now shows not only the numeric value, but also the previous comment as tooltip.

Feature 88024: Display Previous Value information for Factor Indicators

The previous value and comment is now also shown on Factor Indicators in Data Entry.

Feature 88078: Provide full-page editor for Text Values

A full-page, Markdown-enabled (with preview) edit field can now be invoked for Text indicator values. This allows for better editing of longer texts with formatting as Text indicator values.

This editor is invoked by double-clicking the Text indicator input field.

Feature 88129: Allow creation of links for unauthenticated Data Entry

Users with the tenant-wide DataEntry:ManageShare right can now create links to Data Entry forms in order to share the form via link which does not need authentication.

Note: Links should only be shared with trustworthy entities. While the anonymous access is highly restricted to the parts of the application used for Data Entry, the link still provide much insight into the tenant configuration and may also allow more data manipulations than anticipated since the normal permissions checks apply.

Best practice is to still create a dedicated user account (which may be claim-less) with the exact required permissions and to impersonate this account when creating the anonymous Data Entry link.

Feature 88805: Include parent structure name in Input Values Excel export

When creating an Input Values Excel export, an additional column with the structure parent name has been added.

Feature 88895: Add additional value-related functions to formulas

New functions have been added for formulas:

  • statusOnly("code") strips the value down to keep only the status, or null if there is no indicator status in the given value. This function can be useful in calculations for including indicator references which should not contribute to the end result in other ways than by their status.

  • ignore("code") ignores the referenced value completely, also to be used in calculations.

  • statusOf("code") returns the invariant name of the data status.

  • idOf("code") returns the persistent value ID. Note that consolidated, aggregated, computed and flowed values do not have a persistent ID.

  • isEditableStatus("code") returns true if the data status is editable (typically the "open" data status). This is independent from editability of the value.

Feature 88912: Support notion of absolute and relative object IDs in formulas

When saving formulas, relative and absolute period indexes for named objects have always been supported (e.g. "X" which is equivalent to "X"(+0), "X"(+1) which is X in the next period, "X"(-1) which is X in the previous period, and "X"(2018) which is X in the period 2018).

The information whether an absolute or relative index had been used was however not persisted in the internal formula representation which uses the object ID, so that the indicator references would always be interpreted as being relative, causing confusion when editing formulas, or when copying a period to another year.

The formula conversion between named and ID and the internal ID representation has now been extended to keep this information intact.

Feature 88920: Allow to insert commonly used text snippets in names, descriptions and other select fields

Snippets can now be configured (by default ["CO₂", "²", "³", "∑"]) for commonly used text fields.

Feature 89564: Add "Compute on specific Frequency" functionality for calculations

Analogue to the "Compute on specific Level" functionality, but regarding the time-consolidation. This performs the calculation on a specific time frequency (for instance on the month) and sums the result up on the parent frequencies (in this example quarters and year), instead of performing the calculation with the values on each time index independently.

This makes it possible to compute time-dependent multiplications, such as ton-kilometers based on tons shipped and kilometers driven.

Feature 90008: Provide completeness information for values in Data Analysis charts

Charts now include information about value completeness in their tooltip, and they apply transparency in order to make the completeness visually apparent. Also, the line charts show incomplete values with a Diamond bullet instead of a Disc.


Release Notes for "Balikun" (Build 2073)

Feature 83232: Allow to restrict the times selection in Data Grid to Yearly only

A new setting DataAnalysis:onlyYearlyTimes (boolean, default false) can be used to control the appearance of the time selection process. When enabed, the time selection in the Data Grid only allows to select yearly values, regardless of the effective time indices.

Feature 83236: Provide column with default value in Input Value Export

The Input Values Excel export now includes a default value column. Numeric defaults are show directly in the cell, and formula-based default values are shown as comment of the cell.

Feature 83501: Provide Query generator in Data Grid module

Users who have application access can have the system generate a query from the currently loaded Data Grid. This is a convenience feature to removes the need to manually write the query.

Feature 83677: Allow optional read-only access to Data Entry

A new setting DataEntry:allowReadOnlyAccess (boolean) controls whether users need SetValue or GetValue functions to access Data Entry. Default is false (SetValue).

Feature 83740: Add Data Quality to value tooltip in Data Grid

The tool-tip on the Data Grid cells now include information about the data quality of the value (if available).

Feature 83754: Display values of non-persistent indicators in bold font in Data Grid

A new setting DataAnalysis:boldNonPersistentValueCells allows to control whether computed values are shown in bold font in the Data Grid

Feature 83840: Display all persistent values with a pen, gray when not editable

This allows the user to distinguish between values of an indicator which were entered directly and values which were somehow computed (e.g. time or organization consolidation), even if these values are read-only for some reason.

Feature 87857: Full structure scenario support

It is now possible to create "structure scenarios". Each scenario represents a set of structures (the default scenario contains all structures). In Data Grid, the scenario to be computed can then be selected in the Reference Environment and it can also be saved in saved selections.

This functionality allows to create different views on data. For instance, a company may create additional scenarios for production and for offices. Or, when a part of the company is sold off, the sold parts can be excluded in a scenario which would allow to analyze historical data with or without the sold off parts.

The new functionality is a more universal version of the already-existing but much more limited "Run as Scenario" functionality of the Data Grid.

Bug 83730: The OpenID provider does not accept e-mails from TLDs longer than 4 characters

When using SERAM OpenID for authentication, e-mails with TLDs longer than 4 characters are now accepted.

Bug 83763: Empty first column group leads to wrong positioned column group heading in Data Grid

In Data Grid, when the first horizontal group is hidden because it contains no values, the position of the group heading is now computed correctly.

Bug 83789: The scroll position in the Data Grid is not reset when using the Reset button

After loading a Data Grid and scrolling, the old position was retained even after resetting. Due to this, in very specific circumstances, the user would only see the "checkerboard" pattern until scrolling or changing the axes configuration.

Bug 86055: Show an error when no data is imported from an Excel workbook

When an Excel import does not fail (no error) but no data is found, an informative message is now displayed to the user instead of confirming a "successful" import.


Release Notes for "Baise" (Build 2039)

Improvement 63453: Record value and status changes in Audit Log

In addition to the Value History, changes to the value and status can now also be recorded in the Audit Log.

Improvement 71002: Fix SetValue/SetComment function behavior

Users with the SetValue function were always allowed to change the comment, even when the value was not in the editable state. Now users explicitly require the SetComment function to change the comment of values in a non-open state.

Improvement 81787: Add default filter to Excel exports

Tabular Excel Exports now automatically set the Filter on the heading row. Also the report style has been unified in general.

Improvement 81788: Add a function to select units of the same quantity

Whenever multiple units can be selected (e.g. as Input Unit), allow to select all units of the same quantity (e.g. all weight units etc.).

Feature 47333: Export Access Control List to Excel

The Tenant Users Excel export was extended to include the following information:

  • active global users who have access control entries in the tenant
  • access control entries of active users
  • role function information

Feature 80679: Comment support for Choice Indicator

Choice Indicators now also offer a comment field.

Feature 80708: Include last audit date in Users Excel Export

The Tenant Users Excel export now includes a column specifying the last audit date of a user.

In combination with Value Change Auditing this can be used to track when a user has been actively working in the system.

Feature 80914: Allow rendering value text based on calculation result

Calculations can now optionally define a "Display Formula" which is used to convert the calculation result to a textual value.

Feature 80915: Add sign() function to formula language

Formulas can now get the sign of a number with the sign() function.

Feature 81785: Detect diverging server application version and inform the user to refresh

The application is now able to detect changes of the server-side application code. When a change is detected, the user is requested to reload the application.

Feature 81786: Allow skipping the tag selection step in the Data Entry wizard

The selection of Indicator Tags in the Data Entry wiuard can now be disabled in configuration, so that all available tags are used instead.

Configuration setting: DataEntry:skipTagSelectionStep (boolean)

Bug 81023: Potential error in ModuleDataAnalysis.refresh() when grid is still being loaded

In come cases, returning the ther Data Grid after a drill-down etc. would show an error message.


Release Notes for "Azteca" (Build 2024)

Improvement 56189: When removing the mandatory setting of a period indicator, set all its period structure assignments to active

When removing the "mandatory" flag from a Period Indicator, all structures which were active at that time will keep the assignment set to active.

Previously they would revert to the state they had before setting them to mandatory, which would potentially disable assignments and thsus remove entered data.

Improvement 80330: In Period Indicator Excel report, make Level column contain Calculation Level as well

The Period Indicator Excel export contains a column for the Persistence Level. Since this is mutually exclusive with the Calculation Level, that information is now also included the same column for Calculation Indicators.

Feature 43901: Data Display in Data Grid - relevant /active only

The Data Grid will by default only show columns and rows which also contain some data. When manually configuring axes, the behavior can be controlled by the user.

This removes "noise" from the Data Grid and is especially useful when used in conjunction with Saved Selections.

Bug 56353: Also respect the structure date for available input indices in Reporting Indicators

The structure creation/deletion date is now also taken into account for reporting indicator with a higher input than reporting frequency.

Previously all inputs were offered regardless of the start/end date, so if a site existed from march to june, it would still get 12 month fields for a yearly reporting indicator set to monthly input.

Bug 58009: Undoing creation of a structure which is used as link returns SQL error message

Added human-readable message for this error condition.

Bug 73980: Changing only trailing whitespace of a claim deletes the claim

Claim values are now trimmed from leading and trailing whitespace.


Release Notes for "Azerbaijan" (Build 2007)

Improvement 52440: Remember vertical scroll position in view stack and restore on pop

When switching views (e.g. going back in the breadcrumbs), SERAM will restore the scroll position and UI element focus in order to improve overall usability.

Improvement 61392: Data Grid: Double-clicking a value cell without ValueID should perform a drill-down instead of opening the edit view

When double-clicking a cell, a drill-down is now performed for computed values instead of opening the value detail view.

Improvement 62987: Convert CoffeeScript code to TypeScript

The client-side code was ported from CoffeeScript to TypeScript 2 in order to future-proof the client-side codebase.

Improvement 75745: Extend filtering of selectable structures for Data Grid to structures with Indicators:GetValue function

The Data Grid Structure selection now only shows structures to which the user also has the GetValue function, since he can only retrieve and see data on these structures.

Feature 42403: Add indenting to formula writer when writing named formula

Formulas are now automatically nicely formatted and indented (e.g. on if..then, choose... etc.) for display and editing purposes.

Feature 43961: Use CodeMirror as formula editor

The formula editor has been upgraded with syntax coloring, code completion (CTRL-SPACE to trigger), automatic indenting etc. to make the formula editing easier.

Feature 52319: Make UI translatable

The UI now supports multiple languages. Currently, the UI is available in English (which is also the fallback for missing languages) and German.

Feature 61391: Data Grid: Double-clicking a saved selection should trigger the "Use selection ..." action

The Saved Selections in the Data Grid can now be loaded by double-click.

Feature 75744: Introduce separate function Indicators:GetValue which can be used to control access to values of an indicator

A new role function Indicators:GetValue has been introduced, which controls access to indicator values separately from access to metadata.

Feature 75797: Add list of tags to Period Indicator Excel export

A column listing the tags of each indicator has been added to the Period Indicator Excel export.

Bug 61568: Breadcrumbs do not work in IE

The breadcrumb navigation can now also be used in IE.


Release Notes for "Auxois" (Build 1882)

Improvement 70661: Display more information when a formula contains errors

Whenever a formula failed to parse, only a very short error message with the error kind and location was shown (e.g. SyntaxError at line 4 column 5 (index 72)), which left it to the user to count and find the error location.

Now SERAM displays an excerpt of the formula text with up to 40 characters and displays the exact error location in this excerpt as triangle with an exclamation mark. Also, whenever a syntax error is encountered, SERAM lists the expected tokens at the error location.

Feature 70654: Add support for custom indicator conversions

Period Indicators can now not only use the built-in unit and factor conversions, but also formula-based custom conversions. These are performed on the input values whenever these are converted to reporting values.

The formula can reference other indicators with the normal quote notation, as well as the inputValue (number), previousInputValue (number), inputIndex (number), inputUnit (string) and reportingUnit (string).

To leverage the existing unit conversion facility, a new function convert(value, sourceUnit, targetUnit) has been added. Another new function unitOf(indicatorReference) can be used to retrieve the reporting unit (as string) of any indicator reference.

Feature 70671: Add support for "None" time consolidation

A new time aggregation "None" has been added, which can be used on Reporting or Choice Indicators that are not meant to be consolidated over time.

When this time aggregation is used on a Reporting Indicator, the Input Frequency will be fixed to be identical with the indicator's Reporting Frequency.

Feature 70679: Allow to use built-in unit conversions in formulas

Calculation formulas can now perform unit conversions using unit conversion facility of SERAM.

A new function convert(indicatorReference, targetUnit) allows to directly convert indicator values to a specific unit. When no indicator reference is available but just a numeric value, the function convert(value, sourceUnit, targetUnit) can be used to convert between units.

In order to avoid divergence of the target unit in the formula and the unit configured in the calculation, it is now possible to get the unit configured in the calculation through the property calculationUnit in the formula. This property can be used in place of a literal unit when using the convert function.

Feature 70820: When successive values (on time axis) are present, display their difference as tooltip in Data Grid

In the Data Grid, when the previous time index and/or previous period value have been loaded along with a given value, the system will now automatically compute the delta (difference) as absolute number and as percentage and show this information in the tooltip of the value when hovering over the input field.

Feature 70892: Add security function to control "value analytics" functionality in Data Grid

A new application function has been added which allows to hide some functionality of the Data Grid. The function is called DataAnalysis:ValueAnalytics.

The new function controls the following functionality of the Data Grid:

  • Value interpolation in value cell tooltips
  • Value delta to previous value/period in value cell tooltips
  • Availability of the action "Drill-Down into this Indicator Value"
  • Availability of the action "Find Restated Values"

This function is only effective for tenant-wide permissions. For compatibility reasons, upon deployment of this release, a new role "Allow Value Analytics" is created and granted to "Authenticated Users" tenant-wide.

In order to leverage the new functionality, administrators therefore need to revoke this permission and grant the role to specific users or groups instead.

For compatibility reasons, the "Drill-Down" action can be explicitly allowed even when a user does not have the Value Analytics function by setting the setting DataAnalysis:alwaysAllowDrilldown to true.

Feature 71001: Add file attachment data dimension to Boolean, Choice, Factor and Text indicator types

The ability to allow File Attachments has been extended from Reporting Indicators only to all persistent indicator types.

Feature 71599: Replace Owner Structure with period-specific Structure Scope

The existing "Indicator Owner Structure" (on the indicator metadata) has been replaced with the "Indicator Scope Structure" (on the activated indicator).

With this change it is now possible to change not only the persistence level of indicators in new reporting periods, but also the scope. This can for instance be used to introduce a completely new organization structure starting in a certain reporting period while keeping the existing indicators; by using links between the old and the new structures and the data flow functionality, SERAM can make values of old reporting periods available with the new structure without actually touching the historical data.

Feature 72022: Add support for "is NaN" and "is not NaN" in formulas

Formulas can now explicitly check the presence or numeric values through is NaN or is not NaN.

Depending on the context this yields different results from is null and is not null, for instance when used against indicator references "Some Indicator" which may have a value with a data status etc. but no numeric value.

Feature 74127: Compute cells with formulas in the Excel Input Values import

When importing values using an Excel sheet, the cells may now also contain formulas which are then computed.


Release Notes for "Asturcón" (Build 1749)

Improvement 61405: Allow configuration-based style customization of charts

The style and behavior of charts can now be customized through tenant settings.

The JSON object specified in the settings Style:barChartCustomization, Style:lineChartCustomization and Style:pieChartCustomization is merged into the configuration object which is used to create the charts.

Documentation from Charts supplier (also provides demos):

Feature 61056: Add metadata to Indicator Tag to define whether to include/exclude it in the Data Grid Reference Environment

It is now possible to control which Indicator Tags are included by default in the Reference Environment of the Data Grid, so that irrelevant (but accessible) indicators can be hidden from the Indicator selection visible to users by default.

Feature 61362: Add tooltip with additional information (e.g. indicator metadata) for heading cells in Data Grid

The heading cells in Data Grid now show a tooltip with extended information, e.g. the full name (as it may be truncated in the heading cell) and the description (for indicators), the comments (for structures) or the date range (for time indices).

Feature 61597: Add support for unit metadata (allowing translation of names)

Unit names and descriptions can now be translated.

In order to enable this it is now also possible to edit the name and description of standard units (SI) which were completely read-only before.

Feature 63030: Extend Choice Indicator to make the constraint optional (can be left empty)

Choice Indicators can now be configured to allow a data status change with no value set (that is, without the "Must have a value" constraint).

However, when an invalid value (which does not match any of the choices) is in the indicator, the choice will still show a failed constraint.

Feature 63475: Allow custom color for forecasted values in Data Grid

Forecasted values are now shown with a different text color in the Data Grid, so that they become more apparent.

The default color is a very dark red, but this can be controlled by setting the Value:forecastedColor setting to a different HTML color.

Feature 63520: Add generic indicator information (including Sort Key) to period indicator admin trees

When managing indicators, more details are shown in the actions pane when a indicator is selected in order to facilitate management. Also, the "Show Details" view now includes more information as well.

Feature 64797: Return all applicable permission entries of a user, not just the ones explicit to the primary subject ID

When the permissions of a user are viewed, SERAM now shows not only the permissions explicitly assigned to the user, but also all permission entries which apply to the user through implicit and explicit group membership.

This makes it easier to understand and verify what permissions apply to a user, especially when the user is a member of some groups.

Feature 65896: Allow generic CSS customizations via settings

A new setting Style:customCSS has been introduced which allows specific customization on the CSS level.

Note that these customizations may be broken on updates of SERAM, if the layout and/or style sheet of SERAM is changed. This is in the nature of this low-level setting and any configuration applied here is unsupported by Sirius.

Feature 66005: Allow disabling the empty constraint for Boolean values

Boolean Indicators can now be configured to allow a data status change with no value set (that is, without the "must have a value" constraint).

Feature 66296: Show red background in Data Grid cells when the value is erroneous (plausibility or constraint error)

Whenever a value fails the constraint check or when it is marked as being not plausible, its text field is now shown with a light red background in the Data Grid, so that erroneous values can be identified easily in the Data Grid without having to open the edit view.

The Excel Data Grid however does not contain this visual clue, since the background color already represents the status, and the font color represents the forecast status.

Feature 66347: Extend formula processor to handle non-numeric data of indicators (e.g. text)

Until now, indicator references ("Indicator") in formulas did only support the retrieval of the numeric value of an indicator.

Now more information can be retrieved, such as text from text indicators, and additional functions have been added to support this. This allows to implement more specific calculations, constraints, plausibility checks and default values.

Feature 66561: Allow per-indicator control of Data Quality and Forecasted

The Data Quality and Forecasted data dimensions can now be enabled/disabled per indicator, not just on the tenant level.

The toggle is only available when the respective data dimension has also been enabled through the tenant settings, so that Data Quality and/or Forecasted can still be fully disabled for a tenant.

Feature 67643: When a default formula does not return a value, don't mark the value as forecasted

When default values are defined with a formula, they may return a NULL (empty) value.

Until now, if the "Default is forecasted" was checked, these empty values would have a forced forecasted flag. However, since the default did not actually fill in a value this was a source of confusion for the user.

The new behavior is to only force the forecasted flag whenever a default values was really filled in, that is, it was not NULL.

Feature 70362: Add indicator assignment editable selection and active filter actions

When editing Indicator Assignments (both through View Activated Indicators or Structure Management), it is now possible to filter the assignments list to their active status, and to make selections based on the UI-editable status.

Feature 38338: File attachment data dimension for Reporting Indicator values

It is now possible to enable File Attachments on Reporting Indicators. When this is enabled, users can attach any number of files to values.

Attachments are managed like other value data, therefore they are also kept in the value history even after a restatement.

A new action has been added in the Data Grid for finding attachments related to a specific computed value. It performs a deep drill-down which finds all values with attachments that were part of the specified computed value.

Bug 66887: The relative() function does not work for reporting indicator default formulas when reporting frequency is not yearly

The support for the relative() function in reporting indicator default formulas has been extended:

  • It may now be used in default formulas with a number smaller than the reporting frequency (relaxed self-reference check)
  • Recursion during value computation is now properly detected and either reported as exception or handled as volatile null value (controlled by setting Indicators:recursionReturnsNull)


Release Notes for "Appaloosa" (Build 1584)

Improvement 60905: Include Completeness in Choice indicator values

Choice Indicators now also report a completeness value, so that computed values using Choice Indicators have a more accurate view on the completeness.

Improvement 61063: Requesting Period Indicators with a limited rights user takes much longer than with an admin

The resolution of indicators when user were not allowed to see all indicators (for instance calculations referenceing disallowed indicators) would take much longer than with full rights. This has been corrected.

Feature 56343: Respect the exact creation and deletion dates of structures in indicator value operations

In SERAM, a site was either existant or not for full reporting periods. The relevant date for determining the structures was always the end of the reporting period.

With this feature, sites are now seen as existant if the period timespan overlaps the structure existance timespan.

Therefore, if a site is created in February and deleted in October, it will not have values for January, November and December, but it will remain accessible for the period and it does have values for all quarters and the year.

At the same time, the computation rules for breaking down summed values (e.g. monthly values for a value entered on the year) now repsects the actual number of days the site existed. Therefore, if a site was created in the middle of a month, the breakdown value will be about hald of full months as well.

The new behavior is respected in Data Grid, Data Entry as well as in the Data Controlling parts of the dashboard.

Feature 56728: Make the structure filtering optional

A tenant-level setting has been added to control the way the access checks on structures are performed.

Until now, in order to get effective access on a structure, users needed both access to the structure itself but also on all linked structures. In consequence, users can change the reference environment and access data on the linked structures (such as country).

This behavior can now be disabled, so that only the permissions on the structure itself are relevant. Management becomes simpler because adding new structure types does not affect filtering, and users do not need to be granted access to nodes such as countries, providing more data visibility control.

Feature 60161: Create API REST endpoint to retrieve entities and values

A new REST endpoint has been added to query arbitrary data. The endpoint is called via GET or POST with a single parameter q which contains the query in the SERAM Query Language.

The currently supported queries are for indicator values and structures. A complete description of the API is documented in the "Applications" section of the SERAM user manual.

Feature 61052: Allow negative start month for reporting periods

Negative time indices can now be specified for the Reporting Period start month, so that periods starting early (such as October in the hydrologic year).

Bug 61017: When updating a period indicator, circular references can be inserted which causes stack overflows on evaluation

When updating a Period Indicator, the formula is now analyzed for circular references, so that these are cought early on and don't cause the application to error out.


Release Notes for "Andravida" (Build 1541)

Improvement 53051: Add Time Span info to Value History

The History View now displays the full description of the indicator value (e.g. indicator, structure, time) instead of the indicator name only.

Improvement 53253: Add support for XLSX Excel file format

For Excel export and import, the XLSX file format (Excel version 2007 and newer) can now be used.

The default is currently XLSX (version 2007), but this can be configured through the ExcelVersion tenant setting (valid values: Version97to2003, Version2007 or Version2010).

Also, all Excel reports have been unified to use the same layout and file name scheme.

Improvement 53401: In Data Grid, enhance axis auto-selection to "summarize" single entries in the top

When auto-selection of axes is enabled and there is one dimension with a single entry (e.g. one structure), it is not put in the top horizontal row so that it doesn't repeat itself over and over again.

Feature 43740: Provide direct selection actions in the Data Grid axis selections

When making selections in the three axes of the Data Grid, actions now provide direct access as follows:

  • For indicators, all indicator tags (which are accessible by the user and used by at least one indicator in the indicator tree) can directly be checked.
  • For structures, they now also list their level and when a structure is selected, all nodes of one of the descendant levels can be directly checked (the ancestor node is then unchecked).
  • For times, when a time is selected, all time spans of one of the higher frequencies can be directly checked (the ancestor node is then unchecked).

Feature 44246: Automatically fix the order of structure types on the DB level

When setting or changing the order of structure types, the order of all other types is automatically adjusted to assure a stable order. This makes it much easier to adjust the order of the structure types.

Feature 44354: Filter out shared selections which the user cannot load due to permissions

In the Data Grid Saved Selection list, only selections are displayed which are either owned by or relevant to the logged on user.

This feature allows creating and sharing more selections without confusing users for which these selections are unsuitable.

The algorithm is as follows:

  • If the user owns the selection always display it.
  • Otherwise, pre-selected Structures and Indicators as well as Indicator Tags and the Root Structure (both as selected in Reference Environment) are checked for access rights.
  • If nothing is defined for one of the checks, the check assumes a pass (e.g. wildcard).
  • All four checks must pass to make the shared selection available to the user.

Feature 44745: Find restated values

When a Data Grid is loaded, it is now possible to find and analyze restated values (e.g. values which have been re-set to the editable state).

Feature 45317: Create an action to sort by key when editing groups

When editing an Indicator Group, the sort can now automatically be applied to the general order (as defined by the Sort Key and/or the Code).

Feature 47045: Input Values Excel export/import

The input values displayed in the Data Grid can now be exported to an Excel file (previously only XML was supported).

The Excel file is flat and ordered by period, structure, indicator and time index. Special care is taken to handle the input frequency of values correctly even if it is different from the reporting frequency.

Modifications to the Excel file can be round-tripped (imported), if the corresponding values are still open and editable.

Feature 52438: Add action to manage global users from within Tenant Users module

For users who have the global ManageUser permission, a new action is shown in Tenant User Management to switch to Global User Management.

Feature 52616: Hide the Reference Environment in Data Grid to avoid novice users from getting confused

Some "advanced" action categories are now collapsed by default, so that users are less overwhelmed by the number of actions available.

Also, a visual clue now indicates the expand/collapse functionality.

Feature 52654: Allow to view active/inactive status of users in Tenant User management

The Tenant Users now has an active flag on the users, which shows whether a user is active in the system or not. This information is also available to users who do not have access to Global Users.

Feature 52694: Display a constraint error when a factor is missing

When factor indicators are used for converting reporting values, problems now cause a meaningful message to appear in place of the check constraint error.

Feature 52702: Make tree "Select All" etc. actions in the right-hand pane

The Tree Views in the application now use the action pane instead of buttons (except for search field). This allows to use the actions even when scrolling and also provides more different actions, including "select all" and "deselect all".

Feature 52918: Add option in Reference Environment to compute scenario using only data from selected structures

The user can now perform a partial data analysis by using the "scenario" option in the Reference Environment.

In the scenario mode, some grid actions are no longer available because they can only work on the original structure layout:

  • Value drill-down
  • Find restatements

By default, loading a saved selection always resets the scenario option, unless the selection has explicitly been saved with the scenario enabled.

Feature 53176: Provide value completeness tooltip

In the Data Grid, incomplete values (italic font) now display a on-hover tooltip with completeness information.

The tooltip contains the following information:

  • Completeness in percent
  • Time aggregation (when applicable, e.g. for persistent indicators)
  • Linear interpolation (when applicable, e.g. for reporting indicators with "sum" time aggregation)

Feature 53190: Display version (line) chart when viewing the history of an indicator

The value history now displays the changes (timeline) as chart, the chart dots represent the values entered.

Feature 53329: In Data Entry, display effective time span description instead of "Previous Value"

In Data Entry, the previous value column is now labeled with the time span name.

Feature 53338: Detect and handle duplicate application mappings for structures, indicators and statuses

When using the SetValues REST endpoint, configuration errors are logged with more detail in the audit log to allow for better resolution.

Feature 53459: In the Excel Data Grid, export the text of multiple-choice answers instead of the numeric value

The Data Grid can now export the textual representation of values. This is controlled by the ExcelDataGrid:useNumberText configuration setting.

Bug 52711: Some incoming links are not displayed in the Show Links view

Structures which had a complex history of links and parent attachments would sometimes not display accurate information in the UI. This has been fixed.


Release Notes for "Andalusian" (Build 1493)

Improvement 51921: Handle factor indicator restatements better

Factor indicators can now also be marked as forecasted, and they are integrated into the restatement process.

Values which are converted through a Factor Indicator value (such as currencies) which has the forecasted flag set will now always also be marked as forecasted, so that the restatement process takes these values into account even if not explicitly marked as forecasted by the user.

Improvement 51948: Allow searching for the Indicator and Structure codes in the tree views

The search function of the tree views now also searches invisible data of entities, such as the code.

Improvement 52192: Allow using data quality and forecasted in reporting indicator formulas

The formulas used for reporting indicators (default, constraint, and plausibility) can now reference and use forecasted and dataquality data.

Improvement 52193: Set Flat XML as default format type for export

When exporting values to XML, the "Flat File" option is now selected by default.

Improvement 52279: Only apply implicit factor indicator 1:1 ratio on currency units

The Factor Indicator now only uses an implicit 1:1 ratio for currency units. This permits to convert from an unit to itself with a custom factor (such as Number -> Number, or tons -> tons).

Feature 44369: Allow viewing deleted nodes in Structure Management

Deleted structure nodes can now be shown in Structure Management, so that nodes can more easily be found (for instance for undoing the deletion)

Feature 44521: Store axes configuration along in My Selection

The configuration of the axes can now be stored along with the selection, so that the exact view is recreated.

Feature 52371: Allow to create and manage (global) user groups, so that permissions can be abstracted by group memberships

Global user groups can now be created, so that sets of permissions can be assigned at once through group membership.

Feature 52372: Implement user merging action and UI

Global users can now be merged; the new user inherits the subject ID of the duplicate user, which makes it so that the user effectively can use the permissions of both users

Feature 52378: Allow changing the indicator owner structure

The Owner Structure of indicators can now be reset without having to delete and re-create the indicator.

This is even allowed for indicators which are currently activated. However, doing this can cause data loss due to the change in indicator scope, therefore the user is confronted with multiple warnings when using this operation.

Feature 52410: For session-based setups, allow user impersonation for users on which one has ManageUser permissions

Users which have the ManageUser right on another global user can now impersonate this user, thereby getting a direct picture of what the other user sees.

Feature 52431: Allow changing the period indicator input level and frequency

It is now possible to change the reporting frequency and/or reporting level of period indicators in place without having to de-activate them to do so.

Since this operation is destructive, the user is warned at multiple levels when attempting to perform this operation.

Feature 52599: Allow using plausibility checks on Boolean Indicators

Boolean Indicators can now also check the plausibility of the entered value.

The available plausibility rules are:

  • None
  • Must be "No"
  • Must be "Yes"
  • Must be the same as the previous value
  • Custom Formula

Bug 51830: Some lists don't get updated immediately after performing an action

Some operations on structures, indicators etc. would not be reflected immediately in the UI, but only after some time. This has been fixed.


Release Notes for "American Cream Draft" (Build 1463)

Improvement 49564: Copy values of Factor Indicators upon reporting period copy

When copying a reporting period to a new reporting year, the latest value of factor indicators is copied along in order to keep previously-used factors in the new year.

Improvement 51971: Add support for wildcards in application mapping ignore list

The ignore list for external application mappings can now contain ? (any single character) and * (any number of characters, including none) wildcards.

Improvement 52186: Allow selection of Indicator Assignments by their indicator tag

When working with Indicator Assignments by structure and period, all indicators of a specific tag can now be selected with a custom action.

Improvement 49591: Do not use built-in groups for determining Application Access

The user membership in built-in security groups (Everyone, Anonymous and Authenticated Users) no longer has an influence on the Global:ApplicationAccess check, thereby preventing unwanted "invitation" of users by using these in Access Control Entries.

Feature 49650: Add API for external data sources (push)

Added external applications interface.

External applications can be managed through the "Security Management" module. Each external application has a key which identifies and authenticates requests received on the HTTP endpoint.

Applications can write values with the SetValues API, bypassing the normal configured workflow rules of SERAM.

After creating an application, mappings can be added to structures, indicators and data states. Also, the source for the indicator assignments needs to be set to the application in order to make the value read-only and allow the application to write data to these values.

Applications are subject to normal permission checks. Therefore, each application represents a subject (virtual user) which also appears in the value history.

To set data, the application needs Indicators:SetByApplication permission on both the structure and the indicator, and the period must be open.

Bug 44863: Tenant admins do not see all tenant users when adding permissions

Tenant administrators would only see global users to which they has some form of access. In restricted environments this led to missing entries in the offered user selection.

The system now always lists all tenant user metadata regardless of access to the underlying global user. Therefore, as soon as metadata is created for a global user, it will appear as selectable item in the subjects list.

Bug 47411: When a structure type has no nodes, it doesn't appear as owner structure selection when creating an indicator

Structure types without any nodes can now be selected as indicator owner, making the process for configuring new tenants from the ground up work as expected.

Bug 49674: The Excel Data Grid excludes indicators owned by structures not visible to the user

Indicators owned by structures to which the user creating the report had no access were omitted from the Data Grid. The behavior is now consistent with the Data Grid, users don't need to see the owner to get the inherited indicators.

Bug 51773: Editing the Indicator Assignment of a new Factor Indicator throws an error

A bug was introduced in a previous release where editing a factor indicator assignment would throw an unexpected error in the UI. This has been fixed.


Release Notes for "Altèr Real" (Build 1382)

Improvement 44360: Prevent invalid structure deletion and ambiguous names

Added checks and error messages when structures are being deleted on the same date they were created, or if there is a name (code) clash.

Improvement 45411: Rename values of booleans to "Yes" and "No" instead of "True" and "False"

Boolean values have been renamed to match user expectations.

Improvement 47347: Change value history view to use values directly and include row coloring

The history view was changed to use status-based color coding like the drilldown and data status controller views.

Improvement 47349: Color-code the data drilldown views with the least status

The data status controller views have been augmented with color coding based on the lowest data status of the row.

Improvement 47380: Display charts along with the value drilldown

The value drilldown automatically appends charts based on heuristics, typically yielding line charts for time-consolidated values, pie charts for structure-consolidated values and bar charts for calculation values.

The charts are grouped by unit, and only displayed if there is more than one values with the same unit and at least one value is non-zero or non-empty.

Improvement 47421: Render 2 levels in the Data Controlling Excel export

The Data Controlling Excel report now contains 2 levels of data (each data set in its own worksheet). Therefore, when creating the report on the Dashboard, the user will already get a breakdown by time index (containing the list of structures).

Improvement 47438: Links to external resources in markdown blocks should use a _blank target

Links generated in markdown which lead to external resources are now set as target="_blank", so that they always open in a new tab/window instead of re-using the SERAM tab/window.

Improvement 47441: Order structure value drilldown by numeric value descending

The value drill-down has an additional heuristic which causes a descending numeric sort if a structure is being drilled down.

Feature 36248: Multiple choice persistent indicator type

A new indicator type offering Multiple Choice selections has been added. This indicator can be used the create forms, or collect data to be used in formulas (for instance for a choose expression).

Feature 44448: Show a list incoming links when looking at the links of a node

On the Structure Links page, a (read-only) list of incoming links is displayed so that the structure relationships can be seen more easily.

Feature 44743: Drill down into value in Data Analysis

It is now possible to drill down into any non-input value in the Data Grid.

The drilldown provides a list of directly contributing indicator values. For instance, drilling into a calculation will return all the distinct values used in the calculation. Drilling into a structure-consolidated value (even cross-type) will return all values of the contributing structure level. Time-consolidated values will return the time indices used, e.g. a yearly value in a fiscal year will return quarterly values.

Any value in the drilldown list can be drilled down further down to the input value(s).

Feature 45283: Provide an additional Period Line Chart which compares the values of different years

A new line chart type has been added which overlaps the different the values of reporting periods (years), so that a line is shown for each period, allowing for simple visual comparison of values across periods.

Feature 46976: Export Data Controller views to Excel

The Data Status Controller list available from the Dashboard (including the drilldown levels) can now be exported to Excel.

Feature 47398: Add Pay-As-You-Go usage tracking

Support for a modern, pay-as-you-go licensing scheme has been added to SERAM. Current customers are not affected by this.

Feature 47436: Add support for data: URL in Markdown images

In order to help avoid HTTPS/HTTP mixed mode due to logo or dashboard message image loaded from a unsecure resource, support for data: URIs has been added in the markdown processing.

Images (up to 32kb in size for cross-browser compatibility) can therefore now be embedded in the markdown test, making external hosting unnecessary.

Feature 47442: Add CSS print media type for printing data grid, drilldown etc.

In order to enable printing charts and other information directly from SERAM, new CSS print media type styles have been added.

Bug 44078: Duplicate names in My Selections cause a user-unfriendly error message

Added a specific and clear error message for duplicate shared selection codes.

Bug 45674: Values meeting a specific set of conditions are missing in the XML export files

Some reporting indicator values as well as factor and choice indicators could be missing from the XML export. This has been fixed.

Bug 47415: The label in the Period Line Chart should not contain the year

The Period Line Chart now display the expected labels on the X (time) axis.

Bug 47439: Bullets are not displaying in markdown blocks

Fixed handling of bullets in markdown text (dashboard message, indicator descriptions etc.).


Release Notes for "Ariegeois" (Build 1325)

Improvement 45322: Only list active users in the Data Controller Dashboard drilldown

The names of structure data recorders shown in the data controlling drilldown are now filtered to exclude users who have been deactivated.

Improvement 45335: When de-activating an indicator which is still in use, the error message should include the period for clarity

The error message shown when a indicator with hard dependencies is being deactivated now displays not only the name but also the period, so that the dependency information is unambiguous to the user.

Improvement 45366: Only auto-expand structures in tree in Data Grid when there are 10 or less root structures

In order to make the structure selection in the Data Grid fit different needs, it will now only auto-expand the first level if there are 10 structure nodes or less on display.

Improvement 45373: Remove myOpenID from SERAM login

The myOpenID provider has been removed from the offered selections on the logon screen because the service has been discontinued.

Feature 44169: Automatically remove non-critical indicators dependencies when deactivating an indicator

When an indicator is deactivated, it is now automatically removed from groups and formulas in reporting indicators (default/constraint/plausbîbility) are removed if they reference the indicator.

Feature 44761: Re-introduce data quality for reporting indicators

As an optional feature (controlled through the setting Indicators:enableDataQuality), the Data Quality can now be collected on Reporting Indicators.

Feature 45307: Add config option to disable "Forecasted" dimension on indicators

The availability of the "Forecasted" flag on indicators can now be controlled via tenant setting Indicators:enableForecasted (true/false).

This allows customers who do not use value forecasting in their data management workflows to disable and remove this functionality.

Feature 45308: Allow tenant logo URL to be specified as part of tenant user metadata

For customers who wish to display different background logos depending on the user logged on to the tenant, they can now enable user-specific logos with the setting Style:userCustomerLogo (true/false).

Feature 45321: Allow to specify a customizable (setting-based) placeholder text on the "Comment" textbox

If the indicator comment field is being used for a specific type of comment/information in a tenant, a placeholder help text can be specified to provide user guidance.

The placeholder is retrieved from the JSON tenant setting Value:commentPlaceholder (can be specified as metadata object with multiple languages).

Bug 45318: Formulas with negative relative indicator index display a "- -" instead of "-"

Formulas which use indicator references with negative period offsets were rendered incorrectly, making them invalid when saved again. The roundtrip between system representation and user representation of formulas using such indicator references has been fixed.

Bug 45357: When a textbox is focused, clicking an action doesn't trigger the action

Fixed handling of action HTML refresh and keyboard default action submission to meet user expectations.

Bug 45362: The default formula cannot be changed through the UI

The changes made to default formulas were not always saved to the indicator. This has been fixed.

Bug 45380: "TypeError: savedSelections is undefined" when trying to save selection

Under certain circumstances, trying to save a selection would trigger a TypeError. Fixed.


Release Notes for "Anadolu Ati" (Build 1308)

Feature 43812: Simplify the rendered HTML in Data Entry mode

The whole Data Entry related part has been reworked to make it faster and more stable.

This affects Data Entry through either the Dashboard, Data Entry Module, batch operation in Data Grid or single value edit in Data Grid.

Feature 45234: Automatically create bundles of related JS files (code and template for instance)

The JavaScript files sent to the browser are now first analyzed for dependencies on the server, and after analysis bundles are created to reduce the number of requests required on a page load.

Feature 45280: Separate the user names in the Data Controller drilldown by semi-colons

User names in the Data Status Controlling view are now shown with semi-colons for easy copy-paste to Outlook

Feature 45281: Do no split the Bar Chart into multiple time charts when only one indicator or structure is selected

The bar chart no longer creates one chart per time index if a single indicator and/or structure is being charted.

Feature 45282: Use labels instead of timeline in the Line Chart to reduce user confusion

The line chart now uses regular labels instead of the timeline, unless time indices with day-offsets are being used (e.g. in reporting period types not based on months).

Feature 45293: In the Pie Chart, only include values > 0, and add an informational notice for that

The Pie Chart now ignores values <= 0, since these cannot be displayed in a pie.

Bug 45140: Loading a selection with a different indicator reference period uses the old period layout initially

A race condition was resolved where the previously loaded indicator tree was used instead of the one specified in the saved selection because the indicators were still being loaded.


Release Notes for "Altai" (Build 1289)

Feature 42797: Show friendly month names for period indices

The period indices now always show friendly names throughout the application, without the need to change the index code in the database.

Feature 42888: Show the formula for defaults/plausibility always

The formulas on the Reporting Indicator can now always be inspected by using the "Custom Formula" option when editing.

Feature 42939: Refactor activation and deactivation logic of structure indicators

All of the period indicator management parts have been fully overhauled to be simpler, efficient and more consistent in general.

Management of the indicator to structure assignments have also been addressed.

Feature 43132: Refactor indicator details view and have indicator type specific renderings

The "Show Details" action available in Data Grid and Data Entry has been overhauled to display consistent and meaningful information for all indicator types,

Feature 43833: Use metadata names in StructureViewer

The Structure Module now displays the localizable long names instead of the code on all nodes, level and type names.

Feature 43839: Generate content-dependent file names to enable efficient and failsafe browser caching

The JavaScript script files are now managed by their content, allowing for infinite caching duration on the client while solving all caching issues on the client at the same time.

As soon as a script file changes (e.g. when updating the software version), its name will change, thereby forcing the browser to load the new version and "forget" about the old version.

Since the JavaScript is compiled in advance, the server startup and warmup time is greatly reduced as well.

Feature 43849: Precompile all Jason and Coffee script files for performance and quality reasons

The Jason and CoffeeScript files are now compiled as a build step instead of being compiled on the fly on the server. This reduces the warmup time on the server and avoids problems due to JavaScript engine differences.

Feature 44260: Charting of selected value in Data Analysis

All Data Grid values or any row/column selection thereof can now be viewed as an interactive chart.

The system will separate data points which cannot be compared into distinct graphs. Values are deemed comparable if the unit, the structure level and the time frequency are identical.

The three chart choices currently offered are:

  • Pie Charts: All comparable data points are added to the pie.
  • Line Charts: The horizontal axis represents time, multiple lines are created for different indicators which are comparable. Note: For readability reasons, the dots on the lines are always displayed in the center of the time period. Also, by clicking on an entry in the legend, the line graph can be toggled on and off.
  • Bar Charts: The horizontal axis are structures, and one chart is generated per time index. Multiple comparable indicators are shown as multiple columns in the same chart. Note: By clicking on an entry in the legend, the bars of one indicator can be toggled on and off.

Feature 44299: Order the frequencies in a meaningful way instead of alphabetically

The frequencies available for selection when activating a persistent indicator, or when changing the input frequency of a Reporting Indicator, are now lowest to highest.

Feature 44410: Replace structure viewer in Indicator Owner Structure selection with tree

When activating indicators, the old structure selection control for selecting the owner structure has been replaced with a standard tree, making the selection simpler and faster.

Feature 44744: Dashboard for controller

A dashboard for Data Status Controlling has been implemented, analoguous to the pending data entry for data recorders.

The new list on the dashboard shows a summary of the data states a data controller role is responsible for, and allows for drill-downs to the structure and then to the indicator level.

To use this functionality, the data controller roles have to be flagged (in Security Management, edit role).

In order to only show relevant data status information, the system will only show current and past time indices. In addition to this, data states can be flagged as "terminal", which will make them irrelevant for the list display; only time indices with at least one non-terminal state will appear on the list.

Feature 44763: Option per Tenant to include all values on the comment Excel sheet (Data Grid Export)

As a configurable option, the Excel Data Grid export can include all values as a flat list on the comments sheet instead of only the values with a comment.

Feature 44764: Use the decimal places setting for the Data Grid report

The Data Grid Excel export now respects the decimal places setting at the time when the eport is started, thereby representing the grid shown on screen more closely.

Bug 42223: Speed issues with structure viewer in IE

Changes were made to the CSS file to speed up IE's handling of SVG.

Bug 44188: The "Custom Formula" UI option is missing for Reporting Indicator constraint

The constraint formula for Reporting Indicators can now be manually edited.

Bug 44300: Only display valid frequencies when activating an indicator

Only the frequencies valid in the selected reporting period type are now offered for selection when activating a persistent indicator, or when changing the input frequency of a Reporting Indicator.

Bug 44301: Display the reporting period type along with the date range when entering data

The reporting period type name is now always displayed when selecting a reporting period.

Bug 44455: The pencil is shown on values in Data Entry component even though no part of the value is editable

The display of the "pen" symbol has been tuned to be more in line with user expectations.

Bug 44624: After selecting a "Saved Selection" in the Data Grid, it remains loadable even when the grid is displayed

The handling of the Saved Selections has been overhauled to be more consistent.

Bug 44849: Markdown ignores the "mailto" protocol

The markdown processor used in SERAM now allows the conversion of [something](mailto:some@email.address) to e-mail links.


Release Notes for "Albanian" (Build 1223)

Feature 44120: Active Directory integration

Active Directory integration has been enhanced to allow easy user imports from a company directory, and automatic user synchronization (also disables users no longer active in the directory).

The simplified import is available in the subject selection view when adding permissions. Users are imported to SERAM, including their claims and metadata, and they are set to active.

The sync functionality is only active when enabled at the server level. Users are automatically disabled if they are disabled or removed from the directory. The sync runs upon application start, and every day at 1AM (local time) from there on.

Feature 44325: Excel user list

The tenant users list can now be exported to Excel, including information about their active status and claims.

Bug 44418: Default formula cannot use indicator references in Reporting Indicators

The custom formulas of Reporting Indicatorsd are now enabled to use indicator references, so that for instance a default can be computed using another indicator value.

Bug 44454: The indicator value is shown as editable in Data Grid despite being part of a non-editable period structure indicator

Some values were shown with a "pencil" icon indicating that a value may be edited, but they were in fact read-only and the server denied the edit operation when someone tried to edit. The "pencil" icon is now more reliable regarding the effective editability of values.

Bug 44456: In IE9, custom published colors are not used in Data Grid

The load order problem in IE9 has been adressed, so that the custom publication colors are now also respected.


Release Notes for "Akhal-Teke" (Build 1216)

Feature 42810: Add UI actions for enabling/disabling editing (values) of a period

Actions have been added to open and close reporting periods. This allows locking down a period without changing the individual editable settings of the period structure assignments.

Feature 42811: Add UI actions for enabling/disabling editing on indicators

All persistent period indicators have an "active" and an "editable" flag for each structure they apply to. Batch operations have been introduced to quickly makes changes to all structure assignments of period indicators.

Feature 43288: Display publication info on values

Published values are shown with a different color in Data Grid and in the Excel Data Grid report.

The color code can be changed by using the Value:publishedColor setting (expect a #RRGGBB value).

Feature 44032: Provide configurable compact number/unit representation in Excel Data Grid

To get a more compact representation in the Excel Data Grid, a configurable compact format option was added.

When this is set to true on the tenant level, the Excel Data Grid will no longer use two columns (one for the number and one for the unit) but instead use one only, displaying the unit as part of the number format.

Feature 44091: Excel Data Grid should include indicator descriptions

In the Excel Data Grid report, the heading cells not have meaningful comments with indicator description (and link info on structures and date range info on time indices).

Feature 44109: Provide e-mail address in the "Add Permission" user (subject) selection

The "Add Permission" view has been overhauled, inclusind a new column to display the e-mail address of a user, support for tenant-specific data, icons and bold for built-in subjects.

Feature 44118: Display version information in footer

The footer area now displays the SERAM version, and the version and browser information is automatically included when using the "report issue" link. This will make it easier to accurately track issues users might have.

Feature 44137: Sort Saved Selections by Code

The "My Saved Selections" list is now sorted by code.

Feature 44170: Display a "drag" pointer on the draggable members when editing a Group Indicator

The mouse now displays a "drag" pointer to increase usability of the group indicator editing view.

Feature 44174: Make the default for calculation data flows "Consolidate" upon creation

When creating calculations, the default data flow is now "Consolidate".

Feature 44211: Initialized indicator list report

When managing the activated indicators, the tree can now be exported to Excel. The information exported currently includes code, name, description, type, unit an formula.

Feature 44264: Indicator Publication management

Publication management has been added.

Publications can be added, edited and removed; all values modified on or before a publication are shown as being published, the other values are displayed as usual.

Note: the behavior is different to SERAM v1, where publications were a distinct value status. THe new approach allows removing publications and also does not lock values to a non-editable status.

Feature 44265: Show Publication info in Value History

The value history displays the publication status for each value snapshot in the history.

Feature 44266: Restate Forecasted indicators of period

A batch operation has been added to restate all editable, forecasted values in a non-editable status of a reporting period back to an editable status.

Feature 44267: Copy reporting period

Copying reporting periods has been implemented, so that an existing reporting period can be used as template for the new period.

When a period is copied, all period indicators and period structure assignments are copied. However, the period is created in closed state and the editable flag of period structure assignments is re-set.

Values are not copied, and the indicators assignments on deleted structures are discarded as well.

Feature 44358: Add configuration setting to make all indicators available to users without changing root structure

The configuration setting DataAnalysis:showAllIndicators (boolean) has been added. When set to true, all indicators available to the user are shown instead of only the ones in the scope of the root structure.

Feature 15767: Customizable Reporting and Input Frequencies

New tenants have more reporting period types available:

  • Fiscal Year (same as before)
  • Gregorian Year (12 months, no quarters)
  • 4-4-5, 4-5-4 and 5-4-4 years (4 quarters, each with 3 months with weeks)
  • International Fixed Calendar (13 months with 4 weeks each)

Bug 43214: Constraint formula is not detected/shown

The constraint information shown in the indicator details view did not reflect the effective setting. This has been fixed.

Bug 43245: Don't return tag associations on indicators for deleted tags

When deleting indicator tags, the associations were not correctly removed. This has een fixed.

Bug 43400: Apply ordering to indicator list when activating indicators

The indicator list when activating indicators is now properly sorted.

Bug 44030: Message box stops displaying message

The dashboard message sometimes disappeared when changing application modules. This has been fixed.

Bug 44037: "My Saved Selections" doesn't appear when the user has only access to one structure

The "My Saved Selections" would not show up for users which have access to only one structure. This has been fixed.

Bug 44038: Saved indicator tags are not restored when loading selection

When saving selections, the indicator tags were not loaded from the saved selection. This has been fixed.

Bug 44039: Verifier role sees button but cannot change status in single edit in Data Grid

Some valid operations were not accepted by the server due to a overly restrictive security check. This has been fixed.

Bug 44040: The Saved Selections list is not populated if no user has metadata

The "Saved Selections" would not display any items if no tenant user metadata was entered in the system. This has been fixed.

Bug 44047: Comments on text indicators are ignored on import

In contrast to SERAM v1, text indicators no longer have a comment field since this was somewhat redundant and misleading. However, this change led to data entered in comments not being imported as expected by the user.

The import now merges the text and comment during the import phase.

Bug 44055: The textarea of Text indicators in the Data Entry views does not accept line breaks (return key)

Line breaks are now allowed when entering data in Text Indicators.

Bug 44072: When activating a persistent indicator owned by a specific node, don't allow to pick a persistence level above

Invalid level choices are no longer displayed when persistent indicators owned by a node on a lower level are activated.

Bug 44079: Duplicate code for My Selection should be allowed except for shared selections

For non-shared "My Selections", the code now only has to be distinct per user.

Bug 44141: The details view for an indicator doesn't correctly list the activations

When looking at the details of an activated indicator, the list was showing only one activation. This was fixed.

Bug 44159: JS error "'post' is undefined" in ModuleDataEntry.js

Fixed load order problem which led to an error message on some browsers.

Bug 44367: Virtual higher-frequency factor-based values seem inconsitent when the status is non-editable and their factors have changes

The virtual values are now computed with the factor which was used at the time the value was set to the non-editable state, giving the expected numeric representation on the virtual reporting values when using a factor indicator.

The old behavior is however still applied to unit conversions, since these may use an offset, which would render the virtual values invalid if processed with a static factor (e.g. °F -> °C).

Bug 44384: Users may see indicators owned by structures branches where they have no access

The indicator list was filtered by the indicator tags only, therefore it was possible that users with limited access were able to see indicators owned by structure branches where they had no access whatsoever.

The indicator list is now always also filtered down by the user permissions on structures, eliminating indicators which are out of scope for a user.


Release Notes for "Aegidienberger" (Build 1181)

Feature 43412: Decide how to handle deactivation of indicators with values

Deactivation of indicators which have values now asks for user feedback to prevent data loss by user mistake.

Feature 43715: Allow users to save and load Data Grid selections

Users can now load, save, share and take ownership of selections. Only the selection owner can modify the selections.

Which selections are saved can be controlled when saving them, so that partial selections can be created and shared with others (e.g. indicators and time but no structure, so that users can pick that selection for their structure).

Sharing and taking ownership requires tenant-wide permission to do so. Two new rights (Selections:Share and Selections:TakeOwnership) have been added to the Role management for this purpose.

Feature 43729: Add "Reset" action to reset Data Grid selections

The selections made can be reset by clicking the "Reset" button beneath the loaded Data Grid. This allows to return to the selection screen where the Saved Selections are.

Feature 43809: Allow user to always deselect selected rows in the DataGrid component

The datagrid component (e.g. the lists of items) now always offers the choice to de-select a selection, even when filtered. This makes its use easier when the user forgets to de-select before paging or filtering.

Feature 43848: Don't reload the Data Grid when changing axes configuration

When the axes configuration is changed, the data in the grid is no longer reloaded since it is the same data represented in a different way.

Feature 43921: Batch operation to set blanks to zero in Data Entry

The Data Entry views now also allow the use of the "Set blanks to zero" (if enabled on the tenant level).

Feature 43933: Batch forecast terminology

The terminology for the "Forecasted" batch operations have been adjusted to be more intuitive.

Feature 44001: Apply indicator sort key order inside of calculations

Calculations now sort their used indicators by sort key as well, instead of the name only.

Feature 44011: Allow bulk adding permissions to multiple subjects

When adding permissions, multiple subjects (users) can be selected as once, so that assigning large numbers of identical permissions can be performed more efficiently by the administrator.

Bug 43688: Client-side error on editing calculation

Editing a calculation could throw a client-side error. This has been addressed.

Bug 43826: Hide tip tip when changing views

The tooltip shown for comments etc. is now properly hidden when the application view changes.

Bug 43832: Deal with keyboard input in dropdown tree

The dropdown tree now longer allows bogus entry of text.

Bug 43862: Don't break lines if unit doesn't fit

On narrow screens, the unit would break to the next line if it was long (such as "kWh"). Now it remains on the same line.

Bug 43918: Status change from completed to verified finds no values to update when performing Data Entry batch operation in Data Grid

Data changes were using stale data on the client. Now they always use the latest data.

Bug 43934: Make it possible for normal users to see other users metadata

All user names registered in the Tenant Users are now accessible to users of that same tenant. This avoids unreadable IDs in place of user names in various places.

Bug 43940: The correct computations level selection is not initially checked when editing a calculation

The computation level selection for calculation now correctly works when editing calculations.

Bug 43942: The period dropdown when editing a calculation formula is in random order

The period order is now descending by date.

Bug 43944: Don't show the checkbox for invalid indicators when picking indicators for calculations

When editing calculations, only valid indicators can now be selected, instead of allowing the selection but then showing an error message.

Bug 44003: Exception "Unable to get the value of property 'periodType'" in Data Entry

Fixed race condition when opening Data Entry which could cause a client-side error to pop up.

Bug 44015: The use of relative indicators in plausibility checks or constraints can cause significant performance degradation

The internal processing of the relative() function has been adjusted so that it doesn't require a hard dependency on previous years, thereby making the indicator listing and computation more efficient.

Bug 43336: Return newest audit entries if no filter is set

The user audit log now shows the most recent entries when no date filter has been set.


Release Notes for "Abyssinian": SERAM v2 @ Novartis: Fix 1 (Build 1170)

Feature 43714: Show comment of values in Data Grid as tooltip on an icon by the value

In the Data Grid, the red triangle which notifies the user about comments on the value has been moved to the cell, so that it is also shown for boolean and text indicators.

Feature 43892: Make the reporting indicators show monthly values

Indicators with higher input frequency now display virtual values with these, and sums are also broken down into virtual values in higher frequencies.

The old behavior can be kept by setting the "Indicators:computeValueFractions" setting to "false".

Feature 43893: Prevent the PeriodIndicators from loading multiple when opening the Data Grid

Opening the Data Grid module is now quicker, because a redundant call to the server has been removed.

Bug 43229: Fix order of periods in data entry

Then multiple reporting periods are available for selection in Data Entry, they are now ordered correctly.

Bug 43281: Data Grid text may overlap cells

The text in the top headings of the Data Grid is now cut off when it is too long, as to avoid overlap into the next heading.

Bug 43678: Text extends into value on data entry

The indicator description now shows an ellipsis character when it overflows in Data Entry, so that it doesn't write over the value part.

Bug 43847: When re-entering the "Axes configuration" view, all checkboxes are enabled, so that invalid selections can be made

When re-entering the "Change Axes" view after choosing explicit axes, the user now cannot choose invalid configurations anymore.

Bug 43867: Description field runs out of space in Data Grid

The description field in the indicator information view has been expanded to show all its contents.

Bug 43902: View details of calculated indicators produces error

The details for calculated indicators and groups can now be looked at without producing an error message.

Bug 43904: Average incorrectly calculated

The average over time is now computed from the non-empty values, and no longer from all values.

Bug 43907: Indicator sort order in Excel Data Grid report may differ on the root level

The root sort order of indicators in the Excel Data Grid now matches the order in the Data Grid module.


Release Notes for "Abtenauer": SERAM v2 @ Novartis: Release (Build 1162)

Feature 39045: Dashboard view on how many open/entered/verified indicators for the various users

The Dashboard can now display a customized list of pending Data Entry tasks per user.

The list is created by looking what locations a user has roles enabled for Data Entry, and finding the pending (open) indicators on these.

A configuration setting on the tenant exists to control whether the links are broken down by tags, or if indicators of any tag for one location are consolidated into one entry.

Feature 43237: Data Analysis "screen dump" report

The Data Grid can now be "dumped" into an Excel workbook. The Reference Environment and the axes are applied in the same way, and a separate spreadsheet is generated with a summary of comments made.

Feature 43241: Post messages to the dashboard

Tenant administrators can now customize the message that is shown in the top area of the Dashboard.

The message can be formatted using Markdown syntax, an it is displayed to all users of this tenant.

Feature 43287: Group and order indicators in Data Entry by their parent indicator

In Data Entry, indicators are now grouped in the same manner as in SERAM Lite: grouped by their "parent" group or calculation.

Feature 43344: Data Entry - message for non-relevant indicators

Instead of showing no selection possibilities, the user now gets a message when he got into a dead end in the Data Entry selection process.

Feature 43389: Provide better Plausibility Message when changing status

The various error messages shown on value change errors are now better worded for the average user.

Feature 43436: Structure Tree in Data Entry

The flat list for selecting the Data Entry structure has been replaced by a tree showing only the relevant paths to the available structures.

When the number of available structures is less or equal to 10, then the tree is completely expanded to enable a quick selection of the structure. Otherwise, the tree is collapsed.

Feature 43468: Make failed plausibility checks more obtrusive

Invalid values (either failed constraint or plausibility) are now colored with a red background.

Feature 43471: Pre-select single organizations in Data Grid

When a users permissions only permit him to see a single structure, this structure is automatically pre-selected in the Data Grid selections.

Feature 43472: Provide access to both other axes when editing axes in Data Grid

The user can now always navigate to the other two axes when choosing his selections for the Data Grid.

Feature 43475: Widen the left heading column in Data Grid

The left (vertical) heading column has been widened a bit to make longer names (especially with nested indicators) more readable.

Feature 43477: Make it visually obvious which values are editable

Editable values are now shown with a pen symbol, so that they can be spotted in the Data Grid and in Data Entry.

Feature 43504: Allow color styling of application

Tenants can now use customized color schemes as additional branding/customization functionality.

Feature 43652: Change tree action buttons

The contextual action buttons in the tree to select/deselect have been changed based on user feedback to make them more self-explanatory.

Feature 43653: Make the "Fill with 0" batch action an optional feature which can be disabled through the settings

The batch operation for filling empty values with 0's can now be disabled through a tenant configuration setting.

Feature 43654: Provide a Data Entry interface view in Data Grid when a row or column is selected

When selecting multiple values in Data Grid (e.g. by clicking a column or a row), a new batch operation for editing the values is presented.

The value editing opens a view similar to Data Entry, so that a series of values can efficiently be edited from within the Data Grid.

Feature 43676: Make batch operation success message non-modal

The success message after performing a batch operation is no longer modal, so that the user doesn't get interrupted.

Feature 43759: Use a tree view when changing the structure in the reference environment

When changing the Reference Environment in the Data Grid Module, the user is now presented with a normal tree view instead of the full structure viewer.

This change enables users of older browsers (IE8) to use this functionality without issues.

Feature 43769: When a batch operation fails, ask the user if he wants to re-try with "force"

When errors occur on batch operations (such as due to missing permissions or concurrent value changes), the user is now presented with the option to re-try the operation, skipping any errors occurring.

This enables the user to perform a "do what you can" batch operation.

Feature 43770: Provide batch operations in Data Entry

Batch operations, such as setting the status to entered, are now also available for the values displayed in Data Entry.

Feature 43806: Automatically pick the 3rd axis after changing two in the "Configure axes" view

When manually configuring axes in Data Grid, the 3rd selection is now implied from the two selections made before.

Bug 43381: Plausibility Flag Not Consistently Displayed

When a value fails a plausibility check after editing, the flag and check result are now displayed correctly.

Bug 43414: Boolean indicators without numeric value don't display a value when not open

In Data Entry, the display of boolean values in non-open state has been fixed to show the value to the user.

Bug 43420: Country Data Calculation Error

The computation rules for data viewed through structure links but not computed on a specific level have been adjusted to compute the value as expected.

Bug 43421: Save toggle is not added/removed when values change status

An issue was fixed where a value could not be edited after being re-stated without reloading the data.

Bug 43423: Values of read-only periods cannot be inspected in Data Analysis

The initial release only allowed to inspect the details for editable values. How the details are available for all values.

Bug 43426: Numbers returned as "infinity" cause an error message in Data Grid

If a computation would return infinity (e.g. x/0), the Data Grid would show an error message to the user. THe value is now correctly shown as being empty.

Bug 43427: Axis headings not visible with a large number of columns

In the Data Grid, the top heading now adjusts itself to keep the text visible at all times.

Bug 43429: Order of Sites / Indicators / Time in Data Grid

The order of the columns in Data Grid has been fixed to better match the order of the trees in the selection windows.

Bug 43462: Long unit symbols are wrapped in the Data Grid cells

Unit symbols which are long now longer get wrapped (and thereby made almost unvisible) to a new line in the Data Grid.

Bug 43469: Don't allow to focus read-only values in Data Entry

Internet Explorer would sometimes show the caret in the the wrong input field. This has been fixed.

Bug 43474: Prefilled zeros are not displayed in the Data Grid

Default zeros are no longer omitted from the Data Grid display.

Bug 43509: Display tree for indicators when editing calculations

When editing calculations, the indicators are now shown as tree instead of a flat list.

Bug 43571: Data Grid crashes instead of displaying data in IE8

Added workarounds to enable IE8 usage in the Data Grid.

Bug 43679: Error message when trying to request data for a calculation on a specific level

The calculation on specific levels now work correctly independently of the level where they are queried on.

Bug 43694: Text indicators are not well presented in the Data Grid

Text indicator values in the Data Grid are now displayed in a more usable and accessible way.

Bug 43737: Add full localization support to all localizable items (indicators, structures, etc.)

All items which are localizable (indicators, structures, other names and descriptions) now offer the translation actions, and the translated names are used throughout the tenant.

Bug 43751: Produce and error when the user uploads an xml file that has invalid numeric values

Uploading invalid numbers (invalid number formats) now returns an error instead of silently skipping the problematic value.

Bug 43805: Tool tip not working

The "Exclamation Mark" icon now always shows the information tooltip when clicked.

Bug 43808: The batch operation for setting values to zero in Data Grid is not always available when expected

A wrong check was fixed, so that the action now appears correctly when values can be set to zero.

Bug 43820: Grid doesn't show updated value after clicking "Back" after editing

In a very specific order of events, the Data Grid would not automatically reload after making edits to a value.

Bug 43879: Selecting Q1 in Data Grid also selects indexes 10, 11, 12, 13, 14, 15

The selection of a Q1 column/row in Data Grid no longer also selects July, August, September, October, November and December of the same year.


Release Notes for "Abaco Barb": SERAM v2 @ SIRIUS: Go-Live / Migration

 


See also

SERAM Help and How-to
Last modified: 24.06.2020 20:01
© 2009-2013 Sirius Technologies AG