Contents
SmartOps 7.6 introduces new features and enhancements across SmartOps Orchestration, Packaged Product Enablers and Integrations.
The release is enabled with enhancements to SmartOps Orchestration (Automation Story) through APIs to fetch Workflow details corresponding to Automation Story and fetch all Automation Stories based on different combinations. In addition, release also provides enhancements to Automation Story – rendering and notification framework built to support notification channels.
SmartOps 7.6 release also focuses on “User Data Store” which is a platform component that stores user information as well as application specific information inside the SmartOps platform databases. With 7.6 release, user data store will be capable of performing certain basic operations. The release also focuses on enhancements to Design Studio enabling personalization of Micro Actions in Design Studio and PWF and Rule Engine enhancements.
RHub is enhanced with the capability to synchronize adapter configurations thereby enabling adapters to update the configuration changes without restarting.
PaaS/ Multitenancy feature is enabled with the provision to reserve capacity for batch/asynchronous processes at organization or custom levels.
Release 7.6 includes the following enhancements to "Automation Story".
API to fetch workflow details corresponding to Automation Story, based on different conditions such as Session Id, Automation Story and a Flag (To enable user access check, whether workflow details need to be fetched based on user access to workflow).
API to fetch all Automation Stories based on different combinations - Provision to get the AS names in an organization based on given conditions such as Tags, PWF type, Project ID etc.
Enhancement for Automation Story rendering:
State Management in Workflows - A new micro-action is introduced to enable saving certain fields as part of session, so that it will be available throughout the life cycle of an Automation Story. User can add fields and values in the micro-action so that they gets saved to the Automation Story session. This can be achieved using:
Microaction for Session Update
Microaction to Clear Entities from Session
Save ending MicroActions from back end - During Workflow save/update, for the Microactions which are actually ending Microactions (those Microactions where output connectors are not available) but not explicitly set from UI, will set them automatically as ending Microaction from backend.
In 7.6 release, Notification Framework is built to support notification channels.
New framework can be used by applications running on the platform to send notifications to other applications and users. Notifications will include system alerts, batch processing updates, and application-specific information.
The framework allows to send notifications to users via different channels. The framework also provide provision to pull alerts specific to a user.
Option for users to subscribe/unsubscribe to notifications (user preferences) is enabled. Subscription to notification will be supported at user/group levels.
Notification Framework In-App Microservice In-App Microservice is a component that exposes API for UI applications to get notifications. The In-app microservice shall provide following interfaces:
Interface to push notification into the mongodb storage - This shall be integrated with RHub Flow. So, the queue listener adapter can invoke this API.
Interfaces to get notifications - This interface shall be invoked by UI applications.
Interface to delete/expire/make status as read notifications.
User data store is a platform component which stores user information as well as application specific information inside the SmartOps platform databases.
With 7.6 release, user data store will be capable of performing certain basic operations such as:
Update/Delete user details.
Register application.
Add/Edit/Delete application specific details
Get user details
Get app registration details.
Get Application specific details
Personalization of Micro Actions in Design Studio - Provision to Mark/Unmark a MicroAction as favorite in all MA cards.
SmartOps 7.6 release provides following PWF enhancements:
UI: Grouping and Ordering in Master Configuration Listing Screen (Master Specific) - This feature will bring about enhancements to the master specific master configuration listing screens.
Introduce grouping in the UI, based on configuration group names
Manage the order of groups and fields within group
Provision to de-associate a Role from a User against a Project (Admin)
In master project configuration screens, checking for cyclic dependency and no check for display order or group step number of dependencies. These procedures are automated as part of this enhancements.
In this release, changes are introduced to make automatically read the package and class name from the DRL or Excel rule file and use it for rule creation. Users do not have to provide this information manually.
Facility to specify timeout for rule execution is introduced. Rule file can be downloaded for editing.
User can now integrate rule engine with RHub by providing RHub instance and RHub URL in the rule detail screen.
Synchronize Adapter Configuration – Previously, for reflecting the configuration changes, adapters were required to be restarted. As a solution to this problem, the new feature is developed to listen to the Zookeeper instances and update the configuration changes for the adapters (that is, synchronize the configurations from Zookeeper to respective adapters).
Reserved Capacity - Provision to reserve capacity for batch/asynchronous processes at organization or custom levels. This can be used by applications to offer guaranteed performance in our multi-tenant PaaS through dedicated instances for critical components. This feature will be used in SmartOps orchestration and SmartVision in the coming releases.