Contents

64-bit Support

Serena Business Manager is now supported on 64-bit versions of Windows 2008 R2 Server. Upgrade support for migrating existing 32-bit installations of SBM to 64-bit is handled through a new suite installation on one or more 64-bit Windows 2008 R2 servers. You can either perform a Custom installation that installs one or more SBM components on multiple 64-bit operating systems or you can perform a Complete installation, which installs every component on a single 64-bit server. You can continue to perform Remote Administration tasks or connect directly to the database via ODBC using 32-bit clients. Serena License Manager 2.1.5 is also supported on the 64-bit Windows 2008 Server platform.

You can use the SBM System Administrator that is installed by the suite installer on a 64-bit Windows 2008 R2 server to upgrade the SBM Application Engine database. As part of the upgrade, Serena recommends that you review and upgrade any scripts and APIs that were originally created on a 32-bit operating system to ensure that they also run on a 64-bit system. For example, if you have any SBM scripts that load .dll files, those dll files must be upgraded to run on a 64-bit machine.

Occasional User Product Access

Occasional User access allows the same set of privileges as the External User access type, but it also enables users to own items they submit, update items they own, and transition items they own. This access type is only available with the use of seat-based licenses.

Conditional Routing of Workflow Items

You can now use conditional routing to create application workflows that automatically route an item to a particular state based on visually designed rules. The rules are mapped to outgoing transitions from Decision steps in the workflow. The workflow evaluates the item data defined by the rules and determines which transition will be taken. One or more incoming transitions lead from a source state to a Decision step, and two or more outgoing transitions lead from the Decision step to their respective target states.

The values for the item data can be stored in application variables. Designers can change the value of any application variable, and all rules referencing that variable will use the new value.

New Report Types

The following report types are now available for end users in the SBM User Workspace:

• Drill-Through reports allow you to create a collection of reports that are linked together, meaning that you can have a high-level summary report and then 'drill-through' this high level report into the details. The 'drill-through' populates the linked reports with the data that you selected. For example, your high-level report could be a distribution of items based on severity, and your lower-level reports could be your distribution by developer and duration to close. This would allow you to select High severity items and see how the items are distributed among developers and how long the items take until they are closed.
• Elapsed Time reports help you to maintain and improve the service quality through a constant cycle of monitoring and reporting on the processes that are deployed within an organization. The elapsed time reports display the duration that items have remained in a state or a collection of states.

Rich Editable Grid

Custom Transition Controls

You can now add custom transition controls to a custom form. These controls can be used instead of or in addition to the standard transition buttons at the top of the form. Custom transition controls can be placed anywhere on the form, and their labels can be changed. The controls can be buttons, hyperlinks, or images. You can duplicate controls on other parts of a long form so users do not have to scroll to click the controls.

On a custom state form, you can use a single control for multiple transitions by using a "transition name" placeholder for the control label. The label changes to the name of the outgoing transition associated with the current state. The label also changes if the name of the transition in the application workflow changes.

Swimlanes

You can now add swimlanes to an application workflow. Swimlanes are a way to visually group states in a workflow, so others can quickly understand the workflow design. A swimlane typically represents either the activities performed by the same role or participant, or a distinct phase of the process defined by the workflow.

Relationships Bar

The new Relationships bar provides visibility into design elements, such as forms, that are used by an application workflow. Visual cues in the application workflow and the Relationships bar quickly demonstrate the relationship between the workflow and the design elements. If you need to modify a design element, you can open its editor and Property Editor from the Relationships bar.

SBM Application Engine Web Services API Enhancements

For detailed information about all of the calls, arguments, and responses available in SBM Web services version 7.2, see the Serena^® Business Manager Web Services Developer's Guide.

Enhanced Auto-Logout Timed-Out Users Feature

Improved Notification Server Performance

SBM Application Engine Notification Server performance has been improved. For example, e-mail messages are now processed more quickly by the Notification Server.

Detailed information about supported platforms and software configuration is available in the Supported Platform Matrix.

Server Operating Systems

The following operating systems are now supported:

• Windows Server 2008 R2 Enterprise Edition (64-bit)

Client Operating Systems

The following operating systems are now supported for SBM Composer and the SBM User Workspace.

• Windows 7 (64-bit)

Database Management Systems

The following database management systems are now supported:

• Microsoft SQL Server 2008 R2
• Oracle 11.1.0.7
• Oracle 11.2.0.x

Database Client Connectors

Oracle ODBC connections that use the Oracle driver are no longer supported.

For Oracle systems, you must connect to the SBM Application Engine database using either the Mashup2009 DSN that is installed with SBM or a system DSN that uses the "Oracle for SBM" driver that is installed with SBM. The "Oracle for SBM" driver is now the only supported Oracle driver for SBM Application Engine database connections.

Web Browser

Serena License Manager

Serena License Manager 2.1.5 is now supported.

Web Services

SBM Web services version 7.2 is now supported. The latest application Web service calls can be found in the sbmappservices72 WSDL. The latest administrative Web service calls can be found in the sbmadminservices72 WSDL. All TeamTrack Web services and earlier SBM Web services (including ttwebservices, aewebservices70, and aewebservices71) are still compatible with this release. However, these WSDLs have been deprecated and will not contain any of the new calls or parameters found in SBM Web services version 7.2. For new Web service implementations, use SBM Web services version 7.2.

• Microsoft .NET Framework 3.5.1 is now required instead of .NET 3.5 on all server and client machines. If it is not detected, .Net Framework 3.5.1 is installed by SBM (except on Windows 2008 R2 servers, which require manual installation). To save download and installation time, you may want to install version 3.5.1 prior to running the SBM installer. Also, if you will not have Internet access during the installation, you should download and install 3.5.1 beforehand.
• Server settings for the SBM Application Engine Notification Server and Mail Client can now be configured using the SBM Configurator.
• The SBM Configurator now features a Collect Log Files button that gathers and saves important log files in a .zip file for troubleshooting purposes. The logs that are gathered can be used by Serena Customer Support for troubleshooting problems in SBM. For a list of the log files that are gathered, see solution S138027.
• SBM Configurator now enables you to establish Secure Sockets Layer (SSL) for IIS and JBoss connections. This secures end-user connections into SBM as long as the request is sent using HTTPS. To configure these SSL settings, run SBM Configurator in utility mode and select Security from the Advanced Settings menu. (The Single Sign-On (SSO) tab has been renamed to Security). In the SSL sub-tab, you can generate, import, or remove SSL certificates for the IIS and JBoss components that are installed on the server.

• Additional options have been added to the Display Options under the user's profile. These include:

  • Show Confirmation Alerts when exiting forms
  • Restore Saved Form Data
  • Show Legend
  • Show Focus Helper
  • Default to 'All Transitions' Mode
  • Confirm Quick Transitions

  Refer to the SBM User Workspace help for more information on these settings.
• The Export to Excel functionality has been enhanced to better handle report formatting and field formats. For example, date fields are now imported into Microsoft Excel as dates. The data is now passed using XML.
• On Submit, the project selection screen is now bypassed when users have a single project. When users only have one preferred project in an application or their application only has one project, clicking the Submit link on the navigation pane will take them directly to the Submit form for that project. The project selection screen is now bypassed.
• The functionality to save a submit form as a favorite has been enhanced to eliminate some inconsistencies in behavior of the favorite URLs themselves (differences in how they were invoked and saved) and the save/restore of the values (differences between Web browsers and data types).
• Advanced distribution reports have been enhanced to allow graphical outputs.
• A new System Report enables you to track administrative changes to user accounts. The Users Change History report shows when user accounts have been created, modified, deleted, undeleted, disabled, or enabled. The name of the administrator who made the change and the date and time of the change are also provided. Only changes made since the upgrade to version 2009 R4 are available.
• The SourceBridge installer and documentation have been removed from the Product Information tab in the SBM User Workspace. You can download SourceBridge from http://www.serena.com/support, however, and make it available to users as needed.
• External users now appear as potential selections in the To: field when you send an e-mail from an item in the SBM User Workspace.
• Application icons now appear in the SBM User Workspace. These are defined for applications in SBM Composer, and they appear on the application tabs and on the start page for each application.

