Version 2.0

Monitoring and Notification of Failures

Monitoring is an essential part of any integration project. When you use Atomic Scopes exception handling blocks, an immediate notification will be sent when there are errors in business transactions. AtomicScope uses SMTP server configuration to send alerts in a form of an email to people who need to know about transaction issues. Below is the sample notification email.

User Access Control

In version 2.0 we brought in windows authentication for the users to be able to log in to atomic scope portal. Once the user is authenticated, role-based user access policy controls the level of access a user has gone on the workspace and business processes.

Roles at the Workspace level

There are two roles at the workspace level.

• Workspace User – User can access the business processes within a workspace
• Workspace Owner – User can make changes to the workspace like adding users/ deleting workspace etc.

Roles at Business Process Level

• Business Process User – User can access the business process and edit the business process to which they have access to.
• Business Process Owner – User will be able to edit, delete and add users to the business process.
• Business Process Reader – User can view the business process but won’t be able to make any changes.

Purging Policy

This feature brings the capability to configure a number of days you want to retain the data in atomic scope database. By default it is 30 days, however, you can change it by modifying the application settings as shown below.

Provision for De- Batch Correlation

Message de-batching is very common in integration scenarios. When a batch message is received into BizTalk environment de-batching can happen in receive pipeline or in orchestration.

Version 2.0 brings the following abilities.

1. Ability to log the batch message into the main activity.
2. Ability to archive the batch message
3. Ability to link all the de-batched messages to their parent batch.
4. Ability to allow de-batched messages to progress with their individual journey.

Dynamic transaction resolution

In Atomic Scope, to track activities in BizTalk pipeline we will have to specify the transaction name at runtime as shown below.

Consider a scenario where a single receive location receives different message types and each message type corresponds to a completely different transaction in a business process. For example, you can receive Orders and Delivery confirmation on a single receive location.

Consider another scenario where you receive a batch of different transactions from a trading partner through a single receive location. In both the scenarios, configuring transaction name during design time will not work. We should have an option to dynamically find out the transaction name based on BizTalk message type. Dynamic Resolution Of Transaction feature supports above scenarios by allowing the users to map message types with transaction names.

UI improvements

We always care about user experience. In this release, we improved various aspects of it. We are excited to introduce a brand-new Business Process configuration page, as well as a tabbed view for searching the tracking results.

Configuration based Tracking with Logic Apps

This feature enables you to configure the tracked and search properties for stages executing at Logic Apps.