topic Re: We need to work with alfresco content but we want a confirmation that it is supporting the following points: in Alfresco Forum

We need to work with alfresco content but we want a confirmation that it is supporting the following points:

ahmedhabib — Sun, 02 Jun 2019 13:45:23 GMT

Are we can make the content meta-data customized?Are we can build a custom predefined workflow with a specific human tasks steps, and show it for the user that wants to start a workflow on a content?Are we can integrate the alfresco application with a scanner to be apple to scan and upload file dire

Re: We need to work with alfresco content but we want a confirmation that it is supporting the following points:

afaust — Mon, 03 Jun 2019 10:10:24 GMT

Without any additional information / context / specifics on your requirements, I can answer all points with a resounding YES.

Custom metadata => bread and butter of an Alfresco project
Custom workflows => Alfresco currently includes Activiti engine, but it is planned that this may be removed at some point in the future. Depending on the complexity of the planned process, you may still do this using the embedded engine, or want to consider using a companion process application. If you are considering Alfresco Enterprise (paid commercial variant), you have the option of using Alfresco Process Services, otherwise you can look at Activiti, Flowable, Camunda (and others) as open source applications...
Integration with scanner => Always depends on the scanner in question and what your specific requirements for the integration are. For Alfresco Enterprise, there is / used to be an Kofax integration module. By using Alfresco WebDAV / FTP capabilities, any device capable of handling those protocols can file documents to Alfresco (without metadata in this case), and any device capable of handling CMIS can file documents and metadata.
Custom access rights / automation => Yes, within certain limitations access rights can be customised / extended. Limitations typically mean that you cannot / should not modify any of the out-of-the-box permissions, but can certainly create custom aggregates (roles). Automation is possible via behaviours / policies and folder rules.
Process metadata archival => By default, Alfresco never deletes any process metadata, so unless you actively delete data, it is already "archived" in a sense. If you want a specific archival to occur on specific sub-sets of metadata, you have to model that as part of your process - it would make no sense for Alfresco to archive all process data, since a lot of it is purely technical / of no use to business users.

Re: We need to work with alfresco content but we want a confirmation that it is supporting the following points:

ahmedhabib — Mon, 03 Jun 2019 13:58:49 GMT

Thanks for your reply Faust,

But i need to confirm on that

when i'm using alfresco process services, it will provide me the ability to build a custom process with a specific form metadata and the user that work on the content module will see this process when he wants to start a workflow and can to attach files to the process before and during starting it.
I'm tried the alfresco community version but it's not contains the ability to build a custom index metadata, so how to make it.

Re: We need to work with alfresco content but we want a confirmation that it is supporting the following points:

afaust — Mon, 03 Jun 2019 21:48:39 GMT

Alfresco Community provides the same ability to build a custom metadata model as does the Enterprise version. Though there is a UI tool for developing custom models, it is quite limited and the long-term sustainable way to deal with custom metadata is typically by developing an extension module that bundles a custom model.

When using Alfresco Process Services, any user / group that you configure for a specific process will be able to start a workflow and attach files. During the execution of a process, any user who has been configured in the process model or who has been explicitly "involved" by other users in the same process will have access to its details, and / or be responsible for processing user tasks in that process.