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

TeamSite

AmitB

Created
File > New Branch (amitb)
File > New Workarea (amitworkarea)
Now for workarea 'amitworkarea' created New Job with
File > New Job
and Selected available template for the same and Run the Job. Now I renamed the branch 'amitb' to 'amit'.
Is this behavior ok as I am able to change the name of the Branch ?
What will happen to the tasks assigned to previous branch (amitb)?

Find more posts tagged with

Comments

Adam Stoller

The workflow that is already in progress will get hung up. If you are lucky and you change the branch name when the workflow is sitting in a usertask or owned grouptask, you can go through the Job Admin screens and change the areavpath for all the tasks in the workflow and it will probably work.

Generally, you shouldn't change the names of branches and workareas without first verifying that there are no active jobs (or any other reliance) on those branch or workarea names.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com