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

I can copy all variables from a process instance #18578

Open
1 of 8 tasks
pedesen opened this issue May 16, 2024 · 1 comment
Open
1 of 8 tasks

I can copy all variables from a process instance #18578

pedesen opened this issue May 16, 2024 · 1 comment
Labels
component/frontend Related to a frontend component component/operate Related to the Operate component/team kind/feature Categorizes an issue or PR as a feature, i.e. new behavior

Comments

@pedesen
Copy link
Contributor

pedesen commented May 16, 2024

Description

In Operate, the user can see all process instance variables and their values based on the workflow. In certain scenarios it’s useful to let users copy those variables and use them elsewhere.

Here’s a more specific example. When the user wants to test and validate Camunda forms, the process instance variables which are available in Operate are helpful to use as a form input. A big limitation with our forms right now is that there is no context about available data. Even when a form is part of a BPMN process, when reviewing it individually (in the Form Editor), it’s not clear what data the user can operate with. A proper data management for Camunda forms is our long-term goal, though before we get there, as a quick win, we can enable the user to copy all variables from Operate (as a JSON) to use as a form input. In this case, the user can quickly test a form and define how it should be handled based on data source.

User Story

Scenario: As an Operate user
    Given I am in instance details view
    When I click the button "Copy all variables"
    Then All variables are copied to clipboard in JSON format

Designs

image

Acceptance Criteria

  • The variables footer contains a button "Copy all variables"
  • On button click all variables are copied to clipboard in JSON format

Proposed JSON format:

{
  "<variableName>": <variableValue>
}

Example:

{
  "firstName":"Paul",
  "lastName":"Young",
  "passNo":"P59909399",
  "ticketNo":"783"
}

Definition of Ready - Checklist

  • The issue has a meaningful title, description, and testable acceptance criteria
  • If documentation needs to be updated, an issue is created in the camunda-docs repo, and the issue is added to our Operate project board.
  • If HELM charts need to be updated, an issue is created in the camunda-platform-heml repo, and the issue is added to our Operate project board.
  • Potential Security risks have been considered and added to the product-hub issue risk assessment
  • Cross-team dependencies have been considered

Optional:

  • Design input has been collected by the assignee

👉 Handover Dev to QA

  • Handy resources:
    BPMN/DMN models, plugins, scripts, REST API endpoints + example payload, etc :
  • Example projects:
  • Versions to validate:

Docker file : in case that it needed to be tested via docker share the version contain the fixed along with version of other services .

  • Release version ( in which version this fixed/feature will be released)

📗 Link to the test case

@pedesen pedesen added kind/feature Categorizes an issue or PR as a feature, i.e. new behavior component/operate Related to the Operate component/team component/frontend Related to a frontend component labels May 16, 2024
@sdorokhova
Copy link
Contributor

@aleksander-dytko could you please check this new feature request and prioritize it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/frontend Related to a frontend component component/operate Related to the Operate component/team kind/feature Categorizes an issue or PR as a feature, i.e. new behavior
Projects
None yet
Development

No branches or pull requests

2 participants