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; } } }

selecting whole 'edition' in workflow

rohitspathak123

Hi

Using TS 6.1 Sol 5.8

We have to design a 'Approval Deployment Workflow' in which input is edition & not files.

The user will select select edition & initiate the workflow.

If the approver approves the edition then edition differential deployment will be done.

Now the problem is that what value we shlould have for 'areavpath' for the task.

If i am having something like this

[HTML][/HTML]

then it is giving error 'Bad Area' since i am chossing 'edition'

Please suggest me what should i have in 'areavpath' if I want to choose 'edition' as input to my workflow

~ rohit

Find more posts tagged with

Comments

kaalraa

Hi
Using TS 6.1 Sol 5.8
We have to design a 'Approval Deployment Workflow' in which input is edition & not files.
The user will select select edition & initiate the workflow.
If the approver approves the edition then edition differential deployment will be done.
Now the problem is that what value we shlould have for 'areavpath' for the task.
If i am having something like this
then it is giving error 'Bad Area' since i am chossing 'edition'
Please suggest me what should i have in 'areavpath' if I want to choose 'edition' as input to my workflow
~ rohit

I dont think... EDITION or STAGING files can be attached to a job as both of them are read-only areas.

jkm

The user will select select edition & initiate the workflow.

[HTML][/HTML]

then it is giving error 'Bad Area' since i am chossing 'edition'

Yes it throws this error and i dont think it is possible to achieve this by just selecting the Edition/staging area and triggering the workflow. You need to take inputs from the user in a form and then process those values in the wft file. For example user inputs can be
branch_name
Edition name

concat these values in the wft files and give this as areavpath in the tasks.

Again task should be marked as readonly. If you check wft examples there is a sample workflow to do this.