What's New in BackOffice Associates® Solutions 6.3

This topic contains

New Features

Target Design

In Target Design, users can set dependency relationships (parent and child) for targets across all Waves and Process Areas. Users can view all relationships for a selected target as well. Refer to Set Target Dependencies for more information.

dspCompose

The data sources available for View Import at the Template-Role level are now limited and configured on the new View Import DataSources page. Refer to Add a Data Source that Stores Views for Import for more information.

Added naming conventions to the Parameters page for views used to import data into a request.

Construct

New custom pages and existing custom pages created with Full Construction and Enrichment Construction can use Excel Integration and Bulk Execution. For Full Construction pages, these features are available after the user syncs a target, using Target Design with a source of {Full Construction} with Map. For Enrichment Construction, these features are available when a field mapping with an action of Construction is submitted on the Field Mappings page in Map.

Transform

Added ReportsOnly WebApp group.

dspTrack

In dspTrack, added the Resource Synonym page allowing users to map the resource names from an MS Project plan to the DSP® users.

Excel Integration

End-users of DSP® application pages that need to import data from Excel into custom DSP® pages can use Excel Integration. This feature is primarily for users of Data Construction pages and custom applications pages deployed at customer sites by technical power users.

Bulk Execution

Bulk Execution is the ability to run an event on a DSP® page for all records or a subset of those records via a simple, guided user experience.  

For the initial release (6.3), it is limited to the bulk execution of the Validation event (the event that checks to see if a record is valid).

End-users of DSP® application pages can perform Bulk Execution on custom DSP® pages created by the page Designer. The following DSP® pages are delivered with Bulk Execution enabled:

  • Tables (Collect)
  • Data Source Registry (Common)
  • Plan Task (dspTrack™)
  • Field Mappings (Map)
  • Users (System Administration)
  • Rules: Basic Rules (Target Design)
  • Target Fields (Target Design)
  • Target Data Services Rules (Transform)
  • Target Data Services Reports (Transform)
  • Target Reports (Transform)
  • Target Source Reports (Transform)
  • Target Sources (Transform)

Enhancements

  • In Target Design, a user can add a description of a lookup table on the Target Lookup Table page's Vertical View.
  • In the online help, explained registering a data source in Common as the preferred method and described the sync process for data sources for Common and System Administration. Refer to Data Sources in Common for more information.
  • Three charts were added at the Wave level: Field Construction by Wave, Value Mapping by Wave, and Field Mapping by Wave.
  • To improve accessibility to chart data, charts across the DSP® allow users to access the data in a tabular format. When a user clicks the View Data icon to the right of a chart name, a pane opens that displays alternate text descriptions of chart data in a table.

