This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
Add Property Placeholder Substitution Mechanism to BPMN Files #248
Assignees
Labels
enhancement
New feature or request
ready for release
Issue is fixed and merged into develop, ready for next release
Milestone
Comments
hhund
added a commit
that referenced
this issue
Dec 22, 2021
Adds a property replacements mechanism to bpmn files, similar to fhir
resources. #{version} and #{date} can be used in addition to all spring
managed properties.
Place holders in fhir and bpmn files should use the pattern #{...} now,
since ${...} can't be used in bpmn files, since it is already used by
camunda.
Adds the new placeholder #{date}/${date} to the replacement mechanism of
fhir files. Replacement within fhir resources still works with the old
${...} pattern.
implements #248
hhund
added
the
ready for release
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A property placeholders like ${version} can be used within ActivityDefinition files. These placeholders are resolved before storing the ActivityDefinition. The same or a similar mechanism should be added to the BPMN files, before they are parsed and stored within the business process engine.
The text was updated successfully, but these errors were encountered: