What's New in BackOffice Associates® Solutions 7.0

This topic contains:

WARNING: Any additions or changes users have made to CTS configuration (Admin > CTS >Configuration) may be lost when upgrading from DSP 6.6.x or earlier.

Prior to any upgrade backups should be taken of all databases. Once the upgrade is complete, if any custom CTS configurations are found to be missing, then the backup of the CranSoft database should be restored to a new database (DO NOT restore it to the CranSoft database). The missing custom configurations can be merged into the CranSoft.dbo.CTSConfig% tables from the restored backup.

Please contact BackOffice Support at support.boaweb.com if you would like assistance with this activity.

New Features

Updated User Interface

  • The look and feel of the DSP® has been updated for 7.0. All pages and functionality are still available. Refer to DSP® Navigation for more information.
  • The Styles page in System Administration has been updated with additional options. After upgrading to 7.0, custom styles may have to be updated by an Administrator. Refer to Add a Style in System Administration for more information.
  • Images in the DSP have been updated to svg format. Refer to Add or Update Custom Icons for Custom WebApps for more information about working with svg images.

Updated Online Help Interface

  • The look and feel of the online help has been updated. Refer to How to Use Online Help for more information.
  • The online help is now hosted and accessible via a URL, instead of being installed on site with the DSP. This allows for updates and improvements to help to be made independent of a product release.

Enhancements

Data Stewardship Platform (DSP®)

The DSP now supports SQL Server 2017.

System Administration

  • Administrators now have an avatar icon in the Site toolbar that displays the Administrator’s initials and has a service light. The service light continuously displays the current status of background jobs. When admin users click the avatar, depending on the service light color, the icon directs the user to different linked pages. The service light colors indicate:
    • Red — Service down; links to Resources page
    • Yellow — Service job failed; links to Jobs (Failed) page
    • Green — Nothing in failed job queue; links to Resources page
  • The Styles page has been updated to reflect the additional interface elements that can be styled with 7.0. Elements that are no longer styled have been removed.

    NOTE: Custom styles may need to be adjusted after an upgrade to 7.0. Refer to the Styles page for information about each option.

Online Help

Resolved Issues

dspConduct™

  • Corrected an issue where the request status displayed in the Content WebApp incorrectly. When a request displayed the “Scheduled” request status in dspConduct, it displayed the “Request in Process” status in the Content WebApp. With the fix, the request status displays correctly in the Content WebApp, and users can view which requests are scheduled to post in the future. [DSP70-185]
  • Fixed an issue where, under certain conditions, records were not written to a log table when a role was not used in any of the later dependencies in a request. For example, if role 1 had roles 2, A, B, and C dependent on it, and role 2 had roles B, C, and D dependent on it, when role 2 completed, no log entry was created for role D. Additionally, if role D was dependent on any other role, no log entry was created. Now, records are written to the log table without issues. [DSP70-202]
  • Fixed an issue when using the Group Post feature where the user ID of the person triggering the posting process was not recorded correctly against each of the posting steps. The user ID stored as the request's Posted By value is now used for the individual posting processes in that request. [DSP70-203]

dspMigrate™

Map

Deadlock errors occurred and duplicate fields displayed on the Target Source Schema page in Map when a user selected multiple fields and clicked the Reset button. With the fix, the Reset icon is active when one field is selected, and is dimmed when multiple fields are selected. [DSP70-198]

SQL AutoGen

Fixed an issue where, in certain situations, DSP did not map the correct SQL Server data type to a System Type field’s data type when building tables using AutoGen. With the fix, all relevant data types can now be mapped for System Type field’s data types, and tables are built correctly. [DSP70-201]

Transform

An issue occurred and users could not execute target reports that had key field names that contained special characters. With this fix, users can execute target reports in Transform, even if the key field names contain special characters. [DSP-6552]

dspMonitor™

Postal code formats for validations used in dspMonitor™ have been updated as a result of SAP OSS number 1381564. [DSP70-199].

Data Stewardship Platform (DSP)®

An issue occurred where SSIS packages took too long to process. With this fix, the code for processing SSIS packages was changed back to OleDB.net and is processing quickly; users no longer need to use the ManualSSIS Package workaround. [DSP70-270]

Common

An issue occurred where Lookup Table values were not being populated when System Types were imported into Common. With this fix, System Type Import populates Lookup Table values for System Types Table Fields as expected. [DSP70-282]

Online Help

  • The navigation for the field description topic describing the Target Source Copy To page in the DSP was improved. Also, both a field description and use case topic were added to the help that explains the Target Rule Copy To page in the DSP. [DSP-9544]
  • Improved the RANGE LOW and RANGE HIGH field descriptions on the Sample Sizes (Setup) page in Transform.

IG Universal Connect

Fixed an issue with the plugin used by Integrate and Collect to call Boomi that caused an error when the number of processes in a single account was greater than 400. [DSP70-87]

WARNING: Customizations made to any component of the delivered BackOffice Associates® Solutions 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

NOTE: 6.5.4 and 6.5.5 versions of BackOffice Associates® Solutions were not released. The immediately prior release to 6.5.6 was version 6.5.3.

NOTE: A 6.4 version of BackOffice Associates® Solutions was not released. The immediately prior release to 6.5 was version 6.3.1.

Help Build Date:December 20, 2018 11:15:06 AM

See this topic in Version 7.0.2

See this topic in Version 7.0.1