Bugs Fixed

  • When the SQL AutoGen process generated tables for Construction pages, if the table name contained special characters, the table name was not included in brackets and the table was not created. In addition, reports and remediation reports did not generate. With the fix, the target table, source table, and reports allow for custom tables with special characters in the table name.
  • An issue occurred when creating a source using SQL AutoGen. When a user added a source to a target in Target Design but did not initially set a System Type for the source, an error displayed when the user attempted to create the source table on the Automation SQL Target Source page. With the fix, the source table can be created in SQL AutoGen when a System Type is added to a source after the source was initially added.
  • When a mapping was imported, exported or copied, if relationships existed, they were not included with the mapping. With the fix, existing relationships are included with mappings when copied, imported, or exported.
  • In Map, an issue with changing the Action on a mapping has been fixed. If a field mapping was saved with the Copy Action, an error displayed if a user attempted to change the Action to Internal. With the fix, a user can edit a mapping and change the Action from Copy to Internal and no error displays.
  • An error displayed if a user attempted to auto-generate a table under certain conditions. In Target Design, a user updated a Key Target Field (e,g,, KUNNR)’s Date Type from NVARCHAR to DECIMAL. The user then deleted the corresponding zLegacy* record (for example,zLegacyKUNNR). After synching Map and Target Design, the user attempted to auto-generate a table and received the error. When Target Design attempted to create the zLegacy field, it did not create the data type (DECIMAL) of the zLegacy field correctly. With the fix, the data type of the zLegacy field is created correctly, and a user can auto-generate a table without receiving this error.
  • When a System Type was imported into Target Design, all targets in all Waves displayed the message "Pending Design Changes"  in the Status of Sync column on the Targets page. With the fix, when a System Type is imported for a target, only that target displays the Pending Design Changes message on the Targets page.
  • When registering a source to a target in Target Design, occasionally the request timed out and the source was not added. An insert statement in a stored procedure has been optimized and sources can now be registered to targets.
  • In dspCompose™, corrected an issue that caused external request scenario processes that existed on upgrade from dspCompose™ 6.0.3 to fail. With the fix, external request scenarios that existed before the upgrade process.
  • The download time for SSIS package types was slow, taking longer to download than other package types such as DTS and Assemble. With the fix, SSIS package types download more quickly at a rate comparable to other package types.
  • In System Administration, corrected an issue where the default page sort was on the toolbar field.  With this fix, the page is ordered by the first visible column. A down arrow beside the column header denotes the sort order.
  • In System Administration, corrected an issue where the import and export buttons on the Catalog page's Vertical View were not working.
  • An issue was fixed related to custom security roles and security access in Console. If a custom security role allowed access to a single Wave and Process Area and limited objects within that Wave and Process Area, users assigned to the custom security role did not have proper security set. These users could access additional Process Areas and objects and add targets in Target Design, though the targets did not display on the Targets page for the user. With the fix, security checks have been added to Process Areas and objects so that the configured security is enforced.
  • When exporting a target report in Transform whose rows exceed the limit for Excel exports, a delimited file is generated instead of an Excel Workbook. A hard-coded semicolon delimiter was used, so if the report data contained a semicolon, the report generated a new column for each occurrence of the semicolon in the data. With the fix, the user can change the delimiter applied to a character that is not present in the report data so that reports are formatted as expected on non-Excel exports.
  • In Transform, Generated Reconciliation/Audit/Technical Specs report creation was removing white space between words from text fields, making them difficult to read. With the fix, white space is retained to maintain readability.

Enhancement Requests

  • Across all components in the product, a record can be added to a filtered record set.
  • Added support for sorting on the boaStatus column on Collect's Targets, Target Sources, and Tables pages. The header for this column is S.
  • In Console, an Administrator user can assign a default Context for users. Refer to Set the Default Context For a User for more information.
  • In Console, a user can assign multiple Developer or Business User contacts to an object(s) at the same time. These object assignments cascade down to Target Design, and the contacts are assigned to every target and source in the object. Developers can review and approve mappings. Business Users are used for reporting purposes and allows users to receive published reports and Data Services reports from Transform. Refer to Add Multiple Target Contacts to an Object for more information.
  • In Target Design, the user can view all pending changes for a target on the Target Design Pending Changes page (Design > Targets > Pending Design Changes).
  • In Map, a user can view a list of all archived mappings across all Waves and Process Areas for a field (based on System Types) and import a mapping for use in the selected target or source. Refer to Copy a Mapping for more information.
  • Updated the online help for the Value Mapping (Config) page in Map. The Refresh button's description includes the note "The language to be refreshed is controlled at the Wave level (Console > Wave > Vertical View > Language field)."
  • In the online help, added a troubleshooting topic in Integrate documentation: Resolve Problem Connecting to the SAP GUI During Template Recording. The topic describes how to configure security settings in Internet Explorer to resolve the issue.  
  • In Transform, when a user processes Rules Only, the record count for the target is now updated.
  • An enhancement request from BOAUnited Customer addresses an issue with filtering on a single client when generating views from an SAP source using SQL AutoGen. When using SAP, a filter on the Client column is now included in the Where clause when generating views based on check tables that contain the Client column.
  • If a target exists in the database, a user cannot build a table using SQL AutoGen until the target is synced with Map. Refer to Build Target Tables Using SQL AutoGen for more information.
  • In Transform, when a process fails and the user clicks the Continue button on the Monitor page, the status column on the Monitor page updates to reflect the correct status ("Processing").
  • In dspMonitor™, a user can add a subset of frequently used reports to the Your Favorite Reports page. Refer to View Your Favorite Reports for more information.

 

WARNING: Customizations made to any component of thedelivered BackOffice Solution will be overwritten in the next upgrade. To preserve customizations, make a copy of the customizations prior to applying any upgrade.

A customization is a change to the underlying source code, which differs from configuration – normal setup of the software, such as setting up workflows and defining parameters via the configuration pages.

Previous Versions