• 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 file...s 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). More

Recent Tweets