Contents

New for Users

• Graphical report rendering has improved for Distribution, Trend, and Duration reports. Rich Graphical Reports offer dynamic charting and animation capabilities. Adobe Flash Player is required for users to run Rich Graphical Reports, which are enabled by default for your system.
• The Web interface has been redesigned and has a new color scheme. Many links and buttons have been replaced with user-friendly icons, and the Launch page has been reorganized. For example, the application Home link has been replaced with an icon and moved to the upper right corner of the Web interface.
• The State Change History now appears on a single row on the Item Details form and contains a slider that enables users to scroll through the state change history when there are many states and transitions. A "Show All" link has also been added. Users can click this link to view the complete state and transition history in tabular form.
• First, previous, next, and last links are now available when users are viewing items from report or search results and have the Single Frame View check box selected in your their profile. This enables them to quickly view items in the report or search results without returning the results list.
• An icon has been added to the Item Details page to enable users to copy the URL for the item to the Clipboard. In the dialog box that opens, users can press CTRL+C to copy the selected URL.
• Users can now manage their Application tabs by clicking the Manage Tabs link available when they click the More link. This link is only available for users who have access to more than three applications.

New for Mashers

• The Create New Mashup dialog box lets you create mashups based on built-in templates (application and orchestration), user-created templates stored on your computer (.mst files), and pre-built mashups from Mashup Central. When you click Create in this dialog box for built-in or user-created templates, the Configure Mashup dialog box opens, which forces you to change mashup, application, and database table field names. This is necessary because validation fails if any application or table in the new mashup has the same database name as it had in the template. When you click Create in this dialog box for pre-built mashups, another Create New Mashup dialog box opens, which requires you to enter information about yourself and your company, and agree to an end-user license agreement.
• Mashup designers can create report definitions for application listing reports. Application listing reports are a starting point for end users to pre-configure regular reports. End users can create any number of regular reports from a single application listing report. This feature supports the drag-and-drop operation for field selection, drop-down lists for comparison operators, and in-place or popup editors for the values section of an expression.
• The Add Owner to State wizard lets you quickly establish ownership for items in a state by assigning a User field to the Owner property of the state. The Add Secondary Owner wizard lets you quickly establish secondary ownership for items in a state by assigning a User, Multi-User, or Multi-Group field to the Secondary Owner property of the state.
• You can now place widgets on custom forms using widgets to create rich interface mashups or presentation mashups. Several specialized widget types are available in Mashup Composer, including widgets that you can use to embed almost any valid HTML or Javascript, the content found at any valid URL, an RSS feed, a YouTube video, or an Amazon.com search.
• The REST Grid widget lets mashup users access external data (a REST service) and display it in a tabular format in a mashup. You can pull data from any Web service that supports the REST format.
• Web service endpoints can now be defined from within Mashup Composer when you deploy mashups.
• You can now create synchronous orchestrations that return data immediately to an application. Synchronous orchestrations can be specified for transition actions and state actions.
• When possible based on information in a mashup, external mashup endpoints are automatically created when a mashup is deployed. Other endpoints must be manually defined in Mashup Manager. Users will should verify and edit (if necessary) the external endpoints that are created to make sure they are mapped to the correct runtime locations.
• You can now compare the differences between two mashups by running the Comparison report in Mashup Composer.
• You can now create references to associate design elements from another application into your mashup. For example, to create a Post transition that submits items into a project in a different application, you can now reference the application rather than merge the two applications together. The "merge" capability is no longer supported.
• Mashup Repository connection options in Mashup Composer have been improved. You can now specify the server name and port number rather than a full service URL. In addition, you can now switch between repositories more easily, and specify a non-default local cache path.
• Mashup Composer can be used in on-premise or on-demand mode. Functionality specific to on-premise mode, such as Mashup scripts, is not available in on-demand mode. Mashups are validated for on-demand functionality before they are deployed to an on-demand environment.

New for Administrators

• The Active Users system report has been added to help you track the number of users with full and external product access who have actively used the system in the last 12 months. An active user is defined as any user who has created or updated a report or submitted, transitioned, updated, or deleted an item.
• To accelerate the setup process, your mashup is preconfigured with the following elements after the mashup is deployed for the first time:
  • Projects - Projects store items tracked by your mashup. A project is automatically created for each application workflow and sub-workflow in a mashup. The project inherits all properties from the workflow, including the project name. If the workflow name includes "Workflow", it is replaced by "Project".
  • Notifications - To ease the process of implementing new mashups, a default set of notification and notification rules is automatically provided for each workflow in your application. The notifications and supporting rules are added after the first deployment of a new mashup or on subsequent deployments after new workflows have been added. The following notifications are provided with each deployed workflow:
    • I become the owner of any [item]
    • Any [item] is submitted
    • Any [item] changes owner
    • Any [item] changes state
    • Any [item] changes to inactive
    • Any [item] I submitted changed state
    • Any [item] I submitted changed to inactive
• Logging has been significantly enhanced. The Log Viewer in Mashup Composer displays step-by-step messages pertaining to Web service operations and mashup events that are assigned to state and transition actions. This information can be exported to an XML file. The Common Log View in Mashup Manager displays messages about deployment successes and failures and step-by-step information about Web service callouts and events raised by the Orchestration Engine.
• Mashups can now be undeployed from the Application Engine by users granted appropriate privileges. This action deletes the mashup and associated primary items and other data from the Application Engine. This operation is available within Mashup Manager.
• The "Login as" feature has been extended to allow users granted the "Logon as Another User" privilege in Mashup Administrator to log in to Mashup Manager as another user.
• This release includes a number of performance improvements benefitting systems with heavy user or automation activity. Improvements include a reduced memory footprint for the Application Engine, throttling support to limit the number of Web service invocations and payload, and JMS queue to improve reliability of the Orchestration Engine. For details, refer to the Serena^® Business Mashups Installation Guide.

• Active/Inactive icons no longer display next to items returned in Listing reports or searches in the Web interface. The color of item's title in a list of results now indicates the status of the item. Custom active/inactive icons you used in previous releases no longer appear in the Web interface.
• The Back to Search link on Search Results pages has been replaced with an Edit Search icon. The icon is located in the upper right corner of the results page, between the Export to Excel and Save as Report icons.
• Users can now choose to search for item link attachments by item ID or keywords. Item IDs or keywords can also be used to search for items to link as subtasks or principal tasks.
• A Reload Item icon has been added next to the Actions drop-down list on the Item Details page. Click this icon to reload any item. This is especially useful to reload items that might be waiting for an Orchestration or Web service update.
• The License Usage system report has been renamed to Current User Activity report to more accurately reflect the results returned by the report.
• The Printable View icon is not available for Rich Graphical Report results. To print results for these report types, right-click in the report results, and then select Print Chart.
• Administrators can now use the Web Administrator to change passwords for existing user accounts that they can manage.
• Managed administrators with privileges to delete users can now do so from the Web Administrator. Deleted users can also be restored from the Web Administrator.

• Mashups created in versions previous to 2009 R1 are automatically upgraded when they are imported into Mashup Composer. Once upgraded, these mashups cannot be opened in earlier versions.
• In earlier releases, you could merge mashups so you could deploy related applications at one time. External references are now used instead to relate applications in different mashups. With external references, related mashups must be deployed in a certain sequence. Referenced mashups must be deployed before referencing mashups. If there are circular references (that is, Mashup A references Mashup B, and Mashup B references Mashup A), at least one of the mashups must be deployed twice to make sure that all referenced mashups are deployed before all referencing mashups. The deployment sequence can be A-B-A or B-A-B.
• You can now use Single Selection fields to define actions.
• Visual feedback is provided when you drag a new state onto an application workflow. This "ghost" image of the state being dragged lets you see exactly where the state will be placed when dropped onto the workflow.
• A mashup that exists in Mashup Manager, but does not exist in the Mashup Repository (because it has never been imported into Mashup Composer), now appears in the Open Mashup dialog box as if it had been imported.
• Mashup Composer now supports Secure Socket Layer (SSL) connections to the Mashup Repository.
• You can now select the parent controls that you want to modify in a form from a menu. This lets you see the hierarchy of controls, and makes it easy to select a control that is behind another control on the form.
• You can now resize rows or columns by dragging a cell or cells over other cells. There are visual indicators, or handles, that show you from which direction they can drag. You can resize controls by dragging them over a cell or cells. The handle for controls is visually different from the handle for cells.
• The General tab of the Options dialog box has an option that causes all design elements to be displayed in Mashup Explorer when you start Mashup Composer. If this option is not selected, the Workflow Design filter is displayed by default.
• Visual feedback is provided when dragging a transition onto a workflow. This lets you see exactly where the transition will be placed when dropped into the workflow. This means that the transition can be placed accurately with just one mouse click.
• The current connection information, including whether you are connected or offline, and the server mode (on-demand or on-premise), is displayed on the Repository tab of the Options dialog box.
• In the form editor, a context menu lets you select column and row sizing behavior (fixed, percentage, or autosize). You can also click a table on a form to see the sizing behavior—an F on the outside of the column or row indicates that the column or row is of fixed size, an A indicates that a column or row is autosized, and a % indicates that the size of the column or row is measured as a percentage of the form. You can click F, A, or % to toggle between sizing behaviors. In the form editor, you can also resize columns and rows that use the fixed or percentage sizing behaviors.
• Validation warnings are now generated when required Web service elements are not mapped. In addition, warnings are now generated when a mapped design element is deleted.
• The Message Selector dialog box, which is invoked from the Log Viewer, lets you select whether user messages or user and technical messages are displayed. The default is to display user messages only.
• The REST Grid and Amazon Search widgets now let mashup users select a row in the grid to populate one or more controls.
• The placement of a transition label is preserved when you change the shape of a transition in a workflow.
• A new Create New Mashup dialog box was added to accommodate the requirement that you agree to the EULA (End User License Agreement) before you can create a mashup based on a pre-built mashup from Mashup Central.
• Work Online and Work Offline options are now available as check boxes from a single menu at the bottom right of the Mashup Composer window. These options can also be selected from the Repository panel in the Serena Mashup Composer Options dialog box.
• The appearance of the Ribbon was simplified and its functionality was improved.
• The default on-demand or on-premise setting changes depending on the installer (on-demand or on-premise) used to install Mashup Composer.
• When you connect to a repository that does not match the current mode (on-demand or on-premise), a message is presented that lets you change the current mode.
• You can no longer change a Text field's type once a mashup has been deployed. For example, you cannot change a fixed-length Text field to a memo field. If you open a previously published mashup from a file, however, you may be able to change the type of a Text field. In this case, you will receive an error when you attempt to deploy the mashup. To work around this problem, export the mashup to a file, reopen the mashup from the file, change the Text field back to its original type, and deploy the mashup.
• To prevent data loss when working in a patch context, you can no longer create some design elements in a patch context. You can, however, copy design elements from the head (tip) version to the patch context. Because the design elements retains the same internal identifiers, any data collected in the Web interface or related to design elements created in the patch context is still viewable when the head (tip) version is deployed.

• You can now remove Quick Links from the Settings tab of the Add User or Edit User dialog box in Mashup Administrator. In addition, you can add more than two Quick Links to each user's account.
• Deployment and promotion activities are no longer recorded in the TS_ADMINCHANGES table.

• There is now a Common Log view in Mashup Manager that displays log entries pertaining to Application Engine and Orchestration Engine activities. "Key" (most important) messages are highlighted. You can search the Common Log messages by text content, severity, date/time, user name, application name, and orchestration name. The Common Log is available from the Advanced tab in the Mashup Manager navigation pane.
• When viewing the history of a mashup, you can now purge old mashup versions using the new Purge button. For details, see the Mashup Manager documentation.
• The Activities view how has a pagination feature. When the list of activities is long, they are divided among multiple pages. You can navigate between pages by clicking the arrows or page-number links provided in the lower right corner of the window.
• A command-line tool is now available to encrypt the passwords stored in the JBoss datasource files on the file system.
• You can now create a new endpoint when you deploy a mashup for which endpoints need to be defined by clicking the Create Endpoint link in the Destination Endpoints window.
• The link to change your current language and country has been moved from the Login page to the Mashup Manager toolbar.
• A "No Filter" option has been added to the Event Manager Log page.
• Global administrators can now delete environments that specify an Application Engine server that has been removed from the network.
• The Deploy History and Versions tabs for a mashup now have a column containing the comment added to the mashup when the mashup version was published.

