Configuring Filters for Components
Each of the following components can use a filter to help further constrain the set of data displayed in the dashboard. Once configured, an additional Filter by: attribute list appears in each component. The list contains the possible values for the specified filter attribute.
To add a filter to one of these reports, the administrator must override the filterAttribute properties by adding entries for these properties to the custom.lcs.properties file.
Each filter attribute property identifies a single internal name.
Season Dashboard
If the following property is set, the filter list appears. The legal set of values for this property is limited to the set of internal names defined on the Season type.
com.lcs.wc.season.SeasonSummary.filterAttribute=
DEFAULT: No value (no filter is visible in the component). If a value is specified, it must exactly match a defined internal name.
RFQ Dashboard
If the following property is set, the filter list appears. The legal set of values for this property is limited to the set of internal names defined on either the Product or RFQ type. To include the name of a product attribute, use the prefix Product (for example, Product.division). To include the internal name of an RFQ attribute, use the prefix RFQ (for example, RFQ.status).
|
|
For the RFQ type, the RFQ attribute defined as the filter must not be defined on the attribute type context for the response header.
|
For the RFQ type:
com.lcs.wc.sourcing.RFQSummary.filterAttribute=
DEFAULT: No value (no filter is visible in the component)
For the RFQ Response type:
com.lcs.wc.sourcing.RFQSummary.responseFilterAttribute=
DEFAULT: No value (no filter is visible in the component)
com.lcs.wc.sourcing.RFQSummary.groupByDefaultAttribute=status
DEFAULT: status
Order Confirmation Dashboard
If the following property is set, the filter list appears. The legal set of values for this property is limited to the set of internal names defined on the Order Confirmation, Product, or Sourcing Configuration types, or the following modeled attributes.
Example: Order Confirmation.status and hardAtt values such as hardAttseasonMasterReference.key.id for season filter and hardAttorderSourceReference.key.branchId for vendor filter.
com.lcs.wc.sourcing.OCSummary.filterAtt=Order Confirmation.status
DEFAULT: Order Confirmation.status
com.lcs.wc.sourcing.OCSummary.groupByDefaultAttribute=status
DEFAULT: status
Material Sample Dashboard
If the following property is set, the filter list appears. The legal set of values for this property is limited to the set of internal names defined on the Color, Material, Sample, or Supplier types, or the following modeled attributes. For example, to include the name of a color attribute, use the prefix Color.
com.lcs.wc.sample.MaterialColorSampleSummary.filterAttribute
DEFAULT: No value (no filter is visible in the component)
The legal set of values for this property is limited to the set of internal names defined or the following modeled attributes.
Example: Product.sampleStatus and hardAtt values such as hardAttColor.thePersistInfo.theObjectIdentifier.id for GroupBy.
com.lcs.wc.sample.MaterialSampleSummary.groupByDefaultAttribute=sampleStatus
DEFAULT: sampleStatus. The attribute can live on the Color, Material, Sample, and Supplier types.
Product Sample Dashboard
If the following property is set, the filter list appears. The legal set of values for this property is limited to the set of internal names defined on the Sample, Product, Sourcing Configuration, or Specification types, or the following modeled attributes. For example, to include the name of a product attribute, use the prefix of Product (for example, Product.sampleStatus).
com.lcs.wc.sample.ProductSampleSummary.filterAttribute
DEFAULT: No value (no filter is visible in the component)
com.lcs.wc.sample.ProductSampleSummary.groupByDefaultAttribute
DEFAULT: sampleStatus
