Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Process Edit/Copy in Workspaces with referenced Files after Sharing #383

Closed
10 of 11 tasks
iaktern opened this issue Sep 16, 2024 · 0 comments · Fixed by #392
Closed
10 of 11 tasks

Process Edit/Copy in Workspaces with referenced Files after Sharing #383

iaktern opened this issue Sep 16, 2024 · 0 comments · Fixed by #392
Assignees

Comments

@iaktern
Copy link
Contributor

iaktern commented Sep 16, 2024

If a process is shared to the public, there should be the option to copy and edit this process in the users own spaces.

TODOs:

  • Rename "Add to your workspace" into "Edit" (with icon)
  • The following modal should have the title "Options for Editing", a list with multiple options (rectangular buttons like currently, horizontal scrollable if too many workspaces) and under it a selection/info area. The buttons for the modal should be "Close" and "Copy and Edit" (and a closing cross icon on the top right)
  • First option: "Direct Edit" button. It should only be activated if the user is member of the same space where the process is currently hosted and if she has access to the folder (i.e. is authorized). In this case, show in the info area the text: "The process will not be copied. You directly edit the original process. This will change the process for every other user including this sharing document." If the user has no access to the folder, gray the "Direct Edit" button out.
  • Other options: show a button for every space the user has access to. The text: "Copy to XX Space". Every click on own of the buttons should render a tree view in the info area for the folders of this workspace, so that the user can select a folder where she wants to copy the process to.
  • Clicking on "Copy and Edit" should not copy referenced files (e.g. images). instead it increases the reference_counter for this file in the DB.

TODOs for implementing the Ref Counter:

  • for every new upload of a file in the frontend needs to set the
  • for every change/modification of an existing file, a new file in the GCP DB need to be created (not overriding an exiting file). Set the reference_counter to 1 for this new file and decrease the reference_counter by 1 for the modified file
  • if a process, BPMN element (task, event, etc.) or file gets deleted, also decrease the reference_counter by 1 for every referenced file
  • if undo is clicked after a BPMN element (task, event, etc.) was deleted, increase the reference_counter by 1
  • if a process is copied (not moved), increase the reference_counter by 1
  • batch process: if reference_counter is 0 then delete the file after one week
@iaktern iaktern converted this from a draft issue Sep 16, 2024
@anishsapkota anishsapkota linked a pull request Sep 23, 2024 that will close this issue
@OhKai OhKai closed this as completed in #392 Dec 9, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in PROCEED MS New Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants