Hi mrogers,
Agree and accept your comments on archiving being quite a vague term. Being more specific, can I refer to it as meaning looking to move the document from its current location to another "archive" location or outright remove/recycle/delete it when it reaches a certain age or on certain date.
Alfresco obviously provides capabilities to allow this, e.g. writing new scheduled actions based off custom fields, but my clients are always surprised when they here that it takes custom development to do a task like this, which they expect should be out of the box from an ECM product.
I know that this infringes a little on the area of records management and decolation of records which is handled by the Alfresco RM module but in a lot of cases the full RM overheads are not required and its just plain document management that's needed. I always explain that there are countless ways that people might want this implemented depending on their own processes and that there's no one "right" way that you guys could just build into the product.
In saying that though, it would be great if there was a way that simple scheduled actions could be created via the Share interface by site admins who are not developers. Something like the rules interface (which is great now) that would allow:
- a condition/conditions to be defined (e.g. created date/modified date/accessed date less than 6 months ago)
- an action to be triggered based on the existing action standard (e.g. move content to here/delete content)
- a frequency for the job to be defined (in a user friendly way, rather than a cron expression)
I think this would greatly enhance the system and allow huge flexibility without the need for experienced developers or for customisation
Any chance?
Steven
Agree and accept your comments on archiving being quite a vague term. Being more specific, can I refer to it as meaning looking to move the document from its current location to another "archive" location or outright remove/recycle/delete it when it reaches a certain age or on certain date.
Alfresco obviously provides capabilities to allow this, e.g. writing new scheduled actions based off custom fields, but my clients are always surprised when they here that it takes custom development to do a task like this, which they expect should be out of the box from an ECM product.
I know that this infringes a little on the area of records management and decolation of records which is handled by the Alfresco RM module but in a lot of cases the full RM overheads are not required and its just plain document management that's needed. I always explain that there are countless ways that people might want this implemented depending on their own processes and that there's no one "right" way that you guys could just build into the product.
In saying that though, it would be great if there was a way that simple scheduled actions could be created via the Share interface by site admins who are not developers. Something like the rules interface (which is great now) that would allow:
- a condition/conditions to be defined (e.g. created date/modified date/accessed date less than 6 months ago)
- an action to be triggered based on the existing action standard (e.g. move content to here/delete content)
- a frequency for the job to be defined (in a user friendly way, rather than a cron expression)
I think this would greatly enhance the system and allow huge flexibility without the need for experienced developers or for customisation
Any chance?
Steven
