Create a Report as follows: <Resource Id="stockReport" Name="Stock Report" Type="Report"> <ParameterBag Id="parameters" Name="parameters" Type="Parameters"> <Parameter Id="objectType" Name="Object Type" Type="String" Interpretation="Resource-Ref" Uom="Slot" Value="Slot" /> </ParameterBag> <ParameterBag Id="columns" Name="Display Columns" Type="Display"> <Parameter Id="location" Name="Location" Type="String" Interpretation="Resource-Ref" Uom="Location" Value="$name" /> <Parameter Id="storage" Name="Storage" Type="String" Interpretation="Resource-Ref" Uom="Storage" Value="$name" /> <Parameter Id="section" Name="Section" Type="String" Interpretation="Resource-Ref" Uom="Section" Value="$name" /> <Parameter Id="slot" Name="Slot" Type="String" Interpretation="Resource-Ref" Uom="Slot" Value="$name" /> <Parameter Id="product" Name="Product" Type="String" Interpretation="Resource-Ref" Uom="Product" Value="$name" /> <Parameter Id="quantity" Name="Quantity" Type="String" Interpretation="Resource-Ref" Uom="Slot" Value="Bags/parameters/quantity" /> <Parameter Id="maxQuantity" Name="Quantity" Type="String" Interpretation="Resource-Ref" Uom="Slot" Value="Bags/parameters/maxQuantity" /> </ParameterBag> <ParameterBag Id="joins" Name="Joins" Type="Joins"> <Parameter Id="Product" Name="Product" Type="String" Interpretation="Resource-Ref" Uom="Product" Value="Slot" /> <Parameter Id="Section" Name="Section" Type="String" Interpretation="Resource-Ref" Uom="Section" Value="Slot" /> <Parameter Id="Storage" Name="Storage" Type="String" Interpretation="Resource-Ref" Uom="Storage" Value="Section" /> <Parameter Id="Location" Name="Location" Type="String" Interpretation="Resource-Ref" Uom="Location" Value="Storage" /> </ParameterBag> </Resource> This creates a report for objects of type Slot, where a Join is done on multiple objects: Slot -> Product -> Section -> Storage -> Location Thus the columns can then be fetched from different joing objects. The joing is done by searching for a Parameter on the joined object on the ParameterBag "relations". See the example XML on how this is done. Or ask eitch@eitchnet.ch to write a proper documentation =)) Filtering is missing, and will be added later |
||
---|---|---|
dev | ||
li.strolch.agent | ||
li.strolch.bom | ||
li.strolch.model | ||
li.strolch.performancetest | ||
li.strolch.persistence.postgresql | ||
li.strolch.persistence.xml | ||
li.strolch.planningwebapp | ||
li.strolch.privilege | ||
li.strolch.rest | ||
li.strolch.service | ||
li.strolch.testbase | ||
li.strolch.tutorialapp | ||
li.strolch.tutorialwebapp | ||
li.strolch.utils | ||
li.strolch.website | ||
li.strolch.xmlpers | ||
strolch_minimal | ||
strolch_minimal_rest | ||
.gitignore | ||
LICENSE | ||
README.md | ||
createBundle.sh | ||
deploy.sh | ||
hotfix.sh | ||
pom.xml | ||
release.sh | ||
setVersion.sh |
README.md
Strolch
The main repository which contains all of Strolch.
Strolch consists of the following modules:
- li.strolch.utils
- li.strolch.privilege
- li.strolch.agent
- li.strolch.model
- li.strolch.persistence.postgresql
- li.strolch.persistence.xml
- li.strolch.rest
- li.strolch.service
- li.strolch.testbase
With the following test applications:
- li.strolch.tutorialapp
- li.strolch.tutorialwebapp
- li.strolch.planningwebapp
- strolch_minimal
- strolch_minimal_rest
And of course the website itself:
- li.strolch.website
Find more to Strolch at our website: http://strolch.li