New Field Types for File and URL Attachments Hot

by Lynn Mattie on June 09, 2015

Although file and URL attachments are adequate for some attachments, at times the process would be much better if these could be tracked more like a field. This would allow for different types of files or URLs to be required on specified transitions and included in reports.

  • The column in the db might just be an id that points to the attachment table, but having "field" type flexibility for these would be very beneficial to lots of processing. You could track any number of particular type of attachments, for instance maybe you need a Requirements document attached at one part of the workflow and a Design document attached at another part. Maybe there could be an option when you add the field to also show them within the attachments section (probably as read-only).

    Ideas

    Status
    Target Release
    SBM 11.2
  • Please login to view any attachments.

  • Already have an account? or Create an account
    YES! Please make this happen!
    Adam Commented by Adam May 05, 2016
    Top 500 Reviewer  -  

    YES! Please make this happen!

    YEAH!

    This enhancement has been requested by our customers back in 2011!
    I have just searched my inbox and found this original conversation:

    "Hallo Tina,

    right now there is only one "bucket" for attachments per SBM item. Any kind of attachment is stored there. No attachment attributes (besides its name), categories or custom fields can be defined. Bernd now wishes to have the possibility to define as many attachment buckets as he likes and to use them as he is using any other SBM field type.

    So he wants to define an (file) attachment bucket as he can with fields.
    Simply drag an "attachment field" onto the table, workflow and form. This field then should have an upload icon included, so that the user can upload an attachment directly into that field (like he can pick a date from the calendar popup for date fields). We may need to have a Single-Attachment field and a Multi-Attachment field. When the field is read-only it is displayed as download links for the attachments stored inside. When the field is editable is should allow delete/ add attachments. Probably it is good to have it like Journal fields with an "add attachment only" option.

    I think this is a very cool idea."

    Go for it, sooner than later!

    Cheers
    Brian
    Brian Rosenberger Commented by Brian Rosenberger February 25, 2016
    Top 50 Reviewer  -  

    YEAH!

    This enhancement has been requested by our customers back in 2011!
    I have just searched my inbox and found this original conversation:

    "Hallo Tina,

    right now there is only one "bucket" for attachments per SBM item. Any kind of attachment is stored there. No attachment attributes (besides its name), categories or custom fields can be defined. Bernd now wishes to have the possibility to define as many attachment buckets as he likes and to use them as he is using any other SBM field type.

    So he wants to define an (file) attachment bucket as he can with fields.
    Simply drag an "attachment field" onto the table, workflow and form. This field then should have an upload icon included, so that the user can upload an attachment directly into that field (like he can pick a date from the calendar popup for date fields). We may need to have a Single-Attachment field and a Multi-Attachment field. When the field is read-only it is displayed as download links for the attachments stored inside. When the field is editable is should allow delete/ add attachments. Probably it is good to have it like Journal fields with an "add attachment only" option.

    I think this is a very cool idea."

    Go for it, sooner than later!

    Cheers
    Brian

    Perhaps this idea should be combined with this one: http://serenacentral.com/community/ideas/sbm/create-file-data-type
    Tom Clement Commented by Tom Clement October 26, 2015
    Top 10 Reviewer  -  

    Perhaps this idea should be combined with this one: http://serenacentral.com/community/ideas/sbm/create-file-data-type

    We will put this idea Under Consideration for the 2HCY'16 release of SBM.
    David J. Easter Commented by David J. Easter August 07, 2015
    #1 Reviewer  -  

    We will put this idea Under Consideration for the 2HCY'16 release of SBM.

    I completely agree. 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.

    Derek George Commented by Derek George June 23, 2015
    Top 100 Reviewer  -  

    I completely agree. 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.

     
    View all user comments
     

PrintEmail

Recent Tweets

Twitter response: "Invalid or expired token."