New

New data-triggered actions are available to improve data completeness, consistency, and productivity by automating data maintenance tasks​. Actions to create, edit, and delete assets, trigger workflows, or import/export data can be automatically triggered via rules configured by an administrative user. For example, an end date for an application may be set based on the definition of its start date, or an approval workflow may be triggered when a new application is created.

A new Data-Triggered Actions functionality is available in the Configuration section of the navigation panel for the Portfolio Admin user profile. Data-triggered actions may be based on SQL queries to define UPDATE rules or on existing event templates that allow specified events to be automatically triggered in the background. SQL queries may be specified to define the data conditions that must be met in order to trigger the action.

The data-triggered action capabilities can be accessed by users with the base package IT Transformation Server - Enterprise.

Data about peripheral applications that are outside of the core scope of the IT landscape can be captured in the new Capture Peripherals data workbench and content area. A peripheral typically represents an application that is managed by business partners, such as an EDI gateway or a B2B marketplace. Peripherals are connected to applications in the IT landscape by means of information flows. In contrast to an application, a peripheral’s local components or business services as well as the details of its technical platform are not relevant to the IT landscape. The business question What is our application roadmap? has been extended with a filter to include peripherals in the analysis.

Peripherals can be captured and analyzed by users with the extension package Enterprise Architecture Management.