Project

General

Profile

Bug #4988

Instantiating a wf as a composite that has a tag doesn't work as expected

Added by Derik Barseghian about 9 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
tagging
Target version:
Start date:
05/07/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4988

Description

If I have a workflow, drag a composite onto canvas, open the composite and tag it, then close the composite, I see the parent workflow gets the tag. If i delete the tag on the parent, then open the composite again, the tag is also gone on the composite. Fair enough, this seems ok.

However if I tag a workflow, Save Archive it into my local repo workflows folder, then find and expand this KAR in the component library gui and drag the workflow out to canvas, the parent does not get the tag. If I open the composite, it's not in there either.

History

#1 Updated by Derik Barseghian about 9 years ago

pushing to wrp-modules-2.X.Y as discussed in last call

#2 Updated by Sean Riddle over 8 years ago

(In reply to comment #0)

However if I tag a workflow, Save Archive it into my local repo workflows
folder, then find and expand this KAR in the component library gui and drag the
workflow out to canvas, the parent does not get the tag. If I open the
composite, it's not in there either.

This is expected behavior. The tag bar displays all tags on the top-level workflow. The tag is displayed in the original workflow, when it is on the top-level. When that workflow is instantiated into another as a composite, the tag is now on the composite, not on the top-level workflow, so it is not displayed in the tag bar. The tag's presence on the composite can be confirmed by selecting the Semantic Annotation Pane from the context menu of the composite.

#3 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 4988

Also available in: Atom PDF