B2B Metric dashboard

You can view the overall health of B2B for Oracle Integration transactions from the B2B dashboard page. This page provides an easy way to detect and manage failed messages in your environment.

See Monitor the Overall Health of B2B Transactions in Using B2B for Oracle Integration 3.

24.02

Positional flat file/native format support

B2B for Oracle Integration can consume positional flat or fixed length payloads (also called data files in native format) in inbound and outbound translations. These files can be of fixed length for various fields, CSV, delimited, and other formats. B2B for Oracle Integration enables you to define a B2B schema and document from these various formats and include the document in a trading partner agreement.

See Positional Flat or Fixed Length Payloads Support in Using B2B for Oracle Integration 3.

24.02

X12 HIPAA standard

B2B for Oracle Integration supports the X12 HIPAA standard to exchange documents over the internet. X12 HIPAA is a subset of the X12 standard and is used in the healthcare industry for the exchange of data about health insurance claims and payments.

See About X12 HIPAA in Using B2B for Oracle Integration 3.

24.02

With support for a dark theme, favicons can now be set independently for light and dark themes for each of your applications. You can set the favicon to any image in the image gallery by simply changing the favicon in the application's Settings editor. See Manage App Settings.

• Fragments as sections for dynamic containers

  It's now possible to add fragments as sections in a dynamic container. By default, all fragments tagged as pageContent become available for selection when you add a section to a dynamic container. You also have the option of indicating a particular fragment as preferred content for all sections in the container. See Add Fragments as Sections in a Dynamic Container.

• InstanceFactory types for fragments

  Types from code, known as InstanceFactory types, can now be defined in fragments, making these types accessible to fragments. As with all fragment artifacts, these types are local to the fragment. See Create a Type From Code.

• New properties for fragment slots

  The Fragment Slot component now provides several new properties to help you configure a named slot, including a Preferred Content option that indicates the type of content the slot can contain. See Add Slots to a Fragment.

• Drag and drop for fragment slots

  Fragment consumers can now drag and drop their component of choice onto a fragment slot in the fragment's Properties pane, in addition to the Insert Component option. See Add Slots to a Fragment.

• Improvements on customizing fragment variable display in the Properties pane

  • If your fragment variable uses an array of primitives (for example, string[]), you can now edit the fragment's JSON to display a drop-down menu showing all values for each item in the array. See Subtypes and valueOptions for arrays in Customize How a Fragment Variable is Displayed in the Properties Pane.

  • When an object-type input parameter in a fragment is customized to display an endpoint picker, fragment users can use the Configure Endpoint quick start to select a suitable endpoint and choose its URI parameters. See Customize How a Fragment Variable is Displayed in the Properties Pane.

  • When sectioning fragment properties, you can now use a Label field to provide a user-friendly name for the fragment variable. This is particularly useful for dynamic components with data that might take a while to display in the Page Designer. See Section Fragment Properties for Display in the Properties Pane.

• Navigator badge to indicate audit error

  Audit errors are now badged in the Navigator to indicate that action must be taken to resolve the issue. The badge persists until the error is fixed or until the session ends.

• New Copy to Clipboard option

  A new Copy to Clipboard option in the right-click menu allows you to copy one or all audit issues to your clipboard for further processing.

See Audit Application Code.

• Core Pack in Components palette

  The next generation of Oracle JET components, known as Core Pack components, are now available in the Components palette as part of the Early Access category. These components, written entirely using the VComponent API and the JET Virtual DOM architecture, are available as a completely new set of components, so you can use Core Pack and legacy components side by side in your application. Core Pack components provide improved rendering performance over legacy components. See Add Components to Pages.

• Page input parameters from parent flows

  When input parameters for a page are defined beyond its current scope (say, at the app or flow level), those parameters are now listed in the Page Input Parameters dialog, allowing you to readily pass the input parameter from parent flows and pages. See Enable Variables as Input Parameters.

• Live/Design toggle change

  To switch between Live and Design modes using the Ctrl key (Cmd on Mac), the cursor must now be on the canvas. This way, the mode won't switch when the canvas is not in focus. Releasing the key to switch the toggle back works anywhere. See Use the Page Designer.

• Event editor updates to improve developer productivity

  We've reworked how new action chains are generated when you create a listener for an event. Previously, you would use several clicks to create a new action chain at the desired scope with a particular name in the Create Event Listener wizard. Now you simply click the Create {scope} Action Chain option to generate an action chain with a name in the format {event/varId}ChangeListener. See Create Event Listeners for Events.

• New behavior type for custom events

  The transform behavior type for custom events is deprecated and replaced by the new tranformPayload behavior type for new event listeners. The change does not impact existing apps with events configured to use the transform type, but the new tranformPayload type addresses issues with invoking event listeners in the correct order. You are, therefore, encouraged to switch to the new behavior type for your existing apps. See Choose How Custom Events Call Event Listeners.

• Actions tab renamed

  The Actions tab is now the Action Chains tab.

• New options for local functions

  You can now convert a local function to an action chain so it can be used by other action chains. Simply right-click the local function and select the new Convert Function to Chain option. It's also possible to create a local function from an action on the canvas. Just drag an action on the canvas onto the Create Function button, or onto the green line that appears before or after a local function. See Design Editor.

• Summary button to simplify action chain view

  You can now visually simplify your view of an action chain by hovering over the canvas's upper-left corner and clicking the Summary button. The Summary button hides the input parameter details of each action (except for the Assign Variable and Reset Variables actions). Click the Full button to switch back to the complete view. See Design Editor.

• Simplified display for action parameters

  We've simplified and enhanced how parameters display in different actions. Parameters displayed in actions such as Open URL, Call REST, and Fire Data Provider Event are now grouped. Also, the Store Result In variable has been added to the header to make it more readable.

• Changes to the Assign Variable action

  • The Assign Variable action can now be used to create a local variable, by adding the action and using the Properties pane to define it.

  • Consecutive Assign Variable actions are now consolidated into a single action.

  See Add an Assign Variable Action.

• Support to drag and drop an action into an else branch

  You can now drag and drop an action into an else branch on the canvas.

• UI changes for business objects based on your own schema

  When working with business objects that use your own schema, you'll notice some UI changes, primarily when adding or editing a business object's fields. See Create a Business Object Based on a DB Table or View and Add Fields to a Business Object Based on a DB Table or View.

• Improved error handling for business object diagrams

  When business objects and their relationships don't display on the Diagram canvas because of syntax errors, the editor now displays an error message and allows you to edit the JSON source file (diagram.json) to fix the error.

Oracle Cloud Infrastructure Process Automation, a service that quickly automates business approval workflows, can now be integrated in Visual Builder. To leverage this functionality in your application, create an OCI Process Automation backend, then create service connections for the REST APIs you want to use. See Connect to Oracle Cloud Infrastructure Process Automation APIs.