What’s new in Nov 2022

These release notes identify the new features and bug fixes released
in AtomSphere for November 2022.

Subject to the terms and conditions of our existing contract with your firm, and
liability provisions and limits therein, we confirm that Boomi has successfully
passed all applicable test cases associated with the updates identified in this
product release.

Release notes for the 12 months preceding the current release are archived.

AtomSphere platform
Home page

Feature:
 The redesigned AtomSphere platform home page showcases our full line of
services and provides a place where you can discover pre-built solutions to
help you get a jump-start on moving data quickly. The new home page is
built on a framework that provides a sleeker and more modern user
experience and enables faster iteration and time-to-value. The page is also
implemented with localization support —Spanish and Japanese, to start—
allowing for greater global accessibility. (UU-24)

Single Sign-on

Fix:
 When a Unicode or UTF-8 character was in the Attribute Value(s) of a SAML
response, the Single Sign-on authentication would fail with a Forbidden:
Invalid SSO request error. With this fix, Unicode and UTF-8 characters no
longer cause SSO authentication to fail. (ADSEC-903)
Atoms, Molecules, and Atom Clouds
Atom management

Feature:
 When the Account Concurrent Execution Limit (ACEL) quota and the Cloud
Partition Size property are set, the Cloud nodes are partitioned and an
attachment is restricted to only a subset of the nodes. Each node then has
a limit for the number of executions it can concurrently allow for the
attachment. When an execution is prevented from executing on a node due
to the ACEL quota, the execution is retried on the other nodes in the subset
instead of failing immediately. (RUN-4254)

To learn more about this feature, see the topics Attachment quotas

tab, Account Cloud Attachment Properties object, Properties panel,
Advanced tab.

 You can use the property Set Local Working Directory in the Properties
panel's Advanced tab to set a local working directory to which plugins and
core container JARs are copied to each node in a cluster when they are
downloaded or updated. (RUN-2430, RUN-2429)

To learn more about this feature, see the topic Properties panel,

Advanced tab.

Fixes:
 Previously, the Linux file system would replace Unicode characters in
container names with underscores. With this fix, the Unicode characters
display as expected in the container name. (RUN-4045)

Note: This fix was removed as part of RUN-4562, which releases Atom

installer version 22.11.2.
 When a container with Unicode characters in the name was installed on
Windows, it failed to come online due to the Unicode characters converting
to invalid characters. With this fix, Unicode characters display as expected
on Windows and the container starts up normally. (RUN-4049)

 When existing environment names contained Unicode characters, new

Atoms, Molecules, and Atom Clouds were unable to be installed and the
 environment list would not load. With this fix, containers with Unicode
characters in the name can be installed and environment lists load
propertly. (RUN-4142)

 Previously, if you included a backslash (\) in the name of a new container,

you were able to proceed through the installation process before being
stopped at the install directory step. With this fix, you cannot proceed past
setting the name for a container if there is a backslash in the name. (RUN-
4340)

 After the November 2022 AtomSphere Release, Atoms, Molecules, and

Atom Clouds that have a hyphen (-) in the name would fail to install when
the Docker version of the installer was used. Atom installer version 22.11.2
resolves this issue. (RUN-4562)
 To improve performance of the shared file system when handling process
and document logs, you can add the following properties to the Properties
panel's Custom tab:
o com.boomi.container.enableFlushingProcessLogImmediately -
Determines whether to flush the log after every log record is
published or rely on the default Java flushing behavior, which flushes
after the logger is closed. The default value is true, which flushes the
log immediately.
o com.boomi.container.processLogBufferSize - Defines the size of the
process log buffer in bytes. The default size is 8192 bytes.
(RUN-1748)

 In some cases, when an Atom worker was starting up, an error would
display when replacing stale workers due to the maintenance thread
running before the worker was launched. With this fix, the error no longer
displays and the Atom worker starts up as expected. (RUN-4255)

Custom scripts

Feature:
If you use custom script files for Molecules or Atom Clouds, you must make the
following changes:

For procbrowser.sh and procworker.sh:
 Add _hostaddr=$5 below the declaration for _hostid=$4
 Update -Dcom.boomi.container.userLibDirs to -
Dcom.boomi.container.userLibDirs=${BOOMI_ACCOUNT_USER_LIB_DIR}:$
{BOOMI_USERLIB_DIRS}
  Add "${_hostaddr}" to the end of the command, after "${_workerid}" "$
{_accountid}" "${_hostid}"
For procrunner.sh:
 Add _hostaddr=$4 below the declaration for _hostid=$3
 Update -Dcom.boomi.container.userLibDirs to -
Dcom.boomi.container.userLibDirs=${BOOMI_ACCOUNT_USER_LIB_DIR}:$
{BOOMI_USERLIB_DIRS}
 Add "${_hostaddr}" to the end of the command, after "${_execid}" "$
{_accountid}" "${_hostid}"

Note: Using the Forked Execution Properties options in Atom Management

eliminates the need to maintain custom script files.
(RUN-4305)

To learn more about this feature, see the topic Customizing Molecule or Atom
Cloud script files.

Boomi Integration
Process building

Features:
 The Test dialog now includes a progress bar that shows your progress
results when executing large processes. (INT-4369)

 Enhancements to the Start tab include improvements to

the Recents table's search bar, adding extra filters for better search results,
and a new drop-down menu that gives you the option to view Processes
Only or All Components. (INT-5704, INT-5705)
To learn more about this feature, see topic Creating a process from the
Start tab

 This feature adds extra keywords to the functionality of the component

search and the shapes search in the Create New tab, enabling you to
search for components and shapes more effectively. (INT-572, INT-5726)
 An enhancement to the Recents table introduces keyboard functionalities
that make it possible for you to use your arrow and tab keys to move
across the page and use the enter key to confirm a selection. (INT-5894)
To learn more about this feature, see topic Creating a process from the
Start tab
Fixes:
  The August 2022 release introduced an issue that caused the source profile
to be overwritten by the destination profile when the same flat file profile
was used in the extensions, resulting in the destination showing on both
sides. With this fix, the destination no longer overwrites the source profile
and you can add extension elements that appear only on their
corresponding side. (INT-5761)

 The October 2022 release introduced an issue that prevented

the Arrange function from working with unsaved processes. This fix allows
you to arrange unsaved processes. (INT-5916)

AtomSphere API and Partner API

Account User Federation object

Fix:
 If the federationID field was left blank or omitted from the Create operation,
an unspecified fault message would display and a null pointer exception
would be recorded. With this fix, the Create operation completes
successfully if the federationID field is left blank or is omitted. (ADSEC-1798)

Component Metadata object

Fix
 A Query request specifying a component type filter resulted in an error if
the type filter parameter name was specified with one or more uppercase
letters. With this fix, the type filter parameter name is not case-sensitive.
(INT-4865)
Deployment object (Legacy deployment, Deprecated)

Fix
 The Create operation created a packaged component for each of the
requesting account’s environments. With this fix, the Create operation
creates a single packaged component, which is then deployed to each of
the requesting account’s environments. (INT-4992)

Deployed Package object

Fix
 The DeployedPackage - Delete API operation, which is used to undeploy a
package, did not update the license count. With this fix, the Delete
operation updates the used and available license counts for the requesting
account. (INT-3613)
Connectivity
Agiloft CRM connector

The Agiloft CRM connector is renamed "Agiloft CRM - Partner connector". You
can continue to use this connector as normal; its functionality is unchanged.
(CON-6675)

Connector Shapes dialog

Feature:
 Connector shapes with links and short descriptions will also show links and
short descriptions on the Connector Shapes dialog after a connector has
been selected. (CON-6270)

Disk v2 connector

Features:
 Added file name filtering support on the Listen operation using the text
box File Name Filter and the drop-down File Matching Type. (CON-6357)
 Added a mode Singleton Listener for the Listen operation. This value is
unchecked by default. (CON-6359)
To learn more about this feature, see the topic Disk v2 connector.

Google Ad Manager API connector

Feature:
 The Google Ad Manager API connector currently uses outdated API
v202108. With this fix, the connector has been updated to use v202208 as
the default for new connections as API v202108 is no longer supported.
(CON-6693).
To learn more about this feature, see the topic Google Ad Manager
connector.
JMS v2 connector

Deferred: Subsequent to the November 2022 Runtime Release, this connector

was postponed and released off-cycle.
Features:

 Added two server types, ActiveMQ Artemis and ActiveMQ Classic,

supported by the operations Get, Send, and Listen. ActiveMQ Classic is
only available in JMS v1.1. (CON-6274)
 Added server type OracleAQ, supported by the operations Get, Send, and
Listen. This server type is only available in JMS v1.1. (CON-3986)
 Added server type OracleAQ (WebLogic), supported by the operations Get,
Send, and Listen. (CON-6175)
 Added server type SonicMQ, supported by the operations Get, Send, and
Listen. This server type is only available in JMS v1.1. (CON-6275)
 Added the field Time to Live and the tracked property Expiration time.
