Avatar

Level 1

Hi Rui,

Thanks for the response.

I am good with going the 12 different XDPs attached to a single workflow approach. This will ease things a bit for me too in terms of scripting. I am ok with the scripting but I believe layout and flow management will be a bigger issue in this case of roman and asian fonts support in the same form in same label fields.

Anyway now that brings me to the second question.

As we know that the form would be triggered from a Task Manager endpoint from workspace. This endpoint is associated with the orchestration that will route the process. It would have a formvar variable of the type xfaForm. I use the templateURL property of this variable to bind the process to a XDP template. The formvar variable also defines a custom Renderer and Submit service for prefilling the form and handling form submissions.

Now I do not see any way by which a Task Manager Endpoint would pass the language setting/parameter to the main process that will help me select the approrpiate XDP template. How do we do this ?

Moreover are we sure we can have XPATH expression in the templateURL field of the formvar properties window. Otherwise how would we dinamically select the appropriate template for a workflow.

Note 1: This form will get rendered just once (i.e for the initiator, where I need this localization behavior) once the initiator submits the form there are a bunch of notification sent by the process, updates SAP using Webservice call and then the process completes.

Note 2: I know this can be done using 12 different processes (workflows) bound to 12 different XDP templates for each language I need to support. However I do not see it as and elegant solution in terms of long term sustenance.

Thanks and Regards,

Hemen