-
Feature Request
-
Resolution: Won't Do
-
L3 - Default
-
None
-
None
-
None
-
None
User Story (Required on creation):
As a user, I can see an error message when trying to deploy a process model with a script task that has no script format defined.
Functional Requirements (Required before implementation):
Technical Requirements (Required before implementation):
Limitations of Scope (Optional):
Hints (Optional):
Original Description
if you write a script, such as part of a script task, and omit/forget to add a script format, then deploy through auto-deployment the missing script format should be caught as a parsing error. Instead there is no error and during execution the script does nothing.
QoL should provide a level of error catching for deployment of a field that is essentially mandatory in order for the script to execute.
This is the controller panel for Smart Panels app
[CAM-13446] Deployment should fail when script format of a script task is undefined
Hi StephenOTT,
Thank you for this feature request. I will have a look soon.
Stay tuned!
Best,
Tassilo
Hi StephenOTT,
thanks for making us aware of this.
While I generally agree that this is something that the engine could reject upon deployment, we will not add this feature request to the backlog. Introducing a stricter validation in that regard has already led to a couple of issues for customers in the past with older models that could be deployed on previous versions but failed to do so on newer ones. With regards to behavioral compatibility, this can quickly lead to more issues than it solves. Weighing that in, we will not realize that feature request. I will close the request due to this reasoning.
This does not mean that the request is not valid and I would like to emphasize that part. It simply has proven to cause more problems than it solves in the past, this is why we will not follow that request.
I hope that this is a reasonable explanation.
Best,
Tobias
The modeler also does not identify this field as mandatory.