Inputs to both Time to Live and Expiration time are in milliseconds.
Messages will not expire when an input of zero is provided to Time to Live.
(CON-2760)
 Added support for generic services in JMS v2.0. (CON-3225)

 Added support for generic services in JMS v1.1. (CON-3473)

To learn more about this feature, see the topic JMS v2 connector.

Kafka connector

Features:

 Added a mode Singleton Listener for the Listen operation. This value is

unchecked by default. (CON-6636)
 Added support for reading messages from specific partitions by adding the
option field Manually assign partitions and the conditional field Partition
IDs to the Consume and Listen operations. The field Manually assign
partitions is unchecked by default. The input to Partition IDs must be
zero or a positive integer, and the field will only appear when Manually
assign partitions is selected. (CON-6251)
To learn more about this feature, see the topic Kafka connector.
Salesforce connector

Fix:

 Resolved an issue where empty document batches passed into the

connector returned IndexOutOfBoundsException when attempting to fetch
 off an EmptyReadStore. With this fix, when an empty document batch is
received, no Send operations are performed. (CON-6750)

Connectivity development
There are no connectivity development features or fixes in the November 2022
release.

Master Data Hub

Stewardship

Fix:

 The state of a referenced golden record changed to Unresolved when

changing the source type in a domain from Contribute to Contribute and
Accept or vice versa. With this fix, if a source type change continues to
contribute data, the referenced golden record's state remains Resolved.
(HUB-2012)
 Switching between Active and Resolved views in Quarantine caused
the Filter Operator to reset to its saved default. With this fix, switching
views does not affect the Filter Operator. (HUB-2083)
Reporting

Fix:

 Clicking the Resend button to request an update for a single record sent an

update request for all records. With this fix, the Resend button only sends
update requests for selected records on the Outbound Activity page. (HUB-
2276)

B2B/EDI Management
AS2 connector

Feature:

 The Apache POI version for AS2 Connectors is updated to reduce security
vulnerabilities. (B2B-2450)
 To learn more about this feature, see the topic AS2 Client connector.
EDI standards

Feature:

 New ODETTE message types are available to import into ODETTE EDI
profiles from the Document Types > Select Transmission page.
Additionally, the names of the message types that were added in the
August 2022 release are updated. (B2B-2295, B2B-2296)
To learn more about this feature, see the topic EDI profile's Options tab.
RosettaNet attachments

Feature:

 RosettaNet attachments are supported for Trading Partners. In

the Message Options section, you can configure a Document Cache
Component by using the Attachment Cache Configuration option to
support attachments for RosettaNet version 2.0. Configuring RosettaNet
attachments allows for inbound and outbound data flow to and from
Trading Partners. (B2B-2447, B2B-2448, B2B-2449)
To learn more about this feature, see the topics ROSETTANET messages
with attached documents, Trading Partner ROSETTANET Standard tab,
and Document Cache components.
Fix:

 Previously, when the dynamic document property was missing for the
content type of a RosettaNet attachment file, the resulting error lacked
information describing the source of the error. With this fix, the error
message indicates that the MIME type is missing in the dynamic document
property. (B2B-2513)

Trading Partner management

Feature:

 You can set the following Connection properties as extensions for the
MLLP-Trading Partner and MLLP Client connector:
o Send Timeout
o Receive Timeout
o Max Retry
o Fail on Timeout
(B2B-2455)
 To learn more about this feature, see the topics MLLP Client
connection and MLLP Communication Method configuration.
 The AS2 Multiple Attachments and Maximum Document Count fields are
now extensible to Trading Partners and Shared Communication Channels.
(B2B-2314, B2B-2358, B2B-2505)

To learn more about this feature, see the topics AS2 Client

Operation and AS2 Communication Method configuration.
Fixes:

 Previously, you could add the same document type to an ODETTE Trading
Partner multiple times. With this fix, if a document type already exists in the
document type table, it is removed from the Transmission dropdown
menu when you add a new document type. (B2B-2311)
 The Loop Repeat and Segment Max Use values were previously incorrect
for the Edifact templates versions D11B - D20A. This fix corrects the values.
(B2B-2457)

API Management
API Gateways and Authentication

Fix:
 The platform was attempting to generate a Swagger template for an API
Proxy after its authentication method was updated. With this fix, a Swagger
template isn't generated for API Proxies and the error message is improved
in Swagger generation. (APIM-5948)

Process Building

Feature:

 The speed and ease of creating APIs is now accelerated with the ability to
create APIs from an existing process. The Create API option allows you to
create an API from a process that contains a Web Services Server
connector. (APIM-5675)
To learn more about this feature, see the topic Creating an API from a
Process.

