<< Click to Display Table of Contents >> Navigation: Release Information > Version 2.0 (July 2023) |
Important notes and changes
Change of system URLs for object links
With the change of the release, the URLs for accessing individual objects in the system are changed for technical reasons.
Examples include emails sent via an email template that contain the option "Link to ticket" or "Link to SSP" (e.g. "New ticket has been created") or approval emails with a link to the approval object in the self-service portal.
As a result, emails sent with the link before the update will not work after the update. In that case, the ticket processor (for the limited transition period in which these emails are used) must send a new email with the new link if necessary, or the user must log in to the system via the normal log-in and open the object there.
The URLs for the general login (Notified general URL on login page) do not change or are resolved correctly in the background.
Use new version of AD authentication tool required for Single Sign-On (SSO).
With the release, system URLs are changed, this has an impact on the SSO tool.
In order for the SSO functionality to continue to work after the release update, the SSO tool must be replaced (few minutes effort).
The new version was provided in advance of the release including a short tutorial.
For the update please proceed as follows:
1. download the latest version of the authentication tool (ExternalAuthentication_iis_app_files.zip) via WebHelp.
Download link: https://bts.baramundi.com/webhelpen/otx_webhelp_ad-integration.html
2. on the local authentication server there should already be the existing IIS application 'auth', usually under the path 'C:\inetpub\wwroot\auth'.
Delete all files in the directory 'C:\inetpub\wwroot\auth', except for Web.config. 4.
4. now unpack the new version into a temporary directory and copy the complete content except the Web.config into the existing directory 'C:\inetpub\wwroot\auth' and integrate the new files.
Attention: If you also overwrite the Web.Config, the application will be reset and you would have to restart the setup (/auth/config) to specify the setting token and parameters again!
"Task Board" function removed for the time being
In the Cockpits area, there was previously the "Task Board", which provided a graphical overview of all tasks in the system.
According to feedback from many customers, this was not used and had functional limitations.
Pending the availability of a Task Board with technically rebuilt, improved functionality, the feature was removed.
This did not create any functional limitations as this was just an additional overview. Tasks can also be used and managed in tickets as before, or directly in the Tasks section.
Only one login possible in the same browser
Due to the new technical architecture of the client, only one login can be performed in a browser at a time.
I.e. logging in with 2 different users in 2 browser tabs at the same time is no longer possible.
Possible workarounds, if you still need this (e.g. as admin log in once in user access and once in SSP for tests in parallel):
•Use another browser in parallel for the 2nd login.
•Use the incognito mode in the current browser for the 2nd login
Known issues (will be fixed with subsequent releases)
•Workdesk: KPI tab is not displayed
•SSP: at smaller screen resolutions or with browser zoom the function tiles do not wrap cleanly and are rather displayed one below the other
•The user login option with the extension "/User" (automatic display of the workdesk after login) is currently deactivated and redirected to normal login
•The new darkmode (User menu > Color scheme > "Dark") is currently still in a preview version and displays some color contrasts as well as some icons not well readable
New functions
New user client
With this bTS release, a technically completely revised browser client is made available.
This has the following advantages:
Improved performance
By changing the system architecture of the browser client, system performance has been significantly optimized in many areas.
In particular, the loading times for opening forms and processing many form functions are up to 70-90% faster compared to the previous client (speed still depends on the individual network configuration and bandwidth as well as the browser used by the customer).
This allows for a significantly increased efficiency in the processing of all transactions.
Optimized usability
In the course of the new development, all operating elements, menus and editors of the browser client were analyzed and revised with regard to user-friendliness, positioning and the operating concepts.
In addition to a contemporary design, the aim was to make the operation of complex editors and functions more intuitive and consistent throughout.
The optimized user experience ("UX - User Experience") is reflected in many small details as well as larger redesigns.
Revised user interfaces
Many forms, especially large, more complex forms such as the ticket form, have been redesigned in terms of structure and arrangement of some controls.
Large forms have been changed from a long ribbon with sections to a tab structure in order to be able to switch more quickly between the contents and to allow more space for individual lists.
The conversion of the forms as well as the repositioning of individual fields and functions was deliberately not carried out in its entirety in order not to impose too great an adjustment on existing customers.
Mobile use in the browser
The browser client dynamically adapts to the available screen size.
This means that operation is consistently supported across all typical variants of end devices - from large desktop screens to smartphones.
The display of the client and the forms is automatically adapted to the available screen size, thus distinguishing between a desktop view, a reduced screen width (e.g. on a tablet turned upright) or a special mobile view.
Note: Currently, these mobile views are only available in User Access, not in SSP. Some special views (calendars/timelines) are not yet supported on very small screens (mobile view).
Improved session handling
After accidentally closing the browser tab without logging out, an immediate re-login is possible.
In case of an accidental double click on the LogIn button it is also possible to use the already open session.
Note: if the entire browser is closed without logging out, a re-login is normally possible again after about 2 minutes of waiting time.
New interface for people imports directly from bMS
The direct import from a local AD was not possible until now. By using the bConnect2.0 interface it is now possible to directly match and import the persons existing in bMS with bTS.
Detailed instructions will follow, as additional variables must be created within bMS for this purpose. In the meantime, baramundi Consulting is available to answer any questions you may have. In the article regarding bMS Interface you'll find also a link to a manual how to prepare the import on bMS side
Adjustments to various forms to restructure and optimize the form structure
On the following forms, a change from sections to tabs as well as a combination of information to reduce complexity and a new placement of individual fields was carried out:
•Ticket form
•Tasks form
•Knowledge Base Entry
•Email Form
•Asset Form
•User/People Form
•...More in detail
Further 112 Changes
•Minor function enhancements and improvements
•Background optimizations / stabilization measures
•Defect fixes