Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365844 - CR: Provide Save As command for workflows
Summary: CR: Provide Save As command for workflows
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BPEL (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-07 04:27 EST by Nadine Ausländer CLA
Modified: 2022-10-03 11:11 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nadine Ausländer CLA 2011-12-07 04:27:04 EST
Build Identifier: 0.5.0.v20110623-1252-H77-CI (BPEL visual designer)

It would be nice to be able to save an existing workflow under a new name.

Reproducible: Always

Steps to Reproduce:
1. Open a workflow in the Business Process editor.
2. Edit the workflow.
3. Try to save the workflow under a new name (File > Save As).
=> Menu item is grayed out.
Comment 1 Igor Novakovic CLA 2011-12-07 04:46:56 EST
+1
Comment 2 Vincent Zurczak CLA 2012-01-31 10:48:27 EST
Hi,

Is it enough to save the process as a new file *in the workspace*?
We could imagine to save it as a new name anywhere on the disk, but the BPEL Designer does not support edition of external processes (located outside the workspace). Saving a copy in the workspace is quite easy to implement.

Another question: what should be the edited file after the "save as"? The previously edited file or the new copy?
Comment 3 Nadine Ausländer CLA 2012-01-31 12:10:28 EST
Hi, 

1st question: IMO, saving the process within the workspace will do. That was just what I intended to do when I posted this CR. ;-) 

2nd question: Well, preferably, it should conform with Eclipse's default behavior (if there is any). I tried it with a text file in the Text Editor: When I change the original file and select "Save As" to create a new file, I end up with the copy in the Text Editor showing the new input. The original file is left unchanged then. This seems to be a reasonable behavior. So, IMO, "the new copy" is the answer to your question.