• Mashup events can now be raised from e-mail messages. For documentation on this feature, refer to the Serena^® Mashup Composer Guide.
• Responses from Web service calls in synchronous orchestration workflows are now logged in the Log Viewer as one of the following:
  • The synchronous orchestration workflow is completing and sending the following message back: [The SOAP message appears here.]
  • The synchronous orchestration workflow is completing and sending the fault {0}: [The SOAP message appears here.] {0} represents the actual fault name.
• Support is now available for raising events by listening to messages (as XML documents) in one or more Java™ Messaging Service (JMS) queues. The Event Manager Queue Adapter reads the XML documents, packages them as mashup events, and sends them to a configured mashup in Serena Business Mashups for processing.
• For Web services that return named faults, Catch branches for all of the fault names associated with a particular Web service operation can be added automatically in the FaultHandler section of a Scope step. For documentation on this feature, refer to the Serena^® Mashup Composer Guide.
• The Throw step has been completely revised and is available on the Step Palette for use in orchestration workflows. For documentation on this feature, refer to the Serena^® Mashup Composer Guide.

• The Set-Value-Method argument has been added to the extendedFieldList parameter of a TTItem argument. Set-Value-Method indicates how to process values in a Text field or any field that contains multiple values such as Multi-Selection, Multi-Relational, Multi-Group, or Multi-User. You can replace, append, or remove values using Set-Value-Method.
• The precedence order in the Set-Value-By argument has been changed. The internal value is now evaluated before the UUID value.
• The Auth type now contains a loginAsUserId parameter that allows you to specify a user ID for a Business Mashups login you would like to impersonate.
• Several new "withName" calls have been added to Business Mashups. These calls do not require an internal table, project, or transition ID. Instead, you can specify the database name for these objects. The new calls are:
  • CreateAuxItemsWithName
  • CreatePrimaryItemsWithName
  • DeleteItemsByQueryWithName
  • GetAvailableSubmitTransitionsWithName
  • GetItemsByQueryWithName
  • GetSubmitProjectsWithName
  • GetTablesWithName
  • UpdateItemsWithName

  Additionally, CreatePrimaryItemWithName was changed to use submitTransName instead of submitTransID.

• The GetReports call has been added to Business Mashups. This service returns a list of reports within a specified range, limited by one or more optional filters.
• The RunReport call has been added to Business Mashups. This service runs a specified report, given the proper privileges.
• The GetSolutionWithUniqueName call has been added to Business Mashups. This service returns a list of applications that can be accessed by the user. The response for GetSolutionsWithUniqueName returns the unique solution name; the response for GetSolutions does not. Thus, if you want to provide the unique solution name for the GetTablesWithName call, use GetSolutionsWithUniqueName.
• Sub-Relational field names are now returned in the <name> element of the extendedFieldList. For example, to indicate the Phone Number field from the Contacts table, the <name> element contains CONTACT:PHONE_NUMBER. In previous versions, only the table and field ID were returned.
• The GetAvailableTransitionsWithStateIDs call has been added to Business Mashups. This service returns a list of available transitions for the specified item. The response includes internal IDs for the "to" and "from" states.

• A new responseOptions parameter has been added to all the Create, Update and GetItem calls. Using responseOptions, you can limit the sections returned in the TTItem response. For example, you can opt to return only the extendedFieldList sections if your response items have large attachment sections that you don't need to see.

