Workspace name | Feature reference # | Feature name | Feature type | Feature description |
---|---|---|---|---|
Digital Workspace Platform | Emails as Push Notifications | New | Overview Real-time push notifications not only grab the attention of the users but also gives an urgent call-to-action, which may trigger instant action from the user, like reacting on System e-mail, Reacting on Approval request, etc User Problem Today, it is possible to send and receive Push Notifications only at Matrix42 Mobile Applications. However, it is much comfortable to receive them in Browser as well (UUX) In addition, having system notification shown the only Mailbox, sometimes produce delays with reaction Target Group End Users MVP The User is able to configure receiving System Emails as Push Notifications in addition to Emails, at User Profile When the option selected, User will be notified with Standard Browser Push Notification about new message, and will be able to review details when clicking on it also, Push Notifications that today can be sent by Workflows using Push Notification activity will be shown the same way |
|
Digital Workspace Platform | Running Engines in a sequence | New | User Problem Engine activations conflict with each other when execution takes a lot of time, and it is not possible to configure execution in a sequence Target Group Administrators It is possible to configure a dependency between Engines configured within a single Engine Activation object, in order to start some engines only after the dependent engine finished processing. Only the Engines which provide a mechanism of detecting the "done" event are allowed for setting the dependency. Engines Example of "Done" event:
Each Engine has to implement a special Interface in code (e.g. IEngineCallback) which signals the Engine supports the dependency execution configuration. Otherwise (interface not implemented) the Engine cannot be defined in sequence. The Engine Preview page provides information about the supporting execution sequences. All the default Engines shipped in DWP support the sequence definitions. Mockup: Adding a new Engine to Activation Validations:
Mockup: List of Engines in Activation By default sorted in execution order. Usecases Usecase 1 - Engine Activation for series of Engines
Usecase 2 - Running Engines from Engine Activation
Usecase 3 - Running Engine Activation when the previous one is in progress
Out of Scope All Engines that are not part of DWP needs to be updated to support running in sequence |
|
Digital Workspace Platform | Import Definitions support Cloud Data Providers | New | OverviewImport Definition supports processing files from the direct link to Cloud Data Providers (Google Drive, One Drive, Dropbox, etc), is able to authenticate when the file is secured. In the end, it is possible to execute such Import Definition on a regular base using Engine Activations, and in case of the file content will be changed - changes will apply User Problem: Today with Import Definition users are able to import files when they are stored locally or in the network share. However, it is not possible to observe non-local files what is especially important in the case of Cloud Offering (without extra efforts), especially needed for regular imports Target Group Services, Partners, Customers Value Proposition To increase Integration possibilities for DWP low code platform MVP It is possible to configure Import Definition for regular import at least from several cloud providers like One Drive, DropBox, and GDrive "Import Definition" ConfigurationThe Administrator on the "Import Definition" authoring is able to define "Cloud Drive" as a Source for import. In that case, the System requires to define the active "Service Connection" object which provides the connectivity for the Target Cloud Drive Provider, and the "File Path"
Use CasesUse Case - Import publically available CSV, XLS, XLSX files from the web
Use Case - Import a secured CSV, XLS, XLSX files from the web
Use Case - Import a secured XLSX files from the Box.com on a regular basis
|
|
Digital Workspace Platform | "Push Notification" from Workflow Studio | New | Overview Real-time push notifications not only grab the attention of the users but also gives an urgent call-to-action, which may trigger instant action from the user. It is possible to send Push Notification to users from Business Processes instead of Emails using Send Push Notification Activity User Problem Today, it is possible to send and receive Push Notifications only at Matrix42 Mobile Applications. However, it is much comfortable to receive them in Browser as well (UUX) Target Group Services, Partners, Administrators MVP The User is able to configure receiving Events as Push Notifications, at User Profile When the option selected, User will be notified with Standard Browser Push Notification about new message, and will be able to review details when clicking on it Push Notifications from the Workflow can be configured using Push Notification activity That has been used in the past |
|
Digital Workspace Platform | Service Connections | New | OverviewService connections enable you to connect to external and remote services to execute tasks in a job. For example, you may need to connect to your Google Drive to import Tickets that are collected with some google form, or use REST API in the Workflow Studio Activity like HTTPSend. User Problem: Today, it is way too complex to configure and maintain connections to 3d parties. Also, there is no way to make a request, without knowing credential, that the user is not allowed to see Target Group Services, Partners, Customers Value Proposition To increase Integration possibilities for DWP low code platform MVP It is possible to configure Service Connection at least from several cloud providers like One Drive, DropBox, and GDrive that can be used in Import Definitions and Workflows A new System Configuration Item "Service Connection" keeps and maintains the information needed to set up the connectivity with the various external Services. In the final implementation, Service connections support different Authentication types, like OAuth, Basic Auth, API Token.
For an easy configuration of the Service Connection the System out-of-the-box provides the predefined configurations to the most popular Identity Providers:
* The custom configuration can be added OAuth Flow In MVP Service Connection support only OAUTH authentication Type. On Service Connection creation the System redirects the request to the target OAuth provide and on response persists the encrypted "Access Token" and "Refresh Token" in the database Automatically Update OAuth Access Token The System automatically tracks the Service Connection Token Expiration and refresh the token over the OAuth refresh Token Mechanism HTML Client API The System provides the API for an easy way of using the Service Connection on preparing the Request Service Connection Public API The System provides a Public REST method for the creation of the Service Connection remotely Use Service Connection in HttpRequest Workflow Activity Introduce property "Service Connection" in Workflow activity HttpRequest, to have a possibility easily authenticate the request |