SBM CUSTOM FILE ATTACHMENTS ?

Can some guide me to do the flowing task related to file uploading?

My Form shall indicate what essential documents are to be uploaded (e.g.Resume,Birth Certificate).

User to select from a list of pre-specified fields indicating what type of essential document is
being uploaded (e.g.Resume,Birth Certificate etc) before upload of the actual soft-copy of the
document.
System allows user to upload other nonessential documents.

System to indicate to user application submission is incomplete and will not be processed when there is missing essential documents.

Tags:

Parents
  • This doesn't necessarily handle any of the chaining together logic of stepping from one required attachment to another, but food for thought in terms of storing/displaying different attachment types using current sbm features.....

    A year ago I had actually put together a proof of concept on this very topic where I chose to use Aux tables for each 'type' of attachment which they could or need to add to a primary CI item. Then the primary item could have an embedded report of attachments showing any data from the Aux table but initially just attachment type (functional requirement, technical requirements, deployment architecture, etc...) and the link to the attachment.

    This was an option that could scale and handle the need for flexibly changing or using different attachment types. While it was a report we could ultimately have used the type to display certain attachments with certain fields or areas of a form since the embedded report could qualify on attachment type. We didn't ultimately implement or expand on this idea for other reasons.

    So while this may be one other option there are other use cases and reasons why the suggested Idea would still be nice to have baked into the product itself.
Reply
  • This doesn't necessarily handle any of the chaining together logic of stepping from one required attachment to another, but food for thought in terms of storing/displaying different attachment types using current sbm features.....

    A year ago I had actually put together a proof of concept on this very topic where I chose to use Aux tables for each 'type' of attachment which they could or need to add to a primary CI item. Then the primary item could have an embedded report of attachments showing any data from the Aux table but initially just attachment type (functional requirement, technical requirements, deployment architecture, etc...) and the link to the attachment.

    This was an option that could scale and handle the need for flexibly changing or using different attachment types. While it was a report we could ultimately have used the type to display certain attachments with certain fields or areas of a form since the embedded report could qualify on attachment type. We didn't ultimately implement or expand on this idea for other reasons.

    So while this may be one other option there are other use cases and reasons why the suggested Idea would still be nice to have baked into the product itself.
Children
No Data