Service - Catalog Standard: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 18: | Line 18: | ||
configKey: {eg: "CatalogTreeServiceName"} | configKey: {eg: "CatalogTreeServiceName"} | ||
configValue: {eg: "CatalogTreeStandard"} | configValue: {eg: "CatalogTreeStandard"} | ||
} | |||
</syntaxhighlight> | |||
<syntaxhighlight lang="JavaScript"> | |||
{ | |||
configTag: "TranslationsServiceName" | |||
configKey: "TranslationsServiceName"" | |||
configValue: xxx // eg: "Translations" | |||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Revision as of 14:28, 3 March 2021
Overview
Handler service for the standard catalog type.
Repository
https://bitbucket.org/stb_working/catalog-standard/src/master/
DynamoDB tables
Standard Config Table Per Service
Configuration tags
{
configTag: "CatalogTreeServiceName"
configKey: {eg: "CatalogTreeServiceName"}
configValue: {eg: "CatalogTreeStandard"}
}
{
configTag: "TranslationsServiceName"
configKey: "TranslationsServiceName""
configValue: xxx // eg: "Translations"
}
Catalog
Fields
- catalogId
- (partition key)
- filter
- stringified object containing default search result filter
- requiredData
- stringified object containing default search result requiredData
- searchType
- product|variant|variantProduct
- default searchType
- categoryTreeServiceName
- eg: "CategoryTreeStandard"
Ideas
- One filter that will normally be on, but could be removed, is to only show items that have available quantity, this will tie into the locationtreenodeid.