How to create a WIdget-BACKOFFICE with dynamic behavior similary a JSP

[Former Member]

We are trying to incorporate a widget in BackOffice where the user going to select an option from a HTML-SELECT representing a different report, in base at the option this going to show a form with input parameter´s for the report, this is a dynamic behavior similary a JSP, using javascript or jquery and ajax request. The query necessary for this report is described below: Is possible integrate this requirement in BackOffice ?

select distinct {prod.pk} as PRODUCTPK, {prod.code} as PRODUCTCODE, {catCountry.code} as COUNTRYCATEGORYCODE, {catYEAR.code} as ITKYEARCATEGORYCODE, {prod.SKUcode} as SKU, {prod.spanishDescription} as DESCRIPTION, {catITKSection.code} as SECTIONCATEGORYCODE, {catITKReference.code} as REFERENCECATEGORYCODE, {prod.yearAplication} as YEARAPPLICATION, Enumerationvalueslp.p_name as PLMNAME, {prod5.code} as ITALIKAPRODUCT, {prod5.elektraId} as SKUITALIKA,{catMODEL.code} as MODEL from { Spareparts as prod join CategoryProductRelation as level9 on {level9.target} = {prod.pk}

  join CategoryCategoryRelation as level8 on {level8.target} = {level9.source}
  join CategoryCategoryRelation as level7 on {level7.target} = {level8.source}
  join CategoryCategoryRelation as level6 on {level6.target} = {level7.source}
  join CategoryCategoryRelation as level5 on {level5.target} = {level6.source}
  join CategoryCategoryRelation as level4 on {level4.target} = {level5.source}
  join CategoryCategoryRelation as level3 on {level3.target} = {level4.source}
  join CategoryCategoryRelation as level2 on {level2.target} = {level3.source}
  join CategoryCategoryRelation as level1 on {level1.target} = {level2.source}
  join Category as catCountry on {catCountry.pk} = {level1.source}

}, { Spareparts as prod2 join CategoryProductRelation as level6 on {level6.target} = {prod2.pk}

  join CategoryCategoryRelation as level5 on {level5.target} = {level6.source}
  join CategoryCategoryRelation as level4 on {level4.target} = {level5.source}
  join CategoryCategoryRelation as level3 on {level3.target} = {level4.source}
  join CategoryCategoryRelation as level2 on {level2.target} = {level3.source}
  join CategoryCategoryRelation as level1 on {level1.target} = {level2.source}
  join Category as catYEAR on {catYEAR.pk} = {level1.source}

}, { Spareparts as prod7 join CategoryProductRelation as level5 on {level5.target} = {prod7.pk}

  join CategoryCategoryRelation as level4 on {level4.target} = {level5.source}
  join CategoryCategoryRelation as level3 on {level3.target} = {level4.source}
  join CategoryCategoryRelation as level2 on {level2.target} = {level3.source}
  join CategoryCategoryRelation as level1 on {level1.target} = {level2.source}
  join Category as catMODEL on {catMODEL.pk} = {level1.source}

}, { Spareparts as prod3 join CategoryProductRelation as level2 on {level2.target} = {prod3.pk}

  join CategoryCategoryRelation as level1 on {level1.target} = {level2.source}
  join Category as catITKSection on {catITKSection.pk} = {level1.source}

}, { Spareparts as prod4 join CategoryProductRelation as level1 on {level1.target} = {prod4.pk}

  join Category as catITKReference on {catITKReference.pk} = {level1.source}

}, Enumerationvalueslp

, { ItalikaProduct as prod5 join ItalikaProdSpareRel as rel on {rel.source} = {prod5.pk}

  join Spareparts as sp on {sp.pk} = {rel.target}

}

where {catMODEL.code} = $P{MODEL} and {prod.code} = {prod.code} and {prod2.code} = {prod.code} and {prod3.code} = {prod.code} and {prod4.code} = {prod.code} and {prod7.code} = {prod.code} and {sp.code} = {prod.code} AND {prod.plm} = Enumerationvalueslp.itempk

[Former Member]

moved from the yaas space

[former_member625836]

Hi ,

You definitively can implement such logic in Backoffice. Backoffice uses zk framework under the hood which allows any dynamic content you wish. Backoffice has many facilities that makes it even easier. You can define your own view in zul format, put there a reference editor (I'm guessing that a report type is an entity in database) and some content container, then inject them to your controller, annotate apropriate method with @ViewEvent to handle value change in your editor and then manage the contents of container.

Cheers, Jacek