-
Notifications
You must be signed in to change notification settings - Fork 197
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
Support documentation URL in element template #614
Comments
I would imagine it something like // Element Template
{
"name": "My Task",
"id": "com.camunda.example.MyTask",
"appliesTo": [ "bpmn:ServiceTask" ],
"description": "An example task",
"documentationRef": "https://www.example.com/myTask"
} // JSON Schema
{
"documentationRef": {
"$id": "#/documentaionRef",
"type": "string",
"pattern": "^(https|http)://.*", // or whatever pattern we use
"errorMessage": {
"pattern": "Malformed documentation URL"
}
}
} |
Yes, that makes sense as a start. We can relax it at a future date (i.e. also allow relative URLs). |
@MaxTru @marstamm could you maybe have a look at my proposal (cf. #614 (comment))? If there is nothing against it, I could already start bringing the new property to the Schema. I would even say let's support it for both 7 and 8, there is no reason to only focus it on Camunda Platform 8. |
I don't see any problems with this approach, I think we can go ahead with it |
👍 from me as well |
This is fixed upstream via camunda/element-templates-json-schema#47. A schema release is pending, though. |
Implementation to follow-up with: #616 |
Is your feature request related to a problem? Please describe
As a user I want to see detailed documentation for a templated task, to be shown in the properties panel as well as the template chooser.
Describe the solution you'd like
Describe alternatives you've considered
None.
Additional context
Example showing an integration into the properties panel:
Example showing an integration into the element / template chooser:
Related to #610.
The text was updated successfully, but these errors were encountered: