InterConnect offers an array of Portals that allow access to SAP Business One for different user audiences. Each Portal has its own website, but uses common infrastructure to connect to a specific SAP Business One company database. Details of infrastructure requirements and software prerequisites are outlined below.

Confirm infrastructure

For a detailed outline of possible configurations, see Infrastructure Architecture. The configurations below describe the most common server arrangement.

Infrastructure (InterConnect, Portals or SPS Cloud EDI)

Infrastructure Example - InterConnect, Portals or SPS Cloud EDI - SQL or Hana database.
Infrastructure Example - InterConnect, Portals or SPS Cloud EDI - SQL or Hana database.

Component Summary

Application Server

Hosts Windows-only applications, including InterConnect server components, B1i components and other third-party Windows applications needed for B1. This is required for both Hana and SQL database versions.

This requires a Windows Server.

InterConnect Server Components include:

  • InterConnect Server Tools
  • B1WebAPI
  • License database*
  • Workflow databases (Hana Only)*
  • InterConnect Manager Add-On
  • SPS Add-On (if applicable)

* Note: Hana B1 databases require 64-bit Microsoft SQL Express, Standard or Enterprise to be installed on this server.

SAP Business One Components requirements include:

  • SAP Business One Client
  • DI-API 32-bit (B1 version 9.3 and lower)
  • DI-API 64-bit
  • Legacy DI-API (B1 version 10)
  • ODBC Hana drivers must be installed (Hana database version only)

Ports:

  • Ports are closed to the general internet (i.e. “Behind the firewall”) for security purposes.
  • Ports 4000 to 5000 must be opened to permit access from the SaaS hosted Web Server.

Database Server

Hosts SAP Business One Hana databases.

This requires a Linux Server for Hana environments or a Windows Server for SQL environments.

No InterConnect components are installed on this server.

SAP Business One components are as required for a SAP Business One implementation.

RDP Server

Allows access to the B1 client and internal resources via Remote Desktop Connection.

This requires a Windows Server.

InterConnect Server Components include:

  • InterConnect Manager Add-On
  • SPS Add-On (if applicable)

SAP Business One Components include:

  • SAP Business One Client
  • DI-API 32-bit (B1 version 9.3 and lower)
  • DI-API 64-bit
  • Legacy DI-API (B1 version 10 only)

Firewall

Permits or rejects incoming connections. Used to restrict access to sensitive business data.

SaaS Hosted Web Server

Hosts InterConnect Portals or third-party web applications. Note that this requires either a Shared or Dedicated Software as a Service (SaaS) server. Contact Sales for available SaaS subscription options.

This requires a Windows Server.

InterConnect Server Components include:

  • InterConnect Portal websites

No SAP Business One components are required on this server.

SSL Certificate is required per domain.

Detailed examples for SQL and Hana are shown in Infrastructure Architecture.

Before Installing a Portal

  • Identify the web server where the Portal website(s) will be installed. Will this be a Shared SaaS hosted web server or a Dedicated SaaS hosted web server?
  • Identify the SAP Business One server and Application server where B1WebAPI and InterConnect Server Tools will be installed.

  • Ensure Typical Hardware and Software Requirements are met.
  • Ensure full administrative rights are assigned to the user who will be installing the software.
  • Create a back-up of all SAP Business One databases prior to installing new products.
  • Carefully review this Implementation Guide prior to performing the installation and basic configuration.
  • Download the latest version of the Portal package.

Review Hardware and Software Recommendations

