Home
TeamSite
Attachments within workflow
Hazzie
Hi,
We have a user requirement to enable workflow creators to attach documents to a workflow (word, excel, graphics, etc) that help to explain what the authors/editors need to do to get the job done.
These attachments do not form part of the edited files and will not be open deployed up to the end web sites. This is all well and good as i can link the user requirements documents to the workflow and save them in a folder that open deploy does not look at and therefore not upload.
However my problem is that these attachments are only unique to the piece of work being done at the time. If another workflow creator comes along and creates a workflow (which is based on staging) then they must not receive any of the previous workflows attachments.
How do i prevent users from seeing/downloading certain files (or even whole folders contents) from staging when a workflow is created, yet allow only the relevant attachments to be within an edition for audit purposes.
Hazzie
TS 5.5.2 on NT.
Find more posts tagged with
Comments
Bowker
Hazzie,
Sounds like you will need to write some custom code to handle your attachments.
Things to think about:
* Do you want the 'instructions' to be versioned? (submitted to staging?)
* You don't say how those instructions are created and placed in staging. Maybe that process can create the workflow so only the new instructions can be attached.
* Using the exclude features in OD is a good way to prevent the files from deploying.
WIthout more of the business logic/environment options you have it would be tough to help with this one.
Dan Bowker
Northern Trust
Web Publishing Technology
Hazzie
Hi,
Thanks for the reply.
Well custom code I am happy to write so no problem there.
I already have a process that kicks off a workflow that pops up a CGI that allows the user to fill in details of the job to be done. These details are text and stored in a MSSQL DB but often the users want to store a word document or a picture or something else to give the job extra meaning that they cannot adequately convey in a sentence.
After they click continue on this CGI and edition of staging is published and work area is created based on this new edition (done this way as it is significantly faster than just populating a workarea from staging). It is on this CGI that I will create an attach document button, link the document to the workflow and place it into a folder that is NOT deployed by OD. That is all fine and relatively easy to do.
My problem is that the attached documents only have relevance to the particular workflow at that time. They will NEVER be used again by another workflow and previous workflows attached documents should not be available to the authors/editors of the work. These documents have to be versioned for historical purposes and for problem dispute.
So how do I reconcile the need for versioning but only have relevant documents in the attached documents folder so authors/editors will only see the documents that have meaning to the job they are doing.
When I create the workarea can I tell it not to bring down a folder from the edition and if so will I have any issues when I put that folder back into staging and update the edition when deploying.
Ta,
Hazzie
TS 5.5.2 on NT.
Bowker
If custom code is not a problem for you then I would suggest that before your "submit" step, that you copy the files in question to another branch (sub branch?), submit them there and remove them from the current workflow.
I'm assuming that after the job completes that you are destroying the 'temporary workarea' you use.
Dan Bowker
Northern Trust
Web Publishing Technology