• SSO now also enables users with a valid e-mail address assigned to their account to request a password change from the SSO login page. After users request a password change, responses are sent to their e-mail address by the Notification Server.
• Single Sign-On (SSO) is now automatically configured if you select the SSO options during installation. The exception is that you must still enable SSO on the Server tab of the Settings dialog box in Mashup Administrator. In addition, Mashup Composer now automatically detects if the system it is connected to is SSO-enabled, and users no longer need to modify the Serena.Studio.Shell.Application.exe.config file to enable or disable SSO.
• An SSO Endorser user account is now automatically added to new and upgraded databases and is configured to communicate with the Security Token Service. This user account is assigned API/Script product access. This product access type does not consume seat or named licenses and users assigned API/Script access cannot log into the Web interface. Privileges are not assigned to the SSO Endorser user account. For details on modifying this provided account, refer to the Serena^® Business Mashups Installation Guide.
• Mashup definition files, or blueprints, now have an .msd extension. You can continue to open files with a .zip extension in Mashup Composer if they contain a valid mashups. In addition, mashup snapshot files now have an .mss extension.

• Several improvements have been made in the Serena^® Business Mashups Web Services Developer's Guide. All Application Engine Web service calls, arguments, and responses are now described directly in the guide. The same improved reference material now appears in the Mashup Composer online help.
• Support for throttling the number and payload size of Web service calls has been added to Business Mashups. For more information, see the "Throttling the Application Engine and Orchestration Engine" section in the Serena^® Business Mashups Installation Guide.
• Instructions on configuring the Common Log data source have been added to the Serena^® Business Mashups Installation Guide.
• Several improvements have been made to the Business Mashups silent installation documentation. All silent Installer components and variables are now explained in the "Silent Installation" section of the Serena^® Business Mashups Installation Guide.
• A new chapter has been added to the Serena^® Business Mashups Installation Guide that covers the best practices for scalability with Business Mashups.

• The Serena^® Mashup Composer Guide has been improved and enhanced as follows:

  • Detailed troubleshooting steps for both applications and orchestrations are provided in the "Troubleshooting" and "Troubleshooting Orchestrations" chapters.
  • Handling faults from Web services is explained more fully in the "Orchestration Procedures" chapter, under the "Using the Scope, Throw, and Compensate Steps to Handle Faults From Web Services" section. Several examples and tutorials are included in this section.
  • The "Raising Events Using JMS Queues" chapter introduces the Event Manager Queue Adapter (EMQA). This chapter, intended for advanced users, contains useful information on topics such as adding a JMS connection and importing and mapping custom mashup tools.

• Database upgrade performance has improved for Teamtrack-to-Serena Business Mashups upgrades due to changes in how unique identifiers (UUIDs) are assigned.
• The installer will now prompt you for Serena Common Tools POP3 and SMTP mail server information. The POP3 server is used to receive e-mails which can trigger events in the Event Manager. The SMTP server is used to send e-mails whenever the Event Manager was not successful in processing an event.
• The option to install Mashup Composer is now available at the end of the suite installer. In the Post Install Summary dialog, select "Install Mashup Composer" to immediately launch the client installer, which will install Mashup Composer on the server.
• The suite installer no longer requires you to install IIS when you only install the Mashup Administrator component. However, in this scenario, Serena recommends running the client installer (SMC2009.exe) instead, since it is smaller and does not contain the rest of the server components.
• The silent installer now installs the tmtrack and gsoap virtual directories under the Web site you specify in the varWebsiteChoice and varWebsiteNumber variables.

• Field selections set to display as radio buttons or checkboxes on a custom form now appear vertically in the Web interface. This fixes an issue that caused the selections to appear horizontally in the Web interface, though the form preview in Mashup Composer would display them vertically.
• An error no longer occurs when users delete an item that contains a question mark in the Title field.
• Users lacking the "View State Change History" privilege no longer see the State Change History container on custom forms in the Web interface.
• The designated submit transition that is used when posting an item now honors the Required Attachment setting. This fixes an issue that prevented the requirement from appearing, causing an error to occur when completing the submit transition.
• Data entered during a transition is now repopulated if the transition is executed again after navigating away from a partially completed form. This fixes an issue that would clear all previously-entered data on the form if the user navigated to another area without supplying a required field value.
• Fields that require values during a Mass Update now appear in red text. If items that you are mass updating span multiple projects in which the required attribute has been overridden, the first issue in the list is used to determine the project that is used to determine the required fields.
• An error no longer appears when users copy an item containing file attachments that are stored in the database.
• The Required Attachment setting on a transition can no longer be circumvented by attaching a file and then deleting it before the transition is completed.
• A code change has been made to fix a situation that would put the Web interface into an endless loop when executing a Create Subtask or Post Item transition. Prior to this fix, if the submit transitions (called either via a Create Subtask or Post transition) had either the "No Button on Form" or "Quick Transition" option selected, the browser would loop endlessly, forcing the Administrator to remove these options from at least one of the available submit transitions.
• Fields and field values from all field sections no longer appear for external users on the Advanced Search page. Only fields and field values from the Standard section now appear for external users.
• Performing a Lookup against a numeric field in an Auxiliary table now returns the proper results.
• Journal field values are no longer saved prematurely if a transition is failed due to form validation performed by a Post-Transition script.
• Results are now correctly returned for all tables selected for Multi-Table reports and Global Searches when multiple tables are specified in the query.
• The Set as Home Page option now works correctly when users select it from the Save Report page.
• Existing text is now removed from an Append Only Journal field when the Clear option is selected on the Field Overrides tab of the transition property editor in Mashup Composer.
• Users no longer receive an error when they perform a keyword search that contains an apostrophe. This problem only occurred on systems using Oracle.
• The Title field value is no longer truncated in the subject line of a browser e-mail if the value contains a double-quote.
• The TTAUTH login parameter now works correctly when Single Sign-On (SSO) is enabled for your system.
• The Add a User link located on the Search Results page of the Web Administrator now correctly opens the Add User page.
• Performance improvements have been made to Folder fields that contain a large number of values.
• Sub-Relational field values that originate from a Text field that includes HTML tags are now updated on transition forms. In previous versions, these values were not updated until a transition was completed.
• The Active/Inactive option is now available on the Global Search page.
• The error message: "you have no submittable projects" no longer mistakenly appears when you click Browse and Submit to a Project even though you have submittable projects. The submit tree will now display as expected.
• Users no longer receive an error when they select the Show a Trend line for All Items in This Application check box when they preview a Backlog Trend report. In previous releases, this error occurred when the Submit Date system field is not included in an application. Beginning with this release, this check box is not available to users if the Submit Date field is not used in the report's application.
• File names are no longer corrupted for files downloaded if the file names included double-byte characters.
• Trend reports that query on a start date of the beginning of one month no longer return incorrect results for the remaining months in the results.
• Alignment problems for Text fields and labels have been solved.
• Users created via promotion will now see the Quick Links folder in the Favorites view when accessing the Web interface. Promoted users will now also see System Folders (Inbox, Submitted Items, Transitioned Items, Updated Items, IDE) in the Favorites view if Auto Folder Items is enabled. Additionally, these folders will always be created when calling the API function TSUserAdd regardless of the value specified for the nPersonalFoldersFlag parameter. This fixes an issue in which the Quick Links and System Folders were not created for newly-promoted users.
  Note: Only the Quick Links folder is brought over on promotion. The actual quick links themselves are not.
• Drill-down links may not appear in Distribution report results if the report specifications contain a high number of values in the search filter. If links are not available on the drill-down report, simplify the report specifications on your originating report.
• The Exit link on the Relational Field pop-up window has been replaced with a Close link. In previous releases, users received errors when clicking the Exit link on these pop-up windows.

• "1/1/1970 9:00:00 AM" is no longer automatically filled in in the Default Value field when you add a Date/Time field.
• The duplicate workflow feature is now enabled when you right-click a workflow in Mashup Explorer.
• Mashup Composer no longer fails to launch when .NET 3.5 SP1 is installed on the same machine.
• There is no longer inconsistency between a mashup that was exported to file and then imported from local file.
• Mashups no longer fail to deploy if they contained auxiliary tables that were deleted, and role privileges were set for the deleted tables.
• Name changes made to application elements, such as workflows, states, transitions, and forms, are now propogated to a corresponding orchestration mashup tool.
• Mashup Composer can now handle mashups that use WSDL files that have references to XSD files.
• Mashup Composer now checks syntax during script validation.
• You can no longer change the style of a numeric field after deploying a mashup. However, you can change the Digits Displayed After the Decimal Point value with no adverse effect.
• Mashup Composer no longer crashes when you have a state with height or width of "0" in a workflow.
• Mashups with circular-type references can now be imported.
• When Application Workflows is selected in Mashup Explorer, the Created On and Updated On values are now displayed with the local time and date, instead of GMT (Greenwich Mean Time).
• Mashup Composer no longer allows you to select non-integer Numeric fields as fields to sum for Summation fields.
• The default horizontal alignment for a Combo Box changed from Center to Align Left, so the width of a Combo Box now adjusts to the length of its content.
• A state that was deleted in a workflow now appears as deleted in a sub-workflow.
• You can now publish a mashup when an ampersand (&) is included in the Data Mapping tab of the Property Editor for an orchestration workflow.
• The styles used by quick forms and custom forms based on quick forms are now the same.
• The content of a Combo Box is no longer truncated when the alignment is set to Autofill.
• The Repository functions on the Home tab Ribbon now work correctly.
• You can now see and select child workflow transitions when creating a transition action or trigger.
• The Post table is now always set for Copy transitions in applications workflows that are imported into Mashup Composer, preventing the mashup containing the workflow from validating. This typically occurs in workflows that were upgraded from a TeamTrack system.
• The Hide Button on Form check box is now disabled and cannot be selected for the default system Update transition.
• The check boxes on the Dependencies tab of the application workflow editor now remain in place when you select or clear check boxes in the Restrict dependent fields section.
• When you change a column width on a form to a percentage, the other columns change to similar percentages instead of random percentages.
• New data fields now appear in orchestration workflows after you reimport an external WSDL file.
• After you delete a state from a parent workflow, the same state in a sub-workflow now appears deleted.
• Fixed height changes made to Text/Memo fields on custom forms now appear the same in form preview and in the Web interface.

• Problems with complex expressions that were causing deployment failures have been fixed. This issue affected the Expression section of the Calculate step, the Rule section of the While step, the Source section of the ForEach step, and the Rule section of non-Otherwise Branches in the Decision step. Orchestration workflows that contain any of these sections where operators and functions are used, such as Multiply or Divide, can now be deployed.
• You no longer have to use the NUMBER() function to cause numeric variables to behave as numbers. For example, the array element access array[intVariable] now works.
• Accessing an array that is embedded in an expression no longer causes a deployment to fail. For example, the function CONCAT(array[index], "xyz") now works.
• Orchestration workflows containing branches that use working data of complex type no longer fail at runtime. For example, the branch of condition ForEach.item="one" now works.
• A mashup can now be imported if default values are used for date fields in orchestrations when regional settings other than United States regional settings are used.
• Orchestrations no longer fail if you change the display name of a field in the primary table and that field has been used in an orchestration workflow.
• Subsequent imports of mashups no longer fail if a message name is changed in a WSDL included in the mashup.
• The XPath function SUM(), which appears in the Function menu of the orchestration workflow Property Editor, now works as expected and can be used to add the values of a numeric array to obtain the sum of those values.
• This item applies to expressions in the following areas: the Expression section of the Calculate step, the Rule section of a Branch in the Decision step, the Rule section of the ForEach step, and the Source section of the While step. To increment the value of the numeric type data element item, use item+1. You can also use item or item+1 as an array index. For array indexes, you no longer need to use the XPath function NUMBER(), as in NUMBER(item), NUMBER(item)+1, or NUMBER(item+1).
• SUBSTRING functions are now stackable in orchestration workflows. For example, the following expression is valid: SUBSTRING(SUBSTRINGAFTER(EventNotice.Extension.Title, "R") , 1 , 11 ).
• External event authorization no longer fails if the password contains the UTF-8 character Љ.
• You can now use orchestration workflows if no Internet connection is available.

• The BPEL generator in Mashup Composer now generates the correct XPath expression for attributes and elements in WSDL and schema files.

• When you invoke a Web service operation that does not require input, for example, if you invoke the Application Engine Web service's GetVersion operation without mapping any input, the invocation now returns information to the orchestration workflow.

• Data is now always visible on the Roles tab in Mashup Administrator.
• An error message now appears in the HTML tab of the Settings dialog Mashup Administrator when attempting to save an entry in the Browser Title Bar that contains an apostrophe. Previously, no message appeared to indicate that a literal apostrophe is not allowed. To display an apostrophe in the Web interface, use:

  ’

• You can no longer select NT Challenge Reponse (External) as an authentication option when your system uses Single Sign-On (SSO). This option is located on the Server tab of the Settings dialog box in Mashup Administrator.
• Record locking for primary and auxiliary tables is no longer disabled each time you deploy a mashup. You should verify that this option is set correctly for each table in your system. You can do this on the Advanced tab of the Edit Table dialog box in Mashup Administrator. In addition, record locking with a 30-minute time-out setting is now enabled by default for all primary and auxiliary tables in new mashups. You can modify these default settings as needed after you deploy new mashups.
• Subtask and Post transitions now correctly use the specified Submit transition when determining if a single project is available for the submission.
• Auxiliary items updated by an action or script or imported into Auxiliary tables using the Import Data Wizard can now be viewed without restarting the Web server. In previous releases, users received errors when they attempted to view these auxiliary items if caching was enabled for the table.

• Database collation is now case-insensitive.
• If you multi-select a large number of mashups to save from an environment, Mashup Manager no longer fails to schedule the activity.
• Users no longer receive an error in Mashup Manager when SSO is enabled and the security token expires.

• Deleting a mashup in Mashup Manager now completely removes the mashup from the Mashup Repository.

  Note: Deleting a mashup does not remove it from a server to which it has already been deployed or promoted. You can undeploy a mashup to completely remove it from an environment.
• Elements such as icons, style sheets, and scripts added to forms in tables in the Global Application are no longer lost after promotion or after getting a mashup into Mashup Manager from the Application Engine.
• When you export a mashup containing an orchestration with a particular combination of working data elements, an extra working data element no longer appears when the exported mashup is re-imported.
• Mashup Composer accepts case-insensitive logins to the repository; however, logins are case-sensitive in Mashup Manager. In the past, this potentially prevented users from subsequently publishing mashups set as private from Mashup Manager if their login IDs did not match. This problem has been solved.
• Deployment no longer fails when two endpoints have the same name.
• Login IDs no longer incorrectly behave in a case-sensitive manner.
• Clearing the Server Log now opens a confirmation dialog box to prevent accidental removal of log data.
• In the Server Log, buttons no longer change position when you move the pointer over them in Internet Explorer 7.
• Warnings no longer appear in the Activity Log when you promote a mashup containing a notification subscription that references an invalid group. If the subscription contains an invalid group, the subscription is now excluded from the promotion.
• Code changes have been made to improve performance when you promote a mashup snapshot. Performance has also improved when you promote a Global Mashup snapshot that includes a large number of users.

• The ttwebservices CreatePrimaryItem method no longer fails when used as an application Web service in post-transition context.
• A Web service call containing an input object that concatenates one or more strings no longer fails if the first input object is not mapped.
• View privileges are no longer required for privilege sections that are associated with fields which are mapped to an external Web service.

• Errors no longer occur when you open the Web interface or Mashup Manager from the Start menu on the server on which Business Mashups is installed.
• Users no longer receive an "Internal Server Error" message instead of being redirected to the login screen when their session times out and SSO is enabled.

• Extraneous ALFSSO Gatekeeper errors no longer appear in the JBoss server.log file.

• In previous versions, names of user-defined strings were used as a unique identifier (UUID) in the database. This caused problems during promotion if the length of the string name exceeded 64 characters. To resolve this problem, valid unique identifiers are now generated for all user-defined strings.