Typical Hardware/Software Requirements

  • Application Server Requirements
    Hardware Minimums

    Speak with your SAP Business One consultant to confirm these details also cover other third-party application requirements.

    • 4-8 GB RAM or higher.
    • 2GHz Dual Core processor or better.
    • 100 GB hard drive or higher.
    • 100 Mb Network or better.
    Software
    • Windows Server Datacenter, Enterprise, Standard or Web Edition. See Release Notes for supported versions. Ensure all stable security patches have been applied.
    • Microsoft SQL Server. See Release Notes for supported versions.
      • Hana Only: 64-bit Express Edition or 64-bit Standard/Enterprise Edition.
      • SQL/Hana: 64-bit Standard/Enterprise Edition.
    • IIS including IIS6 Compatibility Modules (See: How to Configure IIS)
    • .Net Framework 4.5 (or higher)
    • For 93.X versions: SAP Business One 9.3. Requires both 32-bit and 64-bit versions of:
      • B1 Client
      • Hana Studio Client (Hana Only)
      • DI-API
    • For 100.X versions: SAP Business One 10:
      • B1 Client
      • Hana Studio Client (Hana Only)
      • DI-API
      • Legacy DI-API
    • ODBC Hana drivers installed (Hana Only).
  • Dedicated SaaS Web Server Requirements
    Hardware Minimums

    Below are the minimum requirements for a Dedicated Software as a Service (SaaS) web server. Consider improved server specs if high volumes of web traffic or large numbers of B1 users are involved.

    • 4 GB RAM or higher.
    • 2GHz Dual Core processor or better.
    • 100 GB hard drive or higher.
    • 100 Mb Network or better.
    Software
    • Windows Server Enterprise, Standard or Web Edition. See Release Notes for supported versions. Ensure all stable security patches have been applied.
    • IIS including IIS 6 Compatibility Modules (See: How to Configure IIS)
    • .Net Framework 4.5 (or higher).
    • The SaaS web server must have access to the B1WebAPI instance.
    • SSL Certificate is required per domain.
  • Shared SaaS Web Server

    Shared SaaS hosted web servers are available to Portal installations under certain conditions.

    Contact Sales to see if Shared SaaS Web Hosting is the right fit for your Portal installation.

  • Firewall
    Hardware

    Network usage minimums are below. Consider improved bandwidth if high volumes of web traffic are involved.

    • 1.5 Mb down
    • 1 Mb up
    Software
    • Network Address Translation
    • Able to alert and report an outage
    • Capable of creating DMZ
  • Database Server Requirements
    Hardware/Software

    Speak with your SAP Business One consultant.

  • End User (Customer)
    Hardware

    A typical home computer, at minimum:

    • 512 MB RAM
    • 100Mb Network
    • 5GB hard drive space available
    • 1GHz processor
    Software

    A standard web browser, such as:

    • Google Chrome
    • Microsoft Edge
    • Internet Explorer (11 or higher)
    • Mozilla Firefox
    • Apple Safari

Infrastructure Cheat Sheets

Common configurations are summarized below. Refer to details above for specific versions.

Server Cheat Sheet

(See version details noted above)

Customer Portal Employee Portal Vendor Portal Interconnect SPS Cloud EDI
Database Server
(SQL - Windows)
(Hana - Linux)
required required required required required
Application Server
(Windows)
required required required required required
SaaS Web Server*
(Windows)
required required required not-required not-required
  • *Web Server must be distinct from the Application/Product DB server and is provided on a Software as a Service (SaaS) basis. Contact sales to see if you require a Dedicated SaaS or Shared SaaS web server for your application.

Component Cheat Sheet

(See version details noted above)

App Server SaaS Web Server
(if applicable)
SQL Server required not-required
.Net required required
IIS with IIS6 Compatibility Modules required required
SSL Certificate
(per domain)
not-required required
DI-API - 32-bit
(B1 9.3 and lower)
required not-required
DI-API - 64-bit required not-required
Legacy DI-API
(B1 10 only)
required not-required
B1 Client required not-required
SQL Management Studio Client required not-required
Hana Studio Client
(Hana Only)
required not-required
ODBC Hana Drivers
(Hana Only)
required not-required

Download the Latest Version

https://productdocs.vision33.com/downloads/ contains the latest download packages.

To download installation files, a username and password are required. Contact support (support@vision33.com) for access.

The latest version of the Portal installation package is displayed in the top section and is labelled Portal installation files for the appropriate version of SAP Business One. To download the installation files, click on the link and enter the username/password information when prompted.

Upgrades

Components for each Portal

Customer Portal

Required Components:

  • B1WebAPI
  • InterConnect Server Tools
  • InterConnect Manager Add-On
  • Customer Portal website

Employee Portal

Required Components:

  • B1WebAPI
  • InterConnect Server Tools
  • InterConnect Manager Add-On
  • Employee Portal website

Vendor Portal

Required Components:

  • B1WebAPI
  • InterConnect Server Tools
  • InterConnect Manager Add-On
  • Vendor Portal website

