nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deploying files from Edition to production server.

prasad54

Hi
I am trying to deploy files from TS Edition to production server using WFT.
I have provided the area vpath explicitly in WFT file using a variable $area_vpath, and I have set all the tasks Read only to true,then only it is working fine. but my other requirement in this workflow is ,user should be able to attach the files. I have provided an user task for this purpose, so that i can select files from task details window. but it's not allowing me to attach files from task details window as i have set the user task readonly to true.
If i remove read only to true i am getting bad work area error.

Could anyone help me out in this regard.? your inputs will be really helpful for me to resolve this.
Thanks In Advance.

Find more posts tagged with

Comments

ISCBorisB

Hi
I am trying to deploy files from TS Edition to production server using WFT.
I have provided the area vpath explicitly in WFT file using a variable $area_vpath, and I have set all the tasks Read only to true,then only it is working fine. but my other requirement in this workflow is ,user should be able to attach the files. I have provided an user task for this purpose, so that i can select files from task details window. but it's not allowing me to attach files from task details window as i have set the user task readonly to true.
If i remove read only to true i am getting bad work area error.

Could anyone help me out in this regard.? your inputs will be really helpful for me to resolve this.
Thanks In Advance.

It *sounds* like you set Tasks' areavpath Attributes to some read-only locations like STAGING or Edition.
Make sure that "Attach Assets" User/Group Task's areavpath is a Workarea where Task Owner has writing credentials.

If you really need help, provide the following instead of the usual "My code does not work, do you know why?" bleating:

1. Platform/OS Information
2. TS Version and Patch level Information
3. Brief Use Case / Scenario description
4. Problem Manifestation description, exact Error messaging, etc.
5. Code or at least relevant code Fragments

prasad54

Thank you very much for your reply. I just wanted to know whether we can attach files through user task when we are deploying files from Edition to production server.
If i put all the tasks read only then only workflow is getting initiated ,If i set readonly to false it's giving invalid work flow error( bad work area).
I wonder ,why is it not giving the bad work area error when i set all the tasks to ready only to true?

Version:TS 6.7.1
OS: Linux

Thanks again for your reply.

ISCBorisB

Thank you very much for your reply. I just wanted to know whether we can attach files through user task when we are deploying files from Edition to production server.
If i put all the tasks read only then only workflow is getting initiated ,If i set readonly to false it's giving invalid work flow error( bad work area).
I wonder ,why is it not giving the bad work area error when i set all the tasks to ready only to true?

Version:TS 6.7.1
OS: Linux

Thanks again for your reply.

In TeamSite Edition is a read-only Area.

TS Workflow Engine does not allow to instantiate non-readonly User/Group task with the read-only Area Vpath.
In other words, if you want to instantiate Task Object in read-only area the Task must be specified as read-only.
Thus you can attach only Files from the Workarea with User Task widgets.

That said, what you do with the attached Files is completely up to you. You may for example let your user
attach Files from the Workarea, build File List from that and use File List Deployment to Deploy
using required Edition as Deployment source Area. Note that in this scenario you may encounter WA/Ed
discrepancies, etc.