Skip to Main Content
Created by Guest
Created on Apr 30, 2025

Process Models - Document Linking

Some of this will prob be training but some seems a bit nuanced and could likely be improved

  • Can’t tell from a flow 'Task' view if there is any linked, have to go into the properties to find out

  • When linking a doc it automatically Saves a copy to the Documents area

    • If want to link to the doc again the browse wasn’t pulling in data without a prompt. Also needed a group and then couldn’t view what was available, had to know the naming of the document, which is potentially not ideal if you are not sure what someone before you named something ? Are there some guidelines to good structure/conventions for documentation file naming , searching that this product recommends or do clients / Teams just look to come up with their own?

  • What is the value add of Selecting a Process Group when adding/linking a file?

  • When deleting a document from a Task it does not delete from the Documents listing by the looks. So then,

  • When viewing files saved under the full Documents listing it is still there, then...

    • Can’t delete a document can only archive, BUT, when go into Archives it lets us delete it BUT, if a document was not deleted from a Task then when go back to the flow the document is still linked and still opens. Even though it has been deleted from the Documents list.
      Not sure about the controls around this? There seems to be no warning that the Document is being used somewhere else nor a way to identify where else it is being used.

      not sure of answer here but seems to require some more thinking for the saving of documents and recommended conventions perhaps

  • Attach files