Different scenario to run Former XML Publisher report

Question

Hi All.
I have some different kind of scenario to run the XML Publisher report. Please look into the following scenario and requirements:
In my current project we are implementing 22 languages like Chinese, Japanese, Spanish etc. Out of these 22 languages, 8 languages will be installed and 14 will be uninstalled. We are defining the language on 2 places: OU level and Address level. For those reports that need to be translated, we are using XML Publisher to achieve this, but we have different scenario to pass the language, in order to select the corresponding template.
Scenario: As i mentioned we are defining the languages on address level, it is considered that the language defined at the address level will be customer's preferred language and he would like to see the output in that language only. there are 2 possible conditions while running the report: 1. User may select the language in which he want the report to be displayed in. 2. User may not select any language. The 1st scenario can be fulfilled by standard functionality. but in case of second scenario when user does not select any language then we need to display the report in language defined on address level for that customer. For Ex: if the Invoice report is running for 4 invoices and have 2 different customers and their preferred language is different, suppose for 1 customer it is Chinese and for another one it is Japanese. Then we need to display the output in customer's preferred language only i.e for Japanese customer it should be in Japanese and for Chinese customer it should be in Chinese i.e 2 different templates will be applicable.
So as per this while submitting the concurrent request we need to check whether user has selected the language or not? And after making all the conditions check we will have to submit the xml publisher report using API. Do you have any suggestion how can we achieve this task?
Please suggest.
Thanks,
AS

Answer 1

Hi AS,
How about using a conc prog parameter for User selected language, and XML element data at customer level, then call a subtemplate (or multiple embedded regions in the same template) in the required language based on if or case logic in the template.
Regards,
Gareth