Petals SE Flowable

Attachment support

Details

  • Type: Improvement Request Improvement Request
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: No version
  • Fix Version/s: 1.5.0
  • Component/s: Process service
  • Security Level: Public
  • Description:
    Hide

    In a process definition, we can have to use attachments. For example, a PDF file must be validated or rejected by a user task.

    Flowable has a support of attachments at process instance and/or task level. So the Petals SE Flowable should support attachments also when receiving service requests.

    As for variables, attachments are mapped through annotations placed inside of the binding operation definition into the WSDL:

    <wsdl:binding name="demandeDeCongesBinding" type="tns:demandeDeConges" > 
   <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
   <wsdl:operation name="demanderConges">
      <soap:operation soapAction="http://petals.ow2.org/se/Acitivibpmn/1.0/su/demanderConges" />
      <bpmn:operation processDefinitionId="vacationRequest" action="startEvent" actionId="request" />
      <bpmn:userId>/*[local-name()='demande']/*[local-name()='demandeur']</bpmn:userId>
      <bpmn:variable name="numberOfDays">
         /*[local-name()='demande']/*[local-name()='nbJourDde']
      </bpmn:variable>
      <bpmn:attachment name="signature">
         /*[local-name()='demande']/*[local-name()='signature']
      </bpmn:attachment>
      <bpmn:output>valid.xsl</bpmn:output>
      <wsdl:input>
         <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
         <soap:body use="literal" />
      </wsdl:output>
   </wsdl:operation>
</wsdl:binding>
    Show
    In a process definition, we can have to use attachments. For example, a PDF file must be validated or rejected by a user task. Flowable has a support of attachments at process instance and/or task level. So the Petals SE Flowable should support attachments also when receiving service requests. As for variables, attachments are mapped through annotations placed inside of the binding operation definition into the WSDL: 
    <wsdl:binding name="demandeDeCongesBinding" type="tns:demandeDeConges" > 
   <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
   <wsdl:operation name="demanderConges">
      <soap:operation soapAction="http://petals.ow2.org/se/Acitivibpmn/1.0/su/demanderConges" />
      <bpmn:operation processDefinitionId="vacationRequest" action="startEvent" actionId="request" />
      <bpmn:userId>/*[local-name()='demande']/*[local-name()='demandeur']</bpmn:userId>
      <bpmn:variable name="numberOfDays">
         /*[local-name()='demande']/*[local-name()='nbJourDde']
      </bpmn:variable>
      <bpmn:attachment name="signature">
         /*[local-name()='demande']/*[local-name()='signature']
      </bpmn:attachment>
      <bpmn:output>valid.xsl</bpmn:output>
      <wsdl:input>
         <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
         <soap:body use="literal" />
      </wsdl:output>
   </wsdl:operation>
</wsdl:binding>
  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Fri, 5 Aug 2016 - 11:56:47 +0200
Field Original Value New Value
Fix Version/s 1.0.2 [ 10654 ]
Priority Major [ 3 ]
Description In a process definition, we can have to use attachments. For example, a PDF file must be validated or rejected by a user task.

Activiti has a support of attachments at process instance and/or task level. So the Petals SE Activiti should support attachments also when receiving service requests.

As for variables, attachments are mapped through annotations placed inside of the binding operation definition into the WSDL:
{code:xml}
<wsdl:binding name="demandeDeCongesBinding" type="tns:demandeDeConges" >
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    <wsdl:operation name="demanderConges">
       <soap:operation soapAction="http://petals.ow2.org/se/Acitivibpmn/1.0/su/demanderConges" />
    <bpmn:operation processDefinitionId="vacationRequest" action="startEvent" actionId="request" />
           <bpmn:userId>/*[local-name()='demande']/*[local-name()='demandeur']</bpmn:userId>
           <bpmn:variable name="numberOfDays">
              /*[local-name()='demande']/*[local-name()='nbJourDde']
           </bpmn:variable>
           <bpmn:attachment name="signature">
              /*[local-name()='demande']/*[local-name()='signature']
           </bpmn:attachment>
           <bpmn:output>valid.xsl</bpmn:output>
       <wsdl:input>
         <soap:body use="literal" />
       </wsdl:input>
       <wsdl:output>
         <soap:body use="literal" />
       </wsdl:output>
</wsdl:operation>
</wsdl:binding>
{code} 		In a process definition, we can have to use attachments. For example, a PDF file must be validated or rejected by a user task.

Activiti has a support of attachments at process instance and/or task level. So the Petals SE Activiti should support attachments also when receiving service requests.

As for variables, attachments are mapped through annotations placed inside of the binding operation definition into the WSDL:
{code:xml}
<wsdl:binding name="demandeDeCongesBinding" type="tns:demandeDeConges" >
   <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
   <wsdl:operation name="demanderConges">
      <soap:operation soapAction="http://petals.ow2.org/se/Acitivibpmn/1.0/su/demanderConges" />
      <bpmn:operation processDefinitionId="vacationRequest" action="startEvent" actionId="request" />
      <bpmn:userId>/*[local-name()='demande']/*[local-name()='demandeur']</bpmn:userId>
      <bpmn:variable name="numberOfDays">
         /*[local-name()='demande']/*[local-name()='nbJourDde']
      </bpmn:variable>
      <bpmn:attachment name="signature">
         /*[local-name()='demande']/*[local-name()='signature']
      </bpmn:attachment>
      <bpmn:output>valid.xsl</bpmn:output>
      <wsdl:input>
         <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
         <soap:body use="literal" />
      </wsdl:output>
   </wsdl:operation>
</wsdl:binding>
{code}
Christophe DENEUX made changes - Fri, 5 Aug 2016 - 11:57:10 +0200
Status New [ 10000 ] Open [ 10002 ]
Christophe DENEUX made changes - Fri, 5 Aug 2016 - 12:08:09 +0200
Component/s Process service [ 10400 ]
Christophe DENEUX made changes - Wed, 21 Sep 2016 - 09:05:07 +0200
Fix Version/s 1.0.2 [ 10654 ]
Fix Version/s 1.0.3 [ 10692 ]
Christophe DENEUX made changes - Fri, 22 Sep 2017 - 17:53:51 +0200
Project Petals SE Activiti [ 10231 ] Petals SE Flowable [ 10270 ]
Key PETALSSEACTIVITI-25 PETALSSEFLOWABLE-16
Affects Version/s No version [ 10740 ]
Affects Version/s 1.0.1 [ 10578 ]
Component/s  Process service [ 10433 ]
Component/s Process service [ 10400 ]
Fix Version/s 1.1.0 [ 10692 ]
Christophe DENEUX made changes - Fri, 22 Sep 2017 - 17:54:06 +0200
Fix Version/s 1.0.0 [ 10741 ]
Christophe DENEUX made changes - Fri, 22 Sep 2017 - 17:54:50 +0200
Description In a process definition, we can have to use attachments. For example, a PDF file must be validated or rejected by a user task.

Activiti has a support of attachments at process instance and/or task level. So the Petals SE Activiti should support attachments also when receiving service requests.

As for variables, attachments are mapped through annotations placed inside of the binding operation definition into the WSDL:
{code:xml}
<wsdl:binding name="demandeDeCongesBinding" type="tns:demandeDeConges" >
   <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
   <wsdl:operation name="demanderConges">
      <soap:operation soapAction="http://petals.ow2.org/se/Acitivibpmn/1.0/su/demanderConges" />
      <bpmn:operation processDefinitionId="vacationRequest" action="startEvent" actionId="request" />
      <bpmn:userId>/*[local-name()='demande']/*[local-name()='demandeur']</bpmn:userId>
      <bpmn:variable name="numberOfDays">
         /*[local-name()='demande']/*[local-name()='nbJourDde']
      </bpmn:variable>
      <bpmn:attachment name="signature">
         /*[local-name()='demande']/*[local-name()='signature']
      </bpmn:attachment>
      <bpmn:output>valid.xsl</bpmn:output>
      <wsdl:input>
         <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
         <soap:body use="literal" />
      </wsdl:output>
   </wsdl:operation>
</wsdl:binding>
{code} 		In a process definition, we can have to use attachments. For example, a PDF file must be validated or rejected by a user task.

Flowable has a support of attachments at process instance and/or task level. So the Petals SE Flowable should support attachments also when receiving service requests.

As for variables, attachments are mapped through annotations placed inside of the binding operation definition into the WSDL:
{code:xml}
<wsdl:binding name="demandeDeCongesBinding" type="tns:demandeDeConges" >
   <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
   <wsdl:operation name="demanderConges">
      <soap:operation soapAction="http://petals.ow2.org/se/Acitivibpmn/1.0/su/demanderConges" />
      <bpmn:operation processDefinitionId="vacationRequest" action="startEvent" actionId="request" />
      <bpmn:userId>/*[local-name()='demande']/*[local-name()='demandeur']</bpmn:userId>
      <bpmn:variable name="numberOfDays">
         /*[local-name()='demande']/*[local-name()='nbJourDde']
      </bpmn:variable>
      <bpmn:attachment name="signature">
         /*[local-name()='demande']/*[local-name()='signature']
      </bpmn:attachment>
      <bpmn:output>valid.xsl</bpmn:output>
      <wsdl:input>
         <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
         <soap:body use="literal" />
      </wsdl:output>
   </wsdl:operation>
</wsdl:binding>
{code}
Christophe DENEUX made changes - Thu, 4 Jan 2018 - 12:10:48 +0100
Fix Version/s 1.0.1 [ 10772 ]
Fix Version/s 1.0.0 [ 10741 ]
Christophe DENEUX made changes - Wed, 24 Jan 2018 - 12:54:57 +0100
Fix Version/s 1.0.2 [ 10812 ]
Fix Version/s 1.0.1 [ 10772 ]
Christophe DENEUX made changes - Thu, 26 Jul 2018 - 17:03:47 +0200
Fix Version/s 1.1.2 [ 10870 ]
Fix Version/s 1.1.0 [ 10812 ]
Hide
Permalink
Christophe DENEUX added a comment - Wed, 12 Apr 2023 - 11:32:38 +0200

Postponed to version 1.5.0 or upper

Show
Christophe DENEUX added a comment - Wed, 12 Apr 2023 - 11:32:38 +0200 Postponed to version 1.5.0 or upper
Christophe DENEUX made changes - Wed, 12 Apr 2023 - 11:32:38 +0200
Fix Version/s 1.5.0 [ 11114 ]
Fix Version/s 1.4.0 [ 10870 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
1m 53s
1
Christophe DENEUX
Fri, 5 Aug 2016 - 11:57:10 +0200



People

Dates

  • Created:
    Fri, 5 Aug 2016 - 11:55:17 +0200
    Updated:
    Wed, 12 Apr 2023 - 11:32:38 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.