camunda-bpm-platform icon indicating copy to clipboard operation
camunda-bpm-platform copied to clipboard

Resolve call-activities and business rule tasks via version tag and latest

Open ThorbenLindhauer opened this issue 4 years ago • 2 comments

This issue was imported from JIRA:

Field Value
JIRA Link CAM-12628
Reporter NYBzR2x
What is this name? This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.
Has restricted visibility comments true

User story

I want to start call-activities and business rule tasks by resolving version tag AND latest, similar to starting a process definition via latest version tag.

Background

The desired functionality to resolve call-activities and business rule tasks as it is possible today to start a process instance of the latest process definition for a version tag: 

 

// Starting a process definition via latest process definition of a version tag

ProcessDefinition pd = processEngine.getRepositoryService().createProcessDefinitionQuery()
    .processDefinitionKey("invoice")
    .versionTag("1.5-patch2")
    .latest()
    .singleResult();

processEngine.getRuntimeService().startProcessInstanceById(pd.getId());

 

Acceptance criteria

  • I can start call-activities and business rule tasks via the latest version tag.{{}}

Links:

  • is caused by https://jira.camunda.com/browse/SUPPORT-8529
  • is related to https://jira.camunda.com/browse/CAM-11408
  • is related to https://jira.camunda.com/browse/CAM-12146
  • is related to https://jira.camunda.com/browse/CAMPLAN-11
  • is related to https://jira.camunda.com/browse/SUPPORT-14657
  • is related to https://jira.camunda.com/browse/SUPPORT-14656

ThorbenLindhauer avatar Oct 21 '20 07:10 ThorbenLindhauer

Hi @ThorbenLindhauer

Are there any plans to implement this? I think the solution today makes not much sense to work with version tags at all.

My scenario is:

  • We have a standard versioning, like major.minor.patch - e.g. 2.4.5.
  • We want that a process is linked to its Minor Version -> like 2.4
  • We have a couple of patch versions - and of course it should take the latest.

At the moment I think the only solution would be to add the version to the Definition Key, like myproject-myprocess-v2.

Is there another way that I missed?

pme123 avatar Feb 05 '24 15:02 pme123

Hi,

This is currently not scheduled. As an enterprise customer you can raise a feature request via product support and request prioritization. In any case you could make a contribution if you need this functionality quickly.

Cheers, Thorben

ThorbenLindhauer avatar Feb 06 '24 13:02 ThorbenLindhauer