• State Not Answered
  • Replies 16 replies
  • Subscribers 7 subscribers
  • Views 5431 views
  • Users 0 members are here
Related Discussions
Home » Discussions » User Interface

92584 92583 92582 92581 92580 Hi .. we h

kumaraveln
92584
92583
92582
92581
92580


Hi .. we have a scenario with SAIL fileUploadFiled component .. We are aware that when we upload a document, it will be stored in a temporary location and will be moved to coded location only after submitting the form ..

if we use a PV of type document type it takes care of everything .. But we don't want to use PV here ..

Our scenario is
1. Our CDT is an array of categories.
2. Each category need multiple documents to be captured.
3. Since its a CDT, we capture documentId as Integer. So our fileUpload should save into Integer variable. We are able do do all the saving stuffs and we have all the temporary document ids as an array of array.
4. We persist the entire CDT into database and retrieve them back for displaying.
5. Our initial assumption was the document will be moved from temporary location to desired coded location with the same document id.
6. Now the problem is appian is not moving the document as such. Its...

OriginalPostID-132941

OriginalPostID-132941

  Discussion posts and replies are publicly visible

Parents
  • 0
    ... creating the document with a new id.
    7. Now our captured document id is of no use and we cannot refer to the actual document in any way.


    Now my questions are,
    1. For some reasons Appian is storing the documents in temporary folder and then moving it to the actual location. Why cant Appian move them with the same properties, at least the minimal properties like documentId. Its really hard to do the coding if something like a unique identifier is going to be different between the time of user action and final submit.

    2. You can say to use PV and thats recommended. We can capture it as PVs and then loop through them and store the actual IDs inside the CDT Integer field. But here the difficulty is we have to capture them as array of array. If there are 5 categories, we have to use 5 PVs of type document array. And our entire array of categories and array of documents to be captured is dynamic. Dynamic in the sense it comes from a XML and business can add a new cat...
Reply
  • 0
    ... creating the document with a new id.
    7. Now our captured document id is of no use and we cannot refer to the actual document in any way.


    Now my questions are,
    1. For some reasons Appian is storing the documents in temporary folder and then moving it to the actual location. Why cant Appian move them with the same properties, at least the minimal properties like documentId. Its really hard to do the coding if something like a unique identifier is going to be different between the time of user action and final submit.

    2. You can say to use PV and thats recommended. We can capture it as PVs and then loop through them and store the actual IDs inside the CDT Integer field. But here the difficulty is we have to capture them as array of array. If there are 5 categories, we have to use 5 PVs of type document array. And our entire array of categories and array of documents to be captured is dynamic. Dynamic in the sense it comes from a XML and business can add a new cat...
Children
No Data
© 2025 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.