WebSphere Lombardi Edition 7.2 > Release notes


What's changed in Teamworks 7.0.0


This release of Teamworks 7 introduces the following changes to existing features. For information about new features that have been added to this release, see What's new in Teamworks 7.0.0.


Changes in platform support

Teamworks 7.0 includes an embedded application server and does not require a third-party application server. See Teamworks Installation and Configuration Guide.


Performance Server name change

In Teamworks 7, the Performance Server name has changed to Performance Data Warehouse.


Installation and configuration changes

Each Teamworks 7 configuration includes one Process Center to which you connect the Process Servers in your test, production, and any additional environments. The following diagram illustrates a typical Teamworks 7 configuration:

Teamworks Process Center provides a central development environment and repository for multiple process authors working in the Process Center Console and other interfaces in Teamworks Authoring Environment. The Process Center includes a Process Center Server and a Performance Data Warehouse, allowing authors to build and run process applications and also store performance data for testing and playback purposes during development efforts.

The runtime environments, like the staging, test, and production environments shown in the preceding diagram, enable Teamworks users to first test and refine processes before finally rolling them out to production audiences. Using the new Process Center Console, administrators can install processes that are ready to run on test or other servers.

During Teamworks 7 installation, install the following:

One Process Center Includes the Process Center Server and Performance Data Warehouse for which you need to create and initially load databases. The Process Center installation also includes all Teamworks interfaces, such as Teamworks Authoring Environment, Process Portal, and Process Admin Console. See the Process Center Installation and Configuration Guide appropriate for your environment for more information and instructions.
One or more runtime environments Each runtime environment includes a Process Server and a Performance Data Warehouse for which you need to create and initially load databases. Each runtime environment installation also includes Teamworks Process Portal, Process Admin Console, and Performance Admin Console. See the Runtime Environment Installation and Configuration Guide appropriate for your environment for more information and instructions.
Teamworks Authoring Environment Those users who want to create process models and share work by connecting to an existing Process Center can install Teamworks Authoring Environment. See the Authoring Environment Installation and Configuration Guide for more information and instructions.

To initially load the databases for your Teamworks servers and import the System Data and other toolkits required by the Process Center, you should run the new initialization script (twinint.cmd). See Teamworks Installation and Configuration Guide.

After Teamworks installation, all Teamworks consoles (including the new Process Center Console) and Teamworks Process Portal can be accessed from your Web browser as follows:

Interface URL Provide...
Process Center Console http://[host_name]:[port]/ProcessCenter The name of the host on which the Process Center Server is installed and the port designated for the Process Center Server during installation.
Process Admin Console http://[host_name]:[port]/ProcessAdmin The name of the host on which the server is installed and the port designated for the server during installation. You can access and administer the Process Center Server or any Process Server installed in a runtime environment.
Performance Admin Console http://[host_name]:[port]/PerformanceAdmin The name of the host on which the Performance Data Warehouse is installed and the port designated for the server during installation. You can access and administer a Performance Data Warehouse included in the Process Center or installed in a runtime environment.
Process Portal http://[host_name]:[port]/portal The name of the host on which the server is installed and the port designated for the server during installation. From the portal, you can run processes on the Process Center Server or on any Process Server installed in a runtime environment.


Changes to Teamworks Authoring Environment

The Process Modeler perspective in Teamworks Authoring Environment has been enhanced and, in Teamworks 7, is now known as the Designer. The new Designer includes changes to several views and tabs as follows:


Folders and library item security in Teamworks Authoring Environment

Folders have been removed from the Library view in Teamworks Authoring Environment. Instead of folders, the library includes categories of item types, which you can click to expand and view the specific items within. You can use tags and custom folders to manage library items in Teamworks 7. For more information, see Manage the Process Center repository > Manage library items in the Designer view in Teamworks Authoring Environment Help.

Security is no longer controlled using folders. Start with Teamworks 7, Teamworks administrators can grant access to the Process Center repository as well as individual process applications and toolkits within the repository using the Process Center Console. Administrators can grant read, write, or administrative access to other users and groups. Users who are granted access to a process application or toolkit have access to all library items within that application or toolkit in Teamworks Authoring Environment. For more information, see Manage the Process Center repository > Manage access to the Process Center repository in Teamworks Authoring Environment Help.


Maintain Process Portal favorites

In previous versions of Teamworks, favorites were established for particular logical roles to configure the users who could start a process from the drop-down menu in the Process Portal. In Teamworks 7, the ability to start a process is controlled using the Exposure settings in the Overview tab in the Designer. For example, you can select a Participant Group to whom you want to expose a BPD and users who are members of that Participant Group can start the process using the drop-down menu in the Process Portal. For more information, see Modeling processes > Configure BPDs > Exposing BPDs in Teamworks Authoring Environment Help.


Logical roles

Logical roles are no longer used in Teamworks 7. Design-time access to library items in the Teamworks repository is granted in the Process Center Console per each process application and toolkit. Administrators can grant repository access to users from both the internal Teamworks security provider and any configured external security provider. For more information, see Manage the Process Center repository > Manage access to the Process Center repository in Teamworks Authoring Environment Help.

Favorites and run-time access are controlled by exposing items to Participant Groups. You can add users from both the internal Teamworks security provider and any configured external security provider to Participant Groups. For more information, see Manage Teamworks Process Servers > Manage Teamworks users in the Teamworks Administration Guide.


Changes to services

In Teamworks Authoring Environment, you can no longer create generic services. The service types available in Teamworks 7 include: Integration, Human, Ajax, Rule, and General System. The following table describes the available service types:

Integration service Use an Integration service when you want to integrate with an external system. Integration services are the same as generic services from previous releases, but without coaches, postpones, or rules. An Integration service is the only type of service that can contain a Java or Web Service integration. You can call an Integration service from any other type of service and an Integration service can call other nested services.
Human service Use a Human service when you want to create an interactive service. A Human service is the only type of service that can contain Coaches and postpones. A Human service is the only type of service that can call other nested Human services.
Ajax service Use an Ajax service when you want to include a control in a Coach to implement dynamic data selection such as automatically populating drop-down lists and automatically completing edit boxes. An Ajax service can pull data dynamically from a connected data source, such as a database. You cannot call an Ajax service from other types of services, but an Ajax service can call other nested services.
Rule service Use a Rule service when you want a condition to determine the implementation invoked. For example, when a certain condition evaluates to true, Teamworks implements the JavaScript expression that you provide. Rule services cannot include Java or Web Service integrations directly. You can call a Rule service from any other type of service and a Rule service can call other nested services.
General System Use a General System service when you need to coordinate other nested services or you need to manipulate variable data. For example, if implement data transformations or generate HTML for a coach, you can use a General System service. General System services cannot include Java or Web Service integrations directly. You can call a General System service from any other type of service and a General System service can call other nested services.

For more information, see Modeling processes > Advanced modeling tasks > Build services in Teamworks Authoring Environment Help.


Integration Definitions and Connectors

Integration Definitions, Java Connectors, and WebService Connectors are deprecated. Deprecated library items will not be supported in future releases of Teamworks. The Integration Definition and Connector library items are no longer necessary because Teamworks 7 enables you to create integrations directly in Integration services. For more information, see Modeling processes > Advanced modeling tasks > Integrate with other systems in Teamworks Authoring Environment Help.


Changes to reports and scoreboards

Because Integration Definitions, Java Connectors, and WebService Connectors are deprecated, use new Integration services as data sources for reports. In previous versions of Teamworks, you could control access to your reports and corresponding scoreboards by setting the Access Control on the folders where your scoreboards resided. In Teamworks 7, you can use the Expose to setting for each scoreboard that you create to establish the participant group whose members can access reports and scoreboards.

You can control access and otherwise configure the standard out of the box scoreboards as follows:

Scoreboard Access Configuration
My Performance By default, this scoreboard can be accessed in Teamworks Process Portal by members of the All Users participant group. (The following note describes how to change members of this group.) No further configuration required.
My Team Performance By default, this scoreboard can be accessed in Teamworks Process Portal by members of the Managers participant group. (The following note describes how to change members of this group.) To establish a team hierarchy for this report, an administrator can use the Team Manager Group setting in the Process Admin Console. See Manage Teamworks users > Manage group membership in Teamworks Process Admin Console Help.
Process Performance By default, this scoreboard can be accessed in Teamworks Process Portal by members of the Process Owner participant group. (The following note describes how to change members of this group.) To establish the processes for which this scoreboard should display data, use the Expose performance metrics setting in the Overview tab for each BPD. For more information, see Modeling processes > Configure BPDs > Exposing BPDs in Teamworks Authoring Environment Help.
SLA Overview By default, this scoreboard can be accessed in Teamworks Process Portal by members of the Process Owner participant group. (The following note describes how to change members of this group.) To establish the SLAs for which this scoreboard should display data, use the Expose setting for each SLA.

From the Installed Apps area of the Process Admin Console, a Teamworks administrator can change the members of the All Users, Managers, and Process Owner participant groups on any runtime Process Server. To do so, administrators can select the current snapshot of the Process Portal process application, select the Role Bindings option, and then adjust members

...in Teamworks Process Admin Console Help.


Sending definitions to the Performance Data Warehouse

In previous releases of Teamworks, you could send definitions to the Performance Server from the Process Admin Console. In Teamworks 7, the Send Definitions page is not included in the Process Admin Console. With Teamworks 7, when you install snapshots of process applications, the Process Server in the runtime environment automatically sends new or changed definitions to the Performance Data Warehouse. If a problem occurs, and definitions are not sent during snapshot installation, you can send definitions after the snapshot installation completes

...in Teamworks Process Admin Console Help.


Enhanced JavaScript API

In order to consolidate all primary functions into a consistent interface, the JavaScript API now includes functionality previously found only in the Web API and EJB API. The enhancements ensure that process authors and developers have a consistent JavaScript API to use within their processes. New objects have been added to support the new features of Teamworks 7. Plus, existing namespaces have been expanded with objects that provide greater flexibility and control. For example, several new objects enable developers to gather information about and control run-time instances of processes.


Changes to calendars

In Teamworks 7, Work Schedules replace Calendars. However, Work Schedules are not library items in Teamworks Authoring Environment and they are not associated with users and groups. Instead, Work Schedules are set on BPDs (in the Overview tab) and for activities (in the Implementation tab). Work Schedules include options for time schedule, time zone, and holiday. For more information, see Modeling processes > Basic modeling tasks > Implementing activities and Modeling processes > Configure BPDs > Set the work schedule for a BPD in Teamworks Authoring Environment Help.


Custom priorities

In previous releases of Teamworks, you could define custom priorities for activities within your BPDs. For Teamworks 7, there are no custom priorities. All priorities are now one of five established levels: Low, Normal (default), Urgent, Very Low, Very Urgent. In Teamworks 7, you can use process variables to handle implementations that require custom priorities.


Global variables

Global variables are no longer available and are not supported in Teamworks 7. Most uses of this feature can be achieved by using process data with business data search.


Time-based Undercover Agent (UCA)

Time-based UCAs are no longer available and are not supported in Teamworks 7. Scheduled UCAs are different and are still available in Teamworks 7. Time-based UCAs provided a way to create one-time events, which can now be done using a process with a timer.


Discontinued and deprecated service components

The following components are either modified, deprecated, or no longer available in the palette when building services in Teamworks 7. Deprecated components will not be supported in future releases of Teamworks.

Component Status Description
Integration Component Deprecated In Teamworks 7, use new Java and Web Service Integrations instead of Integration Components
Modify Task Modified Modify Task no longer includes the following Task Modifications: Category and Custom Status; plus Postpone Task is now a separate service component
Browser Script/Browser Script Layout Removed Browser Script is no longer available in the service palette and is not supported in Teamworks 7
Coach Form/Coach Form Layout Removed Coach Form is no longer available in the service palette and is not supported in Teamworks 7
Send Task Removed Send Task is no longer available in the service palette and is not supported in Teamworks 7
Coach v1/Coach Layout Removed Coach v1 is no longer available in the service palette and is not supported in Teamworks 7
Send Alert v1/Alert Layout Removed Send Alert v1 is no longer available in the service palette and is not supported in Teamworks 7


Dates stored in server local time

Dates and times that were previously stored using a combination of Coordinated Universal Time (UTC)/GMT and server local time are now stored exclusively in server local time. For example, Teamworks stores data about running process instances in the Process Server database. In previous releases of Teamworks, the dates and times were stored using a combination Universal Time (UTC)/GMT and server local time. Now all dates are stored exclusively in server local time. This is also true for dates and times stored in the Performance Data Warehouse.


Teamworks for Organization Management

Teamworks for Organization Management is not available in Teamworks 7.0.


Teamworks for Office and Teamworks for Sharepoint

Teamworks for Office and Teamworks for Sharepoint are not available with the initial release of Teamworks 7.0.

+

Search Tips   |   Advanced Search