Document or Folder Properties/Metadata

Good morning, everyone,

I'm a beginner on Appian, and I'm wondering:

is there a way to manage the properties or metadata of the folders and documents in Appian,

for example: I want to add the customer reference in the properties of my invoice document.

Is this possible? If not, is there a simple workaround?

  Discussion posts and replies are publicly visible

Parents
  • +1
    Certified Lead Developer

    To reinforce what Justin already said above, I strongly recommend creating a database backbone for the document management/metadata needs in any Appian system or application.  The baked-in document controls give us no control over certain things, for one thing, and also there is no easy way to add extended info or easy querying/searching/aggregating.

  • Hello ,  

    I have a background in ECM and normally these "databases" are created from scratch, but I understand the concept.

    Do you think it's better to create a database to manage this data per application or do I create one to manage all the metadata of all my applications?

    I ask you this question because I want to create in the future an application dependent on all the others that will just allow documents management (consult, search, etc...)

  • +1
    Certified Lead Developer
    in reply to Said BARKAM

    If your system is multi-application in nature and users typically have access to more than one of them, then it's probably worthwhile to build a platform-level document database where, among the other metadata you capture, each row stores an applicaton ID or similar. 

    The only real way to tell up-front whether to go with a platform-level or application-level DB, of the top of my head, is to analyze up front whether there will be significant differences in the different types of metadata you'd expect to capture for each document within the different applications.

Reply
  • +1
    Certified Lead Developer
    in reply to Said BARKAM

    If your system is multi-application in nature and users typically have access to more than one of them, then it's probably worthwhile to build a platform-level document database where, among the other metadata you capture, each row stores an applicaton ID or similar. 

    The only real way to tell up-front whether to go with a platform-level or application-level DB, of the top of my head, is to analyze up front whether there will be significant differences in the different types of metadata you'd expect to capture for each document within the different applications.

Children
No Data