+1

Regards,
Chathura

On Mon, Jan 12, 2015 at 7:24 PM, Milinda Perera <[email protected]> wrote:

> Hi,
>
> We are planning to add form generation to HumanTask-explorer webapp [1].
>
> *Current situation as follows:*
>     Currently HumanTask author create separate .jsp files and embed them
> in Main > Human Tasks > List in management console to display task
> information, and assignee work form
>
>     For Example, in ClaimsApprovalTask sample[2] ApproveClaim-input.jsp
>         ApproveClaim-input.jsp - Display inputs to the task
>         ApproveClaim-output.jsp - Generate output message
>
> Since this method increase workload and inefficient from the side of the
> humantask author, we decided to add form generation to the
> HumanTask-explorer. This proposed method reduces effort needed creating
> humantask.
>
> *New Improvement :*
>
> As suggested in [1] configuration need to done by the humantask author as
> follows:
>
> "The task author has to define which xml elements in the input message
> should be displayed under which label. And which xml elements in the output
> message should be filled with which form field. Task authors can provide
> this information under the <rendering> element"
>
> <renderings>
>     <rendering type="wso2">
>         <inputs>
>             <element>
>                 <label>[Label to display for the input element]</label>
>                 <value>[xpath to get the value from the input
> message]</value>
>             </element>
>             ...
>         </inputs>
>         <outputs>
>             <element>
>                 <label>[Label to display for the form field]</label>
>                 <value>[xpath of the element in the output message to be
> filled with this form field]</value>
>             </element>
>             ...
>         </outputs>
>     </rendering>
> </renderings>
>
>
> Then the humantask webapp can generate the output message by mapping form
> fields according to xpath expressions.
>
> Following diagram shows architecture of this new improvement:
>
>
> ​
>
> 1 - retrieve renderings using HumanTaskClientAPIAdmin and generate from.
> 2 - Create response using ResponseCreator which create soap message when
> user submit form.
> 3 - Send response
>
> We are planning to use Membrane SOA Model[3] library to generate output
> message (Response) using humantask wsdl
>
> Suggestions are highly appreciated.
>
> [1] mail : [Architecture] Jaggery based UI for WS-Human Tasks
> [2]
> https://github.com/milindaperera/product-bps/tree/master/modules/samples/product/src/main/resources/humantask/ClaimsApprovalTask
> [3] http://www.membrane-soa.org/soa-model/
>
> Thanks,
> Milinda
>
> --
> Milinda Perera
> Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to