• Many user preferences are now stored in the database instead of as cookies. These include the expansion of the navigation panel, using an accessible interface, and the number of tabs to display.

• In the application editor, you can associate an image with an application. The image will appear on the application tab in the SBM User Workspace.
• The Workflow Palette now has the following sections:
  • Common Items contains the following objects: Swimlane, State, Decision, Transition, and Annotation.
  • States contains the following state types: Active, Completed, Rejected, and Pending. The latter three states are "inactive" states. Their titles represent common inactive states, but can be changed. The Active state type is identical to the State object in the Common Items section.
  • Transitions contains transition types. The Quick transition type is new, and is configured to not show a form to users. The Regular transition type is identical to the Transition object in the Common Items section.
• There are new keyboard shortcuts that let you navigate through the user interface without using the mouse. A new Find dialog box supports searching for items without using the mouse. The name of the previous Find dialog box is now Find Items.
  Note: The "Shortcut Keys" topic in the SBM Composer Guide and online Help lists the keyboard shortcuts. There is also a link to this topic from the Composer Start Page.
• You can double-click a state in the Workflow Palette to add it to a workflow. The state is added to the right of a selected state, on the right side of a selected transition, or to the center of the workflow editor if no state or transition is selected. For most transitions, the transition is placed between the two most recently selected states, and points from the first state that was selected to the second state.
• The AddRadioCallback event method is now included in the SBM Javascript Library. This method is called when a user clicks a radio button in the SBM User Workspace.
• The Twitter widget is no longer supported, and was removed from the Form Palette.
• The system Deleted state can no longer be a destination state for Regular transitions.

• The Bookmarks view has been removed.
• A new tab in the Common Log view enables you to select the environment for which you want to view messages. If you have multiple environments, point the Common Log for each environment to a unique database. This ensures that Common Log messages you see are specific to each environment.

• For Oracle systems, you must connect to the database using either the Mashup2009 DSN that is installed with SBM or a system DSN that uses the "Oracle for SBM" driver that is installed with SBM. If you attempt to use a DSN other than the Mashup2009 DSN provided by SBM, the SBM System Administrator prompts you to either use the Mashup2009 DSN or to modify or create a DSN that uses the "Oracle for SBM" driver. The "Oracle for SBM" driver is now the only supported driver for Oracle database connections from SBM System Administrator.
• Administrative logging is now enabled by default. To support this change, the Enable Database Logging check box has been removed from the Database tab of the Settings dialog box in SBM System Administrator.

• On the Data Mapping tab in the Property Editor for orchestration workflows or Service steps, icons for data elements that cannot be changed now have a small lock icon on them. Previously, these icons were displayed in gray. You cannot rename, change type, or change child data elements for data elements that come from a Web service.

• The sso_endorser user account has been deprecated. This account is no longer used by the Single Sign-On engine to endorse a user ID that does not have an associated password. Instead, these user accounts are now endorsed automatically by way of certificates that are presented to the STS (Security Token Server) with each authentication call. For new installations, this account is no longer automatically added to your database nor is it included in the sample database. On upgrade, this account is not removed from the database; however, you can delete the sso_endorser user account yourself if you do not use it.

• The jakarta virtual directory name has been changed to sbmconnector. The virtual directory name was changed to avoid naming conflicts that occur when SBM and Version Manager are installed on the same server.

• The internal name for the Serena Common JBoss service is now "SERENAJBOSSSVC." This affects scripts running tools that require the internal name (for example, SC.exe).

• Several improvements have been made to the SBM Application Engine Web Services API in this release. See What's New for more information.

• When users click the main help icon on the SBM User Workspace toolbar, the help system now opens to a page that provides guidance for common tasks, such as submitting and searching for items.
• A "What's New" section has been added to the SBM Composer Guide and help system. This section provides a description of new features added to SBM Composer.