Interconnect

Required Components:

  • B1WebAPI
  • InterConnect Server Tools
  • InterConnect Manager Add-On
  • Workflow Portal

Component Upgrade Chart

The following upgrade chart shows which components need to be upgraded between versions. All components require an upgrade when upgrading from version 93.0 or lower.

Portal Upgrade Version Chart - Required   - Recommended   - None
100.3100.2100.1100.093.993.893.793.693.493.393.2
B1WebAPINo upgrade requiredNo upgrade requiredNo upgrade requiredUpgrade Required Upgrade RecommendedUpgrade RequiredNo upgrade requiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade Required
B1WebAPI Version100.0100.0100.0100.093.1093.693.693.693.593.493.3
InterConnect Server ToolsNo upgrade requiredNo upgrade requiredNo upgrade requiredUpgrade RequiredNo upgrade requiredNo upgrade requiredNo upgrade required Upgrade RecommendedNo upgrade requiredNo upgrade requiredUpgrade Required
InterConnect Server Tools (Meta-data only)Upgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade Required
InterConnect Manager Add-OnUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade Required Upgrade RecommendedUpgrade Required
Customer Portal Upgrade Recommended Upgrade Recommended Upgrade RecommendedUpgrade RequiredUpgrade RequiredUpgrade Required Upgrade RecommendedUpgrade Required Upgrade Recommended Upgrade RecommendedUpgrade Required
Employee Portal Upgrade Recommended Upgrade Recommended Upgrade Recommended Upgrade Recommended Upgrade Recommended Upgrade RecommendedUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade RequiredUpgrade Required
Vendor Portal Upgrade Recommended Upgrade Recommended Upgrade Recommended Upgrade Recommended Upgrade Recommended Upgrade Recommended Upgrade RecommendedUpgrade Required Upgrade Recommended Upgrade RecommendedUpgrade Required
Workflow PortalNo upgrade requiredNo upgrade requiredNo upgrade requiredNo upgrade requiredNo upgrade requiredNo upgrade requiredNo upgrade requiredNo upgrade requiredNo upgrade requiredNo upgrade requiredUpgrade Required

Upgrading B1WebAPI (All Products)

Not every version requires an upgrade of B1WebAPI. Review the upgrade chart above to determine if this is required for your upgrade.

Before upgrading B1WebAPI, make a backup of any customizations. Also, make a backup of the configuration file, typically C:/Program Files (x86)/zedIT/zed B1WebAPI/bin/b1enabler.config.

To safely back up these files, save them into another folder (such as C:/backups/) so they are not deleted or overwritten by the installer during the upgrade.

Confirm data migration tasks before beginning an upgrade. Certain versions require special data handling. Speak with your SAP Business One consultant for more details.

B1WebAPI version 93.6 and higher

B1WebAPI 93.6 introduces breaking changes during an upgrade. As a result, there are a few options that can impact which approach will apply to a particular scenario.

Upgrade scenarios:

  • Scenario 1: A single version of a Portal is connecting to the Application server (i.e. All versions are being upgraded at once). An example of this is when test companies are on a different server, and all versions within a server are ready for upgrade).
  • Scenario 2: Multiple versions of a Portal are connecting to the same Application server (e.g. Test is on an upgraded version, while Prod continues running on the old version).
Scenario 1: A single Portal version is connecting to an Application server

This applies to upgrade scenarios where all companies on a server are upgraded at once, such as when two separate servers are in place for Test versus Production.

In this scenario, normal B1WebAPI upgrade steps listed above apply (performing backups, data migration tasks, etc.).

Scenario 2: Multiple Portal versions connecting to the same Application server

This applies to upgrade scenarios where Test and Production systems are hosted on the same server, and Test is upgraded first, while Production remains in place on an older version.

Recommended approach: B1WebAPI 93.6 (or higher) may be installed side-by-side to support new Portal features. This will allow new functionality in the Portals to be fully supported, while maintaining an older system.

The limitations of this approach are:

  • Older versions of the Portals (versions lower than 93.6) cannot use this B1WebAPI, and should continue to use the existing version of B1WebAPI until they are upgraded.

