6 March 2015
Our friends at Seismi pick out their top business and technical highlights from their initial looks at the new release...
Having started our review of the new 184.108.40.206 release we thought we would highlight what we anticipated to be the most valuable from both a business and technical perspective. The full list of features is available here. From a business perspective some of the most notable features are:
- Conditional Workflow Stages – A workflow model can be configured to conditionally alter the workflow path for individual requests. You can include or exclude particular workflow stages depending on whether request items have certain property values or if they fail certain validations. You can also separate request items that require different approvers and split enrichment tasks into different requests to follow separate workflow paths.
- Separation of Duties – You can configure workflow stages to require a separate approving user who has not submitted or approved for any other stage in the request.
- Request Items from File – Request items can be loaded into a workflow request from an external flat file created by a user or source system. You can load request items during a Submit or Enrich stage. Source files may be loaded using the Web Client or Batch Client.
From a technical perspective the following three have real potential:
- Improved Architecture – Data Relationship Management offers a streamlined application server architecture optimized for single machine, multi-processor deployments on 64-bit hardware. Each application utilizes a single engine and server, instead of the multiple engine and server configuration used in previous releases. These improvements result in higher concurrency of read operations, eliminate event traffic between engines, and reduce connections to and data transferred from the repository.
- Reverse Lookup on Import – Lookup type properties can be selected for import section columns to perform a reverse lookup on column values being imported. The resulting value is stored in the defined property that uses the lookup property.
- Hierarchy Groups in Exports – Hierarchy groups can be used to auto-select hierarchies for exports instead of having to manually select the hierarchies for each export. Each export profile is configured with a hierarchy group property and hierarchy group. When a hierarchy is assigned to a hierarchy group, the hierarchy becomes immediately included in all exports using the group.