It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×1,305

question asked: Apr 06 '10, 11:57 a.m.
question was seen: 6,420 times
last updated: Apr 06 '10, 11:57 a.m.

Related questions

How could we migrate our workflow from Ent.svr to Std. svr.?

0
Tommy Wu (6●4●1) | asked Apr 06 '10, 11:57 a.m.
How could we migrate our workflow from Ent.svr to Std. svr.? Is there any license issue or function barrier ?

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Derek Baron (66●3●2) | answered Apr 07 '10, 10:41 a.m.
JAZZ DEVELOPER
How could we migrate our workflow from Ent.svr to Std. svr.? Is there any license issue or function barrier ?


Hi, the terms and conditions for Standard Edition limit you from creating and using custom lifecycles. To clarify: this means you can customize the existing lifecycles using the Web UI in SE, but cannot create new lifecycles from scratch using the RTC client.
0
permanent link
Peter Walker (168●1●3●6) | answered Apr 07 '10, 10:46 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
On 4/6/2010 12:07 PM, tommywu052 wrote:
How could we migrate our workflow from Ent.svr to Std. svr.? Is there
any license issue or function barrier ?

As Gili mentioned on a previous thread, the standard license only

supports the pre-canned workflows. So if you have a non-standard
customized workflow, you won't lose it but it won't show in the list of
workflows on the community lifecycle page.
Regards... Peter Walker

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.