How to edit Workflow on former Template “child” project?
Question ID: 109630

We “downgraded” from “ALM” license to “Enterprise” license and disconnected a project from it’s “parent” Template, but it still executes the template Workflow instead of the local project workflow.  HOW do we disable the old template workflow (since we cannot use it anymore with “enterprise”) , and just use the “regular” workflow?

Marked as spam
Posted by (Questions: 193, Answers: 14)
Asked on June 18, 2020 1:48 pm
Answers (1)
Private answer

So, you can usually edit the "template" workflow code in the template (when you have the full "ALM" license), but not in the "child" project(s), AND the "frozen" Template code always runs in the Child projects AND ignores the "local" workflow stored in the project (non-template).

Since you no longer have the ALM level license, you have a few ways to remedy this:
1) Upgrade back to the ALM license to quickly get back the cross-project/template behavior, then push the template workflow edits down to the "child" projects.
2) ABANDON the template/cross-project additions to the project(s) by "removing" the Template project. This will then unlock the template section of the "child" project workflow scripts and they can be deleted after migrating code down to the "normal" code modules (non-template named).
Then the project(s) will act like "normal" projects.

Marked as spam
Posted by (Questions: 4, Answers: 509)
Answered on June 18, 2020 1:51 pm

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top