Release Version 4.2
Objective 3Sixty releases delivers a host of exciting new features and brings several enhancements.
Installation/Update Requirements
4.2.7 Hot Fix
Resolved Issue
|
Component |
Description |
|---|---|
|
Alfresco Connector |
Resolved the issue where running errors on SharePoint Online to Alfresco MIP job skipped the content rather than process it. |
4.2.6 Service Pack
Resolved Issue
|
Component |
Description |
|---|---|
|
SharePoint Connector |
Resolved regression connecting to SharePoint On Premise with Basic Authentication using NTLM. |
4.2.5 Service Pack
Resolved Issues
|
Component |
Description |
|---|---|
|
Centera Connector |
Centera Clip Migration Issues: The JDBC connector will now have a field called Minimum Pool size when used in jobs. This will dictate the minimum size of the pool for each connecting threads. Lower values are preferable as they put less strain on the source/target database. |
|
Scheduled Jobs |
The Scheduled Jobs not Starting after Application Restart issue has been fixed. |
4.2.4 Service Pack
Resolved Issue
|
Component |
Description |
|---|---|
|
Audit Exports |
Fixed a bug where download and exports would not Stop/Delete correctly. Audit Exports will now work as expected. They will no longer hang and can now be removed. |
4.2.3 Service Pack
Resolved Issues
|
Component |
Description |
|---|---|
|
Clustering View |
Fixed: clustering view gives 500: entity content is too long for the configured buffer limit |
|
Post Processors |
Removed configuration fields that were not needed for the post processor to function properly |
|
Run and monitor Jobs |
3Sixty job no longer hangs based on large volume record count |
|
Google Drive |
Fixed: Fail to transfer documents from google drive to Alfresco Fixed: 403 error for schema instance |
|
Text Cleanup Task |
Fixed: Document Cleanup step replaces Spaces with value True |
User Guide Updates
|
Component |
Description |
|---|---|
|
Google Drive Versioning |
Get versions only works for exportable google documents, like google docs. For documents that are uploaded to google drive, get versions will not work. |
|
Google Drive JWT |
If using a JWT of service account, the service account email needs to be added as a member of Shared drive and be given Manager role. |
4.2.2 Service Pack
Resolved Issues
|
Component |
Description |
|---|---|
|
Unzip Task |
This task has been updated to work more efficiently. It will now send the documents directly to the output connector. Unzip Task |
|
Clustering Widget |
This feature has been updated to handle backslashes that may be included in the document ID. Clustering TagsWidget |
|
Nexus Document Count |
Issue resolved to correct the document count in some instances. The read count will now match the written/error/skip/removed count |
|
MongoDB Query |
Issue resolved that was preventing 3Sixty from properly handling null or empty queries |
User Guide Updates
|
Component |
Description |
|---|---|
|
Widgets |
The list of available content view widgets has been updated. More detail and examples have been added where needed. Widget Definitions |
|
HTTP Task |
The purpose of this task is to execute a GET or POST HTTP call for each repository document. If the status is any of the following, then processing will continue, if not, the document will be skipped. |
|
Objective Connector |
Passthrough authentication currently only works for ECM content service: - Objective Basic Authentication Connector: passthrough username and password |
|
Centera Connector |
Details of how to configure this connector has been added to the user guide. Centera Connector |
|
Azure Blob |
Added clarification for Number of seconds for each attempt to upload field "Must be between 1 and 2147483647." |
4.2.1 Service Pack
Resolved Issues
|
Component |
Description |
|---|---|
|
HTTP Task |
Updates made to the configuration steps. HTTP Task |
User Guide Updates
|
Component |
Description |
|---|---|
|
HTTP Task |
Updates made to the configuration steps. HTTP Task |
|
Trivial Task |
Additional information added to the example. Trivial Detection Task |
|
Processors |
Inconsistencies updated to more accurately reflect the UI. Pre-Processors |
|
Duplication Detection |
Documentation updated to provide more useful information. Duplication Detection Task |
4.2.0 Feature Release
Upgrade Instructions
For the new clustering feature users will need to make the following changes to the Global Properties file:
1. set simflofy.initialize.update=true
2. set simflofy.initialize.bootstrap=true
New Features
|
Component |
Description |
|---|---|
|
New Clustering Content View |
This new view will group content by tags giving users a visualization of their data. Users can drill into the groups for more detail. Clustering Content View |
|
New URL Encoder Task |
This task encodes URLs for a given field. URL Encoder Task |
|
New URL Decoder Task |
This task decodes URLs for a given field. URL Decoder Task |
|
New HMAC SHA-256 Generator |
This task calculates HMAC-256 hashes for files. HMAC-256 Genrator Task |
|
New File System Rename File Post Processor |
This task will rename files once they are processed. Rename File Task |
Enhanced Features
|
Component |
Description |
|---|---|
|
Azure Blob Connector |
Will now support object headers as well as perform MD-5 integrity checks. Azure Blob Connector |
|
Basic JDBC Task |
The Basic JDBC Task can now save result case-insensitively. Basic JDBC Task |
|
MongoDB Query task |
This task now supports multiple fields and will allow users to sort the order in which the fields are checked. Join Mongo Document Metadata |
|
Hash Value Generator Task |
The Hash task can be used to buffered hash calculations and safely skip files beyond a given size. Hash Value Generator Task |
|
Discovery Report Colours |
The colours in the Discovery Reports have been updated from red to green for better clarity |
User Guide Updates
|
Component |
Description |
|---|---|
|
Size limits for the Objective Connector |
Detail has been added about the size limits for chunked uploads. Objective Connector |
|
SharePoint Graph guidance |
SharePoint Graph probably should only use OAuth for migrations. For Content Services, use the key/secret connector because it can automatically refresh the token. SharePoint Graph Connector |
|
Elasticsearch Guidance |
Elasticsearch needs to be configured to handle larger files by setting http.max_content_length to a value greater than 100MB |