# Administration

## <mark style="color:$primary;">Security</mark>

* In the Security Module, the label Admin in the Update Roles and Permissions table has been renamed to Security and Governance Admin.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>What Changed</h3><p>In the Update Roles and Permissions table, the label was previously Admin. Now, the label is updated to Security and Governance Admin.</p><p>This update involves only a label change and does not introduce any functional changes.</p><p><strong>Affected Users:</strong> Administrators</p></div>
* In the Projects Module, viewer license users now have default access to Projects and associated submodules.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>What Changed</h3><p>In the Projects Module, viewer license users previously did not have default access to Projects and associated submodules. Access had to be explicitly configured by application admins. Now, viewer license users have default access to Projects and related submodules. </p><p>This update eliminates the need for manual access configuration, simplifying administration.</p><p><strong>Affected Users:</strong> Admin and Viewers</p></div>

## <mark style="color:$primary;">Custom Fields</mark>

* Custom fields now use a rich text editor configured to allow only hyperlink insertion, replacing the previous plain text format.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>What Changed</h3><p>In Custom Fields, the text custom fields were limited to plain text. Hyperlinks could be added, but there was no user-friendly editor or formatting support. Now, text custom fields use a rich text editor configured to allow only hyperlink insertion. This maintains hyperlink functionality while preventing other rich text formatting and improves usability for adding and managing links.</p><p><strong>Affected Users:</strong> Authors</p></div>
* Custom field names now display correctly in downloaded templates for all object types.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>What Changed</h3><p>In Custom Fields, Global Custom Fields in LMDF templates were displayed as system-generated codes (e.g., gtcf1, gtcf2, gtcf3), making fields difficult to identify. Connector-specific Custom Fields appeared before Global Custom Fields, creating inconsistencies in the UI structure. This issue affected all LMDF templates supporting Custom Fields, including Data Catalog object templates, Tags templates, and DQR templates. Now, downloaded object templates display user-defined names for both Global and Connector-level Custom Fields. Global Custom Fields are positioned before Connector-specific Custom Fields, ensuring a consistent display across all object types, including Data Catalog, Tags, and Business Glossary.</p><p><strong>Affected Users:</strong> Authors</p></div>

## <mark style="color:$primary;">System Settings</mark>

* Reorganize system settings into module-based tabs.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>What Changed</h3><p>In System Settings, all 135 system settings were listed under the Others tab, making it challenging to locate specific keys. Now, new tabs have been added in System Settings based on modules and module groups for better organization. A Global Search feature allows searching across all system setting keys, improving findability and usability.</p><p><strong>Affected Users:</strong> Authors</p></div>
* System setting to enable or disable the session timeout warning pop-up.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>What Changed</h3><p>The application displayed a session timeout pop-up after a period of inactivity, warning users before the session ended. There was no option to disable the pop-up, and the behavior was inconsistent—sometimes the pop-up appeared, other times users were redirected directly to the login screen. </p><p>Now, a new system setting, show.timeout.popup, has been introduced under the Others tab to control the display of the pre-session timeout pop-up: </p><ul><li>True (default): The timeout warning pop-up appears before the session ends.</li><li>False: The session ends immediately after the inactivity period, bypassing the pop-up and redirecting directly to the login screen.</li></ul><p><strong>Affected Users:</strong> Administrators</p></div>
* Restrict Concurrent Login setting logs out newly logged-in users regardless of True or False value.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>What Changed</h3><p>In System Settings, Restrict Concurrent Login to either True or False caused any user logging into OvalEdge to be immediately logged out, preventing active sessions regardless of the setting. Now, a new system setting, restrict.concurrent.logins, controls session concurrency. When enabled, a new login automatically terminates existing sessions on other browsers or devices, while multiple tabs in the same browser remain unaffected. When disabled (default), users can maintain multiple concurrent sessions across devices or browsers.</p><p><strong>Affected Users:</strong> All Users</p></div>
* A new system setting, application.date.format, was introduced in version 7.x to standardize date formatting across the application.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>What Changed</h3><p>The date formatting across the OvalEdge application was not centrally controlled or consistent. The setting is.dateformat.yyyymmdd existed but had no practical impact on how dates were displayed.</p><p>Now, a new system setting, application.date.format, controls the date format uniformly across the application (introduced in version 7.x). Administrators can define a consistent format (e.g., MM/dd/yyyy, dd-MM-yyyy, yyyy/MM/dd) that applies across all relevant modules and interfaces. The setting is.dateformat.yyyymmdd is deprecated, as it no longer serves any functional purpose. </p><p><strong>Affected Users:</strong> All Users</p></div>

## <mark style="color:$primary;">Audit Trials</mark>

* In Audit Trails, a new Others tab is introduced to capture all audit events generated by the audit service.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>What Changed</h3><p>In Audit Trails, previously, audit events for different modules were captured in separate tabs. Now, a new Others tab is available to capture all audit events generated by the audit service. This tab includes filtering options based on predefined categories and subcategories, allowing users to refine audit records for specific operational areas or activity types. </p><p>For example, selecting the category Security and subcategory Object Access displays detailed audit logs of actions performed on objects such as dashboards, tables, and connectors. </p><p>This update introduces only the new tab; no other functional changes are made.</p><p><strong>Affected Users:</strong> Administrators</p></div>

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.