If taking this approach make the following changes to installation steps:

  • reject “uninstall old version” when prompted during the newer B1WebAPI installation.
  • Install the new B1WebAPI in a non-standard file location, such as C:\Program Files (x86)\zedIT\zed B1WebAPI 93.6\ or C:\Program Files (x86)\zedIT\zed B1WebAPI Alt\
  • Install the new B1WebAPI on a non-standard port, such as 4032. Ensure that this port is accessible by the Portals. Additional firewall settings may need to be configured to do this.

Alternative approach: B1WebAPI may remain as-is, and a version 93.6 Portal may be configured for backward-compatibility mode (i.e. “A new portal but old B1WebAPI”).

The limitations to this approach are:

  1. The old version of B1WebAPI must be 93.0 or higher. If B1WebAPI is lower than 93.0, then a “side-by-side” installation (two versions of B1WebAPI on one system) is required.
  2. New Account/Password functionality cannot be used in the 93.6 Portal using an older version of B1WebAPI.

If taking this approach, update the Portal’s web.config file as follows:

In the b1Clientenabler tag, set the property useLegacyLogin="true". By default, when using the latest B1WebAPI and Portal, this flag is set to false.

Example:

   <b1ClientEnabler
    enablerHost="http://192.168.1.23:4033/TEST_PROFILE"
    enablerDomain=""
    enablerUserName="b1webapi"
    enablerPassword="mySecurePassword"
    changePasswordPageURI="~/ChangePassword.aspx"
    loginPageURI="~/login/Login.aspx"
    defaultPageURI=""
    useLegacyLogin="true" />

Upgrading InterConnect Server Tools (All Products)

Only select versions require an upgrade of InterConnect Server Tools. Otherwise, there are no special instructions for upgrading this component.

Review the upgrade chart above to determine if this is required for your upgrade.

Upgrading InterConnect Manager Add-On (All Products)

InterConnect Manager Add-On must be upgraded between service pack versions, but not necessarily for patch releases. For example, if upgrading from version 93.8 to 93.9, the Add-On must be upgraded, but when upgrading from version 93.8.0 to 93.8.1 this is not required.

Before upgrading InterConnect Manager Add-On, backup any custom configuration settings, such as payment settings, welcome messages, menus, etc. To do this, open each config screen found under InterConnect Manager AddOn > Administration, and take a screenshot or copy/paste any field that is too long for a screenshot. Save this information in case updates to the add-on overwrite this.

Specifically, upgrading from version 5 or 6 to version 7+ will delete Payment Gateway configuration and Order Pad configuration. Pay extra attention to payment gateway settings before performing an upgrade from versions 5 or 6.

Menus have changed as of Service Pack 2 for B1 9.2 (version 92.2). When prompted to update menus, this will adjust the layout but may require some custom menu entries to be manually added back to the menu. Review after an upgrade to ensure menus are displaying as expected.

Upgrading Customer Portal Website

  • Back up InterConnect Manager Add-On settings. Be sure to perform backups of any Customer Portal settings found in InterConnect Manager Add-On for SAP Business One.

    Specifically, Payment Options must be backed up when upgrading from version 7 or lower. Payment settings contain breaking changes in version 7, which requires a complete re-configuration of this setting.

  • Back up custom web files. Any file found outside of the Customer Portal folder /customs/ may be deleted during a website upgrade. If customizations are found outside of that folder, copy customized files into another location to back them up.
  • Merge customizations over a new installation. When upgrading web files, recommended best practice is to install the standard Customer Portal web files in a new location, then merge in custom/updated files from the old version. This avoids certain odd behavior due to caching and deprecated files. These types of display issues may be resolved manually if they occur on a system that was upgraded instead of merged.
  • Identify multi-language upgrade tasks. Multi-language support has changed. If you are upgrading a version of Customer Portal that already includes multi-language support, please contact your SAP Business One consultant to ensure this is migrated to the new multi-language format.
  • Identify if Quote functionality is enabled. When upgrading to version 93.6 or higher, a new role (Quote) has been added to accommodate Quote-only access when both Quote and Order functionality is enabled.

    To enable backward-compatibility (i.e. to ensure that users with the Order role can access both Orders and Quotes), ensure that the web.config property OPRoleBackwardCompabilityEnabled is enabled (see Advanced Web.Config Options for a walkthrough).

    Alternatively, ensure that all customers who need Quote access are assigned the new role Quote. This will ensure that backward-compatibility mode is not needed going forward.

  • When upgrading to Customer Portal 93.6 or higher, if B1WebAPI is version 93.0 through 93.4, this will require backward-compatibility mode (B1WebAPI 92.7 and lower are not compatible). This will disable all Password Security enhancements in version 93.6. To enable backward-compatibility mode, update the Portal’s web.config file as follows:

    In the b1Clientenabler tag, set the property useLegacyLogin="true". By default, when using the latest B1WebAPI and Portal, this flag is set to false.

    Example:

     <b1ClientEnabler
      enablerHost="http://192.168.1.23:4033/TEST_PROFILE"
      enablerDomain=""
      enablerUserName="b1webapi"
      enablerPassword="mySecurePassword"
      changePasswordPageURI="~/ChangePassword.aspx"
      loginPageURI="~/login/Login.aspx"
      defaultPageURI=""
      useLegacyLogin="true" />
    