Deployed APIs

Fix:
  Updated the text on the API Management Getting Started screen for users
with the APIM account feature but without sufficient privileges that directs
them to contact their administrator for access. (APIM-5768)

GraphQL APIs

Features:

 Updated the Authentication Source API schema to make all authentication

sources available through the GraphQL query. (APIM-5659)

To learn more about this feature, see the topic Authentication Source

category.
 Added the deployedApiPlanDelete mutation to allow for plan deletion. (APIM-
5672)
To learn more about this feature, see the topic Deployed API plan
category.
 Added the deployedApiPlanCreateInput mutation to allow for plan creation.
(APIM-5862)
To learn more about this feature, see the topic Deployed API plan
category.

Boomi Flow
The following information identifies the new features and fixes in Boomi
Flow platform releases 2022-10-13, 2022-10-20.1, 2022-10-31, and 2022-11-03.

Connectors

Feature:
 The x-boomi-flow-user-access-token is sent with OpenAPI connector requests.
o Enable the Send Access Token to Connectors setting in an identity
provider to send the access token of the identity provider runtime
user in an OpenAPI connector request.
(FLOW-5911)

Fix:
 A “The response ended prematurely” error could sometimes occur when
editing and configuring a connector set up to use Client Certificate
authentication. With this fix, this error no longer occurs when configuring a
connector that uses Client Certificate authentication. (FLOW-5876)
Flow canvas

Features:
 Keyboard accessibility improvements are made to the flow canvas:
o aria-label text is added to canvas elements, providing screen reader
applications with accurate contextual information when using the
keyboard to move between elements on the canvas. (FLOW-5487)
o When an element is selected on the canvas, use the Menu key to
open the right-click context menu. (FLOW-4779)
 The "copy" text is no longer appended to the name of a map element that
has been copy-pasted onto the flow canvas. (FLOW-5729)

Fixes:
 An error could occur when grouping or ungrouping map elements on the
canvas, if the affected elements were moved before the changes were
saved to the canvas. With this fix, a loading spinner is shown after grouping
or ungrouping map elements, preventing interaction with the elements
before changes are saved. As part of this fix, grouping and ungrouping
performance and speed is also optimized. (FLOW-5809)

 If you selected a group and the elements within, and then moved them on
the canvas, the elements were removed from the group. Elements are now
no longer removed when moving a group. (FLOW-5913)

 The canvas right-click context menu could not be easily closed using the
keyboard, as you would need to tab back to the selected element first, to
then close the menu. With this fix, if you have opened the canvas context
menu, you can use the Menu key to close the context menu, and return
focus to the original element. (FLOW-5889)
 When selecting elements on the canvas using the keyboard, tabbing
behavior did not operate as expected with group and swimlane elements.
With this fix, tabbing between group and swimlane elements operates
correctly. (FLOW-5467)

 When using the keyboard to tab between canvas elements, you were able
to shift focus to off-screen elements, making it difficult to know what
element you were going to select. With this fix, the canvas automatically
pans as you tab between elements, with the current element in focus
always visible on-screen. (FLOW-5167)

 When working on the flow canvas, if you opened the Select a

Tenant screen and pasted text from your clipboard into the search field, an
error was shown, and any previously copied canvas map element pasted
 onto the canvas instead. With this fix, you can paste text into the search
field without error and without affecting the canvas. (FLOW-5886)
 You can copy and then paste groups on the canvas as expected. Previously,
only an empty group was pasted. (FLOW-5730)

Identity providers

Fixes:
 An error occurred when using SAML identity provider authentication in a
local runtime environment. After successfully authenticating with the
identity provider, an error was shown when returning to the flow. With this
fix, the error no longer occurs when returning to a flow after SAML identity
provider authentication. (FLOW-5898)

Map elements

Feature:
 Wait functionality is added to page map elements.

o Use this feature to set a period of time for a page to ‘wait’ before a
flow automatically continues along a specific outcome, as long as no
action is taken on the page during this period, such as selecting
another outcome.

For example, you could set up an approval process so that a page

proceeds automatically along an outcome if no approval action is
taken during the configured wait time, such as escalating to an
alternative approver.

o Select Add Wait in the Waits section of the page to add a wait to a

page map element. Define settings such as the wait type and
duration, and the outcome to trigger once the wait is complete.
o The wait starts when the page is shown in a flow, and will refresh and
proceed along the selected outcome unless a different outcome is
triggered first. The wait will start every time that the flow page is
visited, in case the same page map element is reused later in the
flow.

To learn more about this feature, see the topic Page map elements.
(FLOW-4201)
Signing in

Fix:
 If you signed in with a SAML single sign-on (SSO) user account, any changes
made to your user settings were not saved. With this fix, any changes you
make to your user settings are saved as expected when using a SAML SSO
user account. (FLOW-5834)

Table components

Fix:
 Interactive tables with a single outcome showed a chevron icon instead of a
button when viewed on smaller screen displays. This could cause issues if
the outcome triggered a deletion or removal, as users would not know that
they were performing a deletion/removal when tapping or clicking the
chevron icon. With this fix, tables with a single delete or remove outcome
show a button on smaller screen displays. Other types of outcome are
shown as a chevron icon in this scenario. (FLOW-5803)

User interface

Features:
 A Copy icon is added after ID text values, such as tenant, type, and value
IDs. This feature provides an easier, and more consistent way to copy
useful ID text values.
o Click the Copy icon to copy the ID to the clipboard.
(FLOW-5827)

 Value, type and type property IDs are added to

the Values and Types pages.
o On the Values page, the value ID is shown below the value name.
o On the Types page, the type ID is shown below the type name.
Additionally, the ID of each type property is shown in an ID column in
the Properties table.
(FLOW-5786)

Data Catalog and Preparation

Data Catalog and Preparation features and fixes are not in the Runtime Release.
To learn more about new features in Data Catalog and Preparation, read
the documentation
Adapters

Feature:
  The DCP Classic update supports Google Cloud Dataproc 2.0.x HDFS and
Hive adapters. (DCP-1342)

Data Set Explorer

Features:

 Previously, you could load demo data into Data Catalog and Preparation.
With this feature, demo data is available for Boomi Data Catalog. (DCP-
1640)
 You can add hyperlinks to the Description field for data stores, data
sources, data sets, jobs, workflows, schedules, and business glossaries.
Enter an HTML anchor tag in the Description field to display a hyperlink in
the object’s Details panel. Hyperlinks can provide access to web pages
related to an object. (DCP-1623)
 The Create MDH Data Model menu option in the Details panel lets you
create and publish data models and send them to Master Data Hub. This
feature is useful when you want to use a data set from your catalog as a
template for a data model.
When creating a model, you must define at least one matching rule to help
identify duplicate records. This feature does not currently support the
creation of models from hierarchical columns in a dataset. In addition to
having Master Data Hub, your catalog must have the AtomSphere adapter
installed and an AtomSphere data store and data source configured before
you can create data models. (DCP-1512)
Fix:

 Joining columns from two different Master Data Hub models resulted in an

error. With this fix, you can join columns from Master Data Hub models on
the Related Resources page. (DCP-1601)
Data Sources

Feature:

 The AtomSphere Username field is changed to AtomSphere User

Email and the AtomSphere Account field is changed to AtomSphere
Account ID. The new field names provide clarity when setting up an
AtomSphere data source. (DCP-1549)
Jobs

Fixes:
  Jobs targeting a database table failed when metadata sync was activated
and the source table did not contain metadata in the data dictionary. With
this fix, jobs without metadata are successful after activating metadata
sync. (DCP-1309)

 Prep jobs targeting Snowflake that required a role, database, or warehouse

property failed. With this fix, Data Catalog and Preparation applies
properties from Advanced Connection Properties when connecting to the
Snowflake database. (DCP-1536)
 Columns failed to automatically map when you selected UPSERT in
the Strategy drop-down after previously running a job targeting Snowflake
with the OVERWRITE strategy. With this fix, columns automatically map
when switching from OVERWRITE to UPSERT in the Strategy drop-down.
(DCP-1646)
Settings

Feature:

 Audit logs keep track of actions in your instance, including who performed
the action, when the action took place, and what objects were involved.
Audit logs help your organization demonstrate compliance with industry
and government regulations, such as GDPR, HIPAA, and FedRAMP.

Administrators can select one of the following log types in Manage > Audit

Logs to review events:
o Access
o Active Session
o Authentication
o Create Update Delete
o Endorsement
o Permission
You can export audit log event details as a CSV file using the DCP API’s audit
log export endpoint. (DCP-1515)

Workflows

Features:

 In Workflows, you can configure groups with the option to retry only failed
jobs. Retrying only failed jobs within a group can decrease the time needed
to rerun jobs if the scheduled workflow fails. This option is useful when
there are no downstream impacts from retrying only failed jobs. After a
schedule appears in Activities, you can select Retry to rerun only failed jobs
or Rerun to rerun the workflow from the beginning. (DCP-1358)