topic Re: Activiti Rest Api for Form properties in Alfresco Archive

Activiti Rest Api for Form properties

chandraprabha — Tue, 11 Aug 2015 19:07:50 GMT

Hi All,I am using below rest api to read the form properties but i am getting enumValues: [0] .Kindly let me know how i can get back enumValues http://localhost:9080/activiti-rest/service/form/form-data?taskId=95010Thanks,Chandra

Re: Activiti Rest Api for Form properties

chandraprabha — Wed, 12 Aug 2015 23:06:05 GMT

I am stuck can some please suggest the options.

Re: Activiti Rest Api for Form properties

vasile_dirla — Thu, 13 Aug 2015 07:58:07 GMT

please provide a unit test, then all the community members will use it in order to understand, investigate and help.

Re: Activiti Rest Api for Form properties

chandraprabha — Thu, 13 Aug 2015 16:45:34 GMT

I have a user task defined as below
    <userTask id="Reviewed" name="Reviewed">
      <extensionElements>
        <activiti:formProperty id="outgoing" name="outgoing flow" type="enum" required="true">
          <activiti:value id="Rejected" name="Rejected"></activiti:value>
          <activiti:value id="Payment" name="Payment"></activiti:value>
          <activiti:value id="FinalReview" name="FinalReview"></activiti:value>
        </activiti:formProperty>
      </extensionElements>
    </userTask>

I am now using REST Api to get the form properties associate with user task which return the form property but does not return enum

http://localhost:9080/activiti-rest/service/form/form-data?taskId=95010

which returns

{
formKey: null
deploymentId: "49503"
processDefinitionId: null
processDefinitionUrl: null
taskId: "51221"
taskUrl: "http://cdlcapssdgwas.es.ad.adp.com/activiti-rest/service/runtime/tasks/51221"
formProperties: [1]
0: {
id: "outgoing"
name: "outgoing flow"
type: "enum"
value: null
readable: true
writable: true
required: true
datePattern: null
enumValues: [0]
}

I am using form properties to send input to a decision task

Re: Activiti Rest Api for Form properties

trademak — Wed, 19 Aug 2015 20:25:02 GMT

This sounds like a bug. Can you please raise a JIRA issue for it?

Thanks,