Upgrading Employee Portal Website

  • Back up InterConnect Manager Add-On settings. Be sure to perform backups of any Employee Portal settings found in InterConnect Manager Add-On for SAP Business One. Note that as of version 92.5, settings have changed considerably.
  • Back up custom web files. Any file found outside of the Employee Portal /customs/ folder may be deleted during a website upgrade. If customizations are found outside of that folder, copy customized files into another location to back them up.
  • Merge customizations over a new installation. When upgrading web files, recommended best practice is to install the standard Employee Portal web files in a new location, then merge in custom/updated files from the old version. This avoids certain odd behavior due to caching and deprecated files. These types of display issues may be resolved manually if they occur on a system that was upgraded instead of merged.

    Also ensure to copy any signature image files found in the website’s /signatures/ folder. This will ensure web users can continue to view older signature capture.

  • When upgrading to Employee Portal 93.6 or higher, if B1WebAPI is version 93.0 through 93.4, this will require backward-compatibility mode (B1WebAPI 92.7 and lower are not compatible). This will disable all Password Security enhancements in version 93.6. To enable backward-compatibility mode, update the Portal’s web.config file as follows:

    In the b1Clientenabler tag, set the property useLegacyLogin="true". By default, when using the latest B1WebAPI and Portal, this flag is set to false.

    Example:

     <b1ClientEnabler
      enablerHost="http://192.168.1.23:4033/TEST_PROFILE"
      enablerDomain=""
      enablerUserName="b1webapi"
      enablerPassword="mySecurePassword"
      changePasswordPageURI="~/ChangePassword.aspx"
      loginPageURI="~/login/Login.aspx"
      defaultPageURI=""
      useLegacyLogin="true" />
    

    Sales User Upgrades for versions 91.2 and lower

An upgrade from a version prior to 91.2 (SP2 for B1 9.1) will require special attention related to Sales User. These steps must be completed whether or not Sales User was active prior to the upgrade.

The following steps must be completed whenever an upgrade is applied.

If upgrade of Employee Portal was completed in-place (as opposed to a side-by-side install with file merging), ensure that the old Sales User folder salesuser is deleted. This will ensure these deleted files do not conflict with new sales user.

After base Employee Portal has been upgraded, perform the following tasks:

Sales User Upgrade pre-91.2 - Modify Menus

This will remove deprecated menu entries and update other entries for the newer Portal version.

  1. Remove the following menu entries completely. To do this, in B1, go to InterConnect Manager AddOn > Manage My Menus > Employee Portal. These menu entries are no longer valid:
    • Sales User/Sales Pipeline (deprecated)
    • Sales User/Activities in the last 30 days (deprecated)
    • Sales User/Sales Order Analysis (this report is a duplicate of Sales Reports - Order Analysis)
  2. Update the “My Opportunities” menu entry to point to /salesuser/board instead of the old opportunities screen. See screenshot below.

    Update the My Opportunities link to point to the new opportunity board, as shown.
    Update the My Opportunities link to point to the new opportunity board, as shown.
  3. Update any custom report links and golden arrow drill-downs which point to old Sales User links. For example, customer detail drill-downs on a customized customer report will need to point to the new sales user customer details page.
Sales User Upgrade pre-91.2 - Assess the need for customizations

After an upgrade to the latest version, new Sales User features may be available out-of-the-box that once required customization. Assess the new Sales User features to see if further customization is required. In this case, you may create new customizations.

Note that the old sales user and its customizations may be activated, however this will not be supported via the normal product support. Speak with your InterConnect implementation consultant if this is your preferred option.

Dashboard Upgrades

As of version 93.2 Dashboard improvements have been installed out-of-the-box. However, for upgrades from versions below 93.2 to a higher version, a special metadata import is required.

When upgrading from a version prior to 93.2, to version 93.2, 93.3 or 93.4, ensure that all customized core dashboard queries are backed up prior to upgrade. These are found in the InterConnect Server Tools metadata backups folder (for Dashboard queries, this is typically: C:/Program Files (x86)/zedIT/zed Server Tools/MetaData/ZEDSUITE/ in an sub-folder).

When upgrading from a version prior to 93.2 to version 93.6 or higher, if skipping versions 93.2, 93.3 and 93.4, no new dashboard changes will be loaded automatically. In this case, a special dashboard pack must be loaded using the MetaData import feature of InterConnect Server Tools. Ensure the Overwrite option is enabled to ensure the new Dashboard metadata overwrites any previous system defaults.

To upgrade to version 93.6 or higher:

  1. Run Server Tools in Administrator mode.

  2. Open the MetaData screen.

  3. Load the Dashboard meta-data pack, found in the Server Tools folder /MetaData/PACKS/DB_UPGRADE/, typically found in the folder C:/Program Files (x86)/zedIT/zed Server Tools/MetaData/PACKS/DB_UPGRADE/. If this folder does not exist, verify versions before proceeding.

  4. Ensure the Overwrite queries check-box is checked.

  5. Import the Dashboard metadata and review the System Messages provided. This may take a few minutes on Hana.

Upgrading Vendor Portal Website

  • Back up InterConnect Manager Add-On Settings. Prior to upgrade, perform backups of any Vendor Portal settings found in InterConnect Manager Add-On for SAP Business One.

  • Back up custom web files. Any file found outside of the Vendor Portal /customs/ folder may be deleted during a website upgrade. If customizations are found outside of that folder, copy customized files into another location to back them up.

  • Merge customizations over a new installation. When upgrading web files, recommended best practice is to install the standard Vendor Portal web files in a new location, then merge in custom/updated files from the old version. This avoids certain odd behavior due to caching and deprecated files. These types of display issues may be resolved manually if they occur on a system that was upgraded instead of merged.

  • When upgrading to Vendor Portal 93.6 or higher, if B1WebAPI is version 93.0 through 93.4, this will require backward-compatibility mode (B1WebAPI 92.7 and lower are not compatible). This will disable all Password Security enhancements in version 93.6. To enable backward-compatibility mode, update the Portal’s web.config file as follows:

    In the b1Clientenabler tag, set the property useLegacyLogin="true". By default, when using the latest B1WebAPI and Portal, this flag is set to false.

    Example:

     <b1ClientEnabler
      enablerHost="http://192.168.1.23:4033/TEST_PROFILE"
      enablerDomain=""
      enablerUserName="b1webapi"
      enablerPassword="mySecurePassword"
      changePasswordPageURI="~/ChangePassword.aspx"
      loginPageURI="~/login/Login.aspx"
      defaultPageURI=""
      useLegacyLogin="true" />
    

Upgrading Interconnect workflows

Interconnect projects are fully customized and require extra attention to avoid loss of functionality and settings during an upgrade. Speak with your InterConnect implementation consultant before performing an upgrade.

When upgrading from version 93.0 or lower, the following manual updates must be applied prior to upgrade:

  • Remove Workflow message hooks from the SBO_SP_TransactionNotification stored procedure. Prior to upgrade, all Workflow message hooks must be removed from the SBO_SP_TransactionNotification stored procedure and inserted in the SBO_SP_PostTransactionNotice stored procedure.

  • Insert the Workflow message hooks in the SBO_SP_PostTransactionNotice stored procedure. The Workflow message hooks removed from SBO_SP_TransactionNotification must be inserted into SBO_SP_PostTransactionNotice.

Relocating Workflow message hooks ensures that Workflow messages will be created after validation is completed.