AlfStream Change Log

This is the change log for Parashift's Alfstream Module

All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning.

[1.10.1] 2017-09-07

Fixed

  • Can't create site correctly if the same name site has been created on its counterpart

[1.10.0] 2017-08-22

Added

  • Ability to sync out multivalue fields

[1.9.1] 2017-07-14

Fixed

  • Empty String values are now synchronised across again (prevented site synchronisation with an empty description)

[1.9.0] 2017-07-04

Added

  • Ability to include path on the consumer to specify only nodes below a certain path. Will recursively search down using an SQL query.

[1.8.3] 2017-06-29

Fixed

  • New created group can't be synced across correctly

[1.8.2] 2017-06-26

Fixed

  • Synced user doesn't have correct email address with its counterpart
  • Folder path is not parsed properly, which causes the creation of folder with empty folder name
  • When get properties of a node before updating, the value of property is not checked, which causes the attmpt to convert an empty value

[1.8.1] 2017-05-25

Fixed

  • Type cm:failedThumbnail is added to exclude node type list and will not be synced between instances

[1.8.0] 2017-05-19

Added

  • Ability to handle User and Group sync

[1.7.1] 2017-03-08

Fixed

  • Some clients don't provide the correct mime type when submitting an update, the update webscript will now try and guess this

[1.7.0] 2017-02-23

Added

  • Tags are now included and readable via the consumer (no support for producer)

[1.6.2] 2017-02-06

Fixed

  • Modify the version label update logic, when there is a change in regards to version label, the new version will be created for the node, otherwise, disable the versionable aspect behaviour to prevent update content method automatically increase the version label, which causes the faulty increment of version label

[1.6.1] 2017-01-16

Fixed

  • Check-in/Check-out document can't be synced correctly, the following behaviours are added:

  • In Alfresco instance A, click Edit Offline button against document, the corresponding document in Alfresco instance B will be locked

  • Click Upload New Version or Cancel Editing in Alfresco instance A will unlock the corresponding document in Alfresco instance B
  • In Alfresco instance B, you can only Unlock document, which will unlock its counterpart in Alfresco instance A and cancel checkout for working copy to avoid duplicate document
  • Working copy of document will not be synced between instances

[1.6.0] 2016-12-21

Changed

  • Use a SHA-1 Property hash instead of modification date to check against the following properties for changes:

  • Version Label

  • Lock Type
  • Modification Date

  • Use a SHA-1 for the permissions hash instead of MurmurHash to avoid collisions

[1.5.1] 2016-12-15

Fixed

  • Non-UTC timezones now sync correctly

Changed

  • Don't throw an exception if the date cannot be parsed

[1.5.0] 2016-12-09

Added

  • Adjustable timeout parameter (in ms) for consumer connections, with a default of 5 minutes.
  • Persisted transaction and acl change ids as specified by the persistFile parameter.

[1.4.5] 2016-12-08

Changed

  • No longer syncing folder rules to prevent update exception

[1.4.4] 2016-12-07

Fixed

  • Returns a zero length array if there are no aspects present in the database.

[1.4.3] 2016-11-30

Fixed

  • UTF-8 Characters now display correctly

[1.4.2] 2016-11-25

Fixed

  • Sync control can only stop one way sync rather than two way

[1.4.1] 2016-11-22

Added

  • Version label sync
  • Document linkings and shortcuts sync (UPSERT only for shortcuts)

Fixed

  • Delete event can't be synced

[1.3.0] 2016-11-15

Added

  • Sync control by using actions in document library
  • Locally set permissions sync

[1.2.3] 2016-11-07

Fixed

  • Only standard data types are serialised out for compatibility with MM

Changed

  • Combined Repo, Camel, readme & changelog into the one project

[1.2.2] 2016-10-11

Fixed

  • Aspects are removed/created regardless of whether properties exist
  • Peer Associations are added correctly to allow for locking/unlocking

[1.2.1] 2016-10-07

Fixed

  • Fix for comments on documents

[1.2.0] 2016-09-16

Added

  • Include Site as a default property

Fixed

  • Long type variables are converted correctly

[1.1.0] 2016-04-17

Added

  • Ability for different types beyond cm:content
  • Aspect Filter for the getNodes webscript

Changed

  • Only disabled auditable aspect behaviour to allow other behaviours to function

[1.0.0] 2016-03-30

Initial Release