nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

DefaultFormHandler/extensionElement/ -> no form properties

hlux

Hello,

I'm having a problem with the activiti-webapp-explorer2 (activiti 5.4).
Whenever a usertask requires some input the form needs to be rendered
and displayed.

When I press the "complete task" button the following error occurs.

org.activiti.engine.ActivitiException: Unknown property used in expression
   at org.activiti.engine.impl.el.JuelExpression.getValue(JuelExpression.java:48)
   at org.activiti.engine.impl.el.UelExpressionCondition.evaluate(UelExpressionCondition.java:37)
‍‍‍‍‍

org.activiti.engine.impl.javax.el.PropertyNotFoundException: Cannot resolve identifier 'notEnoughInformation'
   at org.activiti.engine.impl.juel.AstIdentifier.eval(AstIdentifier.java:83)
   at org.activiti.engine.impl.juel.AstEval.eval(AstEval.java:50)
‍‍‍‍‍

I tried to find out what the problem is and found that
formData.getFormProperties().size() is always 0;
This is checked in the initTaskForm() method of the TaskDetailPanel class.

The formProperty List is never filled, because there are no FormPropertyHandlers added
during the parseConfiguration(…) in the DefaultFormHandler class.

And all that seems to be the case, because there are no extensionElements in the bpmn20.xml.
Because only when there are extension elements, the formPropertyHandlers are instantiated.

I'm not sure that I'm on the right track here,
maybe somebody can add some helpful thoughts.

thanks in advance.

hlux

Find more posts tagged with

Comments

frederikherema1

Hi,

Explorer 2 webapp is a prototype, and not really ready to be used out in the open. It uses the form-properties defined in the "extentionElement" of the start-event or task to render a form, not the "activiti:formKey" as Activiti explorer does, so makes sense you get this error. When using form-properties, the form will be rendered on the task-detail…

hlux

Hi,

thank you for your answer.

is the source code of that available somewhere?
I couldn't find it in the repository.

greetings hlux

frederikherema1

If you didn't build explorer2 webapp from source, where did you find it?

hlux

I do have the source for explorer2.

I was interested in the way the explorer handles the forms.
You described that it would use the "activiti:formKey" instead of
the "extentionElement".

That confused me a bit, because the DefaultFormHandler that parses the
configuration is part of the activiti-engine package.

I thought maybe it would clear up things for me, if I cound see the source code
of the activiti-webapp-explorer, which is used in the demo.
But that source code I couldn't find.

hlux

frederikherema1

Ah that way

You can find it here: http://svn.codehaus.org/activiti/activiti/trunk/modules/activiti-webapp-explorer

fyi, it overlays the activiti-webapp base-project.

hlux

hi, thank you for the information.

unfortunately I don't see any code that actually deals with
forms in those 2 webapps.

I probably don't understand the concept of the overlaying projects..
maybe you can shed some light on that?

frederikherema1

Sorry, I meant the rest-webapp:

http://svn.codehaus.org/activiti/activiti/trunk/modules/activiti-webapp-rest/src/main/java/org/activiti/rest/api/task/TaskOperationPut.java