表单服务中的未知类型'processDefinition'

Question

我们目前正在使用Grails为Activiti编写一个新的前端，以便在处理任务和填写相关数据时为用户提供一个定制的UI。

我们能够查询Activiti引擎并返回任务列表;下面的代码像我们期望的那样工作，并且(连同视图)给出了一个基本的任务列表——名称、描述等:

def index() {
    def tasks = activitiService.findAllTasks(["sort": null, "offset": 0, "max": 10])
    [tasks: tasks]
}

但是，当我们尝试为单个任务拉回表单数据时(这样我们就可以将表单显示给用户以完成):

def view(params) {
    def taskQuery = taskService.createTaskQuery()
    def task = taskQuery.taskId(params.id).singleResult();
    def form = formService.getRenderedTaskForm(params.id)
    [task: task, form: form]
}

抛出错误:

unknown type 'processDefinition' processDefinition

在def form =线上;完整的跟踪信息如下:

    Line | Method
->>   55 | parseFormPropertyType             in org.activiti.engine.impl.form.FormTypes
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
|     61 | parseConfiguration                in org.activiti.engine.impl.form.DefaultFormHandler
|     34 | parseConfiguration . . . . . . .  in org.activiti.engine.impl.form.DefaultStartFormHandler
|     84 | createStartFormHandlers           in org.activiti.engine.impl.bpmn.parser.handler.StartEventParseHandler
|     58 | executeParse . . . . . . . . . .  in     ''
|     38 | executeParse                      in     ''
|     84 | parse . . . . . . . . . . . . . . in org.activiti.engine.impl.bpmn.parser.handler.AbstractBpmnParseHandler
|     27 | parse                             in org.activiti.engine.impl.bpmn.parser.handler.AbstractFlowNodeBpmnParseHandler
|     36 | parse . . . . . . . . . . . . . . in org.activiti.engine.impl.bpmn.parser.handler.AbstractActivityBpmnParseHandler
|     73 | parseElement                      in org.activiti.engine.impl.bpmn.parser.BpmnParseHandlers
|    435 | processFlowElements . . . . . . . in org.activiti.engine.impl.bpmn.parser.BpmnParse
|     88 | transformProcess                  in org.activiti.engine.impl.bpmn.parser.handler.ProcessParseHandler
|     49 | executeParse . . . . . . . . . .  in     ''
|     35 | executeParse                      in     ''
|     84 | parse . . . . . . . . . . . . . . in org.activiti.engine.impl.bpmn.parser.handler.AbstractBpmnParseHandler
|     73 | parseElement                      in org.activiti.engine.impl.bpmn.parser.BpmnParseHandlers
|    395 | transformProcessDefinitions . . . in org.activiti.engine.impl.bpmn.parser.BpmnParse
|    231 | execute                           in     ''
|    107 | deploy . . . . . . . . . . . . .  in org.activiti.engine.impl.bpmn.deployer.BpmnDeployer
|     50 | deploy                            in org.activiti.engine.impl.persistence.deploy.DeploymentManager
|    115 | resolveProcessDefinition . . . .  in     ''
|     65 | findDeployedProcessDefinitionById in     ''
|    751 | getTaskDefinition . . . . . . . . in org.activiti.engine.impl.persistence.entity.TaskEntity
|     54 | execute                           in org.activiti.engine.impl.cmd.GetRenderedTaskFormCmd
|     24 | execute . . . . . . . . . . . . . in org.activiti.engine.impl.interceptor.CommandInvoker
|     57 | execute                           in org.activiti.engine.impl.interceptor.CommandContextInterceptor
|     47 | doInTransaction . . . . . . . . . in org.activiti.spring.SpringTransactionInterceptor$1
|     45 | execute                           in org.activiti.spring.SpringTransactionInterceptor
|     31 | execute . . . . . . . . . . . . . in org.activiti.engine.impl.interceptor.LogInterceptor
|     40 | execute                           in org.activiti.engine.impl.cfg.CommandExecutorImpl
|     35 | execute . . . . . . . . . . . . . in     ''
|     46 | getRenderedTaskForm               in org.activiti.engine.impl.FormServiceImpl
|     22 | view . . . . . . . . . . . . . .  in TasksController.groovy
|    195 | doFilter                          in PageFragmentCachingFilter.java
|     63 | doFilter . . . . . . . . . . . .  in AbstractFilter.java
|   1145 | runWorker                         in java.util.concurrent.ThreadPoolExecutor
|    615 | run . . . . . . . . . . . . . . . in java.util.concurrent.ThreadPoolExecutor$Worker
^    744 | run                               in java.lang.Thread

我们似乎需要在某个时候将进程定义传递给formService，或者至少有一个可用的库，它可以从中创建一个进程定义;不幸的是，我们还不能确切地知道如何做到这一点。

那么-我们错过了什么将使这个工作?或者，我们实际上完全走错了路，并且有更好的解决方案来满足我们的需求(除了直接查询数据库表，这是我们试图避免的)?

Answer 1

当您使用未注册的自定义类型定义表单字段时，似乎会出现这种错误。如果你试图显示一个表单字段，暴露你的过程定义，我发现了一个很好的博客文章，可能在这里相关

基本上，您必须定义您的自定义类型(在本例中为ProcessDefinitionFormType)并在resources.groovy中注册它:

processDefinitionFormType(org.unnoware.ProcessDefinitionFormType)
processEngineConfiguration(org.activiti.spring.SpringProcessEngineConfiguration) {
           // ... many other properties are set here, you may copy them from activiti plugin source
            customFormTypes = [ref('processDefinitionFormType')]
        }

编辑:

你可以在Config中注册你的自定义类型。groovy":

beans {
    processEngineConfiguration {
            customFormTypes = [new org.unnoware.ProcessDefinitionFormType()]
    }
}