Table of contents
Find out what's coming up in the Administration, solution version 6.0 solution release, which includes the
, , and menu items.Release information
This document describes the TraceLink capabilities included in the Administration, solution version 6.0 solution release, which is available on Validation on 09 Jul 2024 and Production on 06 Aug 2024.
The following solutions are impacted by this release and will be updated to the version listed:
- Administration, solution version 6.0
Apps that support this solution version:
- Administration, version 2024.3
Patch releases
The following patches are released for this version:
- Administer, solution version 6.1.0 is available on Validation on 23 Jul 2024 and Production on 06 Aug 2024.
These patches are culumative, and the most recent patch release includes functionality from all previous versions.
Revisions
Date | Revision | Description |
---|---|---|
09 Jul 2024 | 01 | Initial version.
|
23 Jul 2024 | 02 | The following updates have been made since the previous revision was distributed:
|
UI features
The following new or updated functionality will be included in this release.
B2B integration configuration
System Administrators can now configure various settings in the Opus Web that enable network Owners and their Partners to exchange B2B messages using the Administration solution. System Administrators must create a B2B connection using AS2, SFTP, or SMTP protocols in the Extensible TraceLink Transfer Help Center app. Owners can also update, search and view the details of an exchanged B2B message in the Extensible TraceLink Transfer (XTT).
A B2B connection is a configured B2B gateway account associated with a company or location on the TraceLink network to enable file exchange with an external system (e.g. an ERP system owned by a company on the TraceLink network) using the protocol associated with the B2B connection. B2B connections are uniquely identified by a username, and also include the security information (e.g. certificates, public keys) required to establish a connection.
After creating a B2B connection the System Administrator can use the new B2B integration menu item in the Opus Administer UI to:
- Create an integration principal to enable communication between TraceLink apps.
- Create and enable transform set to send and receive different B2B messages.
- Associate a B2B connection with a company for outbound messages.
- Configure a B2B connection so that B2B messages can be sent inbound or outbound through the B2B gateway.
- Configure a B2B message connection type.
Create and Activate Integration Principals
Prior to enabling companies and Partners to exchange B2B messages, System Administrators must create or edit an to enable communication between TraceLink’s apps. The integration principal enables multiple users to send and receive B2B messages from one app to another without needing each individual user to be a member of both the sending and receiving apps.
The integration principal does not have login access to the UI.
Enable Transform Sets
System Administrators can create a , which is a collection of maps used to convert data from one format to another (e.g. CSV file to JSON file).. A company can have one or multiple transform sets and each set can have many B2B message types such as purchase orders, invoices, etc.
Once a transform set is created, it can be associated with a B2B connection, a company, or an internal location of the company. After a system administrator associates a transform set to a B2B connection, all the messages flowing from the specific B2B connection use this transform set. A company can have multiple B2B connections and use different transform sets for those connections. If a transform set is associated at the company level, all the messages being exchanged use the same transform set regardless of the location. If a transform set is associated at the location level, all the messages being exchanged from that internal location use the same transform set.
Associate B2B Connections
After associating a transform set with the B2B connection, the with a company for inbound or outbound messages.
A B2B connection for inbound or outbound messages can be associated with:
- An internal location.
- An app, which means that all messages received from that app will use this B2B connection.
- A B2B message type, which indicates that only a particular B2B message type will use this connection.
Configure B2B Connections
Configure inbound and outbound identifiers
After creating a B2B connection, System Administrators can configure a B2B connection in Administration so the appropriate Link Identifier, SAP Configuration, and EDI Configuration settings can be used for the app or network. Administrators can configure B2B connections for both and messages.
Configure B2B message connection type
System Administrators can add X12, Electronic Data Interchange for Administration, Commerce, and Transport (EDIFACT), and Intermediate Document (IDoc) to complete adding a B2B connection.
Impact analysis
- Interface options:
- UI
- Business segment impacts:
- All business segments for Owners.
Enhance user SSO settings
Manage User Session Timeouts and Password Settings
System Administrators can on the Sign-on Settings screen. System Administrators can:
- Lock an account after a specific number of failed login attempts, enable or disable lock settings for their company users, and specify the time in minutes after which an account is unlocked if auto lock is enabled (defaults to 5 minutes if the user does not change it).
- Set password expiration rules by indicating that a password never expires or by specifying a specific number of minutes after which a password expires for a user.
- Set password rules to allow users to reuse all previous passwords or not allow users to set a password to a specific number of previous passwords (defaults to 30 previous passwords before account is locked).
View Last Login and Password Expiration Rules
System Administrators can the Last Login and Password Expiration for a specific user on the All screen.
The Last Login date and time captured by TraceLink SSO.
This feature also includes updates to tabs on the
, , and menu items. System Administrators and Application Administrators can select in the side menu and then select:As part of this feature, the tab names on the
screen are updated to the following for clarity:- Previously the tabs in the Users in Opus Networks, Users in Classic Networks, and My Company Users. These tabs are now Networks, Apps, and All, respectively. were
The tab names on the
and screens are also updated for consistency:- Previously the tabs in the Opus Networks and Classic Networks. These tabs are now Networks and Apps, respectively. were
- Previously the tabs in the Opus Links , Classic Links, and Failed Links. These tabs are now Mutli-Network, Single-Network, and Failed, respectively. were
Reset Password Functionality
System Administrators can for a user on the All screen. After selecting , TraceLink sends the user an email to reset their password.
Users can reuse all previous passwords by default.
Impact analysis
- Interface options:
- UI
- Business segment impacts:
- All business segments for Owners.
Export Audit Trail Information in the Opus UI
Audit Trail Information in the Opus UI
System Administrators and Application Administrators must assign users the new Member - Standard Audit Trail Access to access the new menu item in the Opus Administer UI to investigate users and system actions for all TraceLink events. The audit trail provides easy insights into a company's operations and quick entry points to investigate specific events.
This feature allows the System Administrators and Application Administrators to search for an audit trail for a specific date range and then export a CSV file with the audit trail information for that specific data range. The file is available to export for 2 weeks.
Impact analysis
- Interface options:
- UI
- Business segment impacts:
- All business segments for Owners.
System features
There is no new or updated system functionality included in this release.
Resolved issues
Administration, solution version 6.1.0
The following issues are resolved in this release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.
ID | Interface | Issue Description |
---|---|---|
CMCP-37231: Notifications not displayed for Async Transform Set Actions in B2B Integration | Web UI | A success or failure notification should display in the notifications bell section for Add Transform Set, Export Transform Set, and Import Transform Set asynchronous actions. This issue is resolved. |
CMCP-37227: Admin: Audit trail Export Not Working | Web UI | The Administer solution is missing the TraceLink authorization to access the export audit trail functionality. This issue is resolved. |
Administration, solution version 6.0.0
The following issues are resolved in this release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.
ID | Interface | Issue Description |
---|---|---|
CMCP-35711: Users in Classic networks names show GUIDS | Web UI | Network names displayed non-human readable data in the Apps tab (previously Classic networks tab). This issue is resolved. |
CMCP-36774:Updates needed to the 'Assign New User to Network' functionality | Web UI | Updated the name of the ‘Add New User to Network’ section to ‘Add External User to Network’ in the Users menu item. Also, updated the error message that is displayed when assigning an external user to the network and the external user does not exist in in the TraceLink network. The updated message is "The [email] email does not belong to a user who is a member of the TraceLink Network". This issue is resolved. |
Known issues
Administration, solution version 6.1.0
There are no known issues in this release.
Administration, solution version 6.0.0
The following known issues are included in this release and will be fixed in a future patch release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.
ID | Interface | Issue Description |
---|---|---|
CMCP-37093: Pagination not working properly | Web UI | When a user attempts to use pagination in the Date Range filter on the View Audit Trail screen, the actual file count is not displaying correctly and there are some missing files. Additionally, the pagination arrows do not function properly. |