Release information

Are you a customer in BCS and would like to get a general overview of the current and past issues that have been processed in BCS via the ticket system? Are you a customer service representative and would like to enable your customer to independently view external ticket evaluations of his tickets in BCS?

The view "Ticket evaluations" in the area Tickets now allows customers to view the data for their projects. This means that only those tickets are evaluated that come from WBS elements to which the customer has a customer assignment. Data from other projects will not be displayed. The view can be called up with the customer license, not with the guest license.

This view is also available for BCS.start.

BCS 22.3 brings more security for every user. For authentication, you only enter a password as a BCS user so far. However, if you use the username/password pair on another platform at the same time and this data is leaked, unauthorized persons could also log in to BCS with this data. This scenario may be unlikely, but it cannot be ruled out via Trojans, keyloggers, or simply a colleague looking over your shoulder as you enter your credentials.

To eliminate these attack vectors in the future, we implement the TOTP procedure as of BCS 22.3. The second factor for authentication is a smartphone. The TOTP method is based on the fact that the BCS server and the smartphone share a secret. Using the current time, both devices can create a hash that results in a 6-digit number. This number is entered by the person next to the password when logging in to BCS, and the server compares it to the self-calculated number to ensure that the 2nd factor is present.

Each user can activate the 2-factor authentication for himself in his user account via a new button. After entering the user name and password, BCS will now additionally require the user to scan a QR code or enter an authentication code using the TOTP method. Once successfully authenticated, users can indicate that this web browser is to be trusted. When changing passwords, an authentication code is also required after activating 2-factor authentication. As easy as the 2-factor authentication could be activated, it can be deactivated again if desired.

This function is also available for BCS.start.

Do you want your offer to be approved by several people or a group of people before it is delivered to a customer and a review is only required when all people have approved the offer? Depending on the offer, this is of course a differently composed group of people and different individuals.

As of 22.3, there is a solution for this use case in the BPMN module to use multi-instance user tasks. This gives you the possibility to automate such a process scenario to a large extent. Another use case would be contracts in contract management where all selected persons agree to terminate or extend a contract.

This module and this function are not available for BCS.start.