Create and modify a file extension

Hi all,
Is it possible to create and modify a file with a custom extension.

Eg:-
File Uploaded: "HelloWorld.pdf"
Custom File: "HelloWorld.cto"

For each file that is uploaded in Appian, we also need to create a file with custom extension i.e., cto, ndo, pke, etc.,

The legacy service expects custom file which contains the metadata of the uploaded file.

Once both are available, they would be uploaded to the document repository.

Any suggestions would be helpful.

Parents
  • for your custom files - 

    Have a look at this page: https://docs.appian.com/suite/help/19.2/Text_Doc_From_Template_Smart_Service.html

    You can store text doc templates with any extension you wish.

    So you can have CTO_template.cto having one or more keys* to support your metadata.

    Then when you upload your PDF, you can then create a new .cto file, name it whatever you like, and load it with metadata.

    * In the past, I have had use cases in which I found it appropriate to use 1 simple key, e.g. ###docBody### to load the entire document. If you have detailed insight into the standard formatting of these data files, it's ideal to design the template as close to complete as possible.  e.g.

    field1: ###field1###
    field2: ###field2###

    and not

    ###docBody###

Reply
  • for your custom files - 

    Have a look at this page: https://docs.appian.com/suite/help/19.2/Text_Doc_From_Template_Smart_Service.html

    You can store text doc templates with any extension you wish.

    So you can have CTO_template.cto having one or more keys* to support your metadata.

    Then when you upload your PDF, you can then create a new .cto file, name it whatever you like, and load it with metadata.

    * In the past, I have had use cases in which I found it appropriate to use 1 simple key, e.g. ###docBody### to load the entire document. If you have detailed insight into the standard formatting of these data files, it's ideal to design the template as close to complete as possible.  e.g.

    field1: ###field1###
    field2: ###field2###

    and not

    ###docBody###

Children

 Discussion posts and replies are publicly visible