Enterprise Integration and Onboarding [EIO]

Onboarding Legacy

Backend

Updated ETL to import order source data for applicable merchants.

Onboarding Legacy

Backend, UI

Added functionality to manage Order Destination Colors at the site level, and new sites are created with the colors set in the master document.

Onboarding Legacy

Backend

Created an API endpoint for retrieving a list of closed stores.

Onboarding Legacy

Backend, UI

Some fields and entities can be designated as master fields, allowing users to set values as company-level defaults for all site versions.

Onboarding Legacy

Backend, UI

Added functionality for importing data from the Omni "storedata" collection.

Onboarding Legacy

Backend, UI

Added support for discounts that apply based on a minimum order subtotal value.

Onboarding Legacy

Backend, UI

Configured onboarding for merchant parent organizations.

Onboarding Legacy

Backend

Updated the schema file naming and JSON formatting for OL configurations.

Onboarding Legacy

Backend

Extended Target First to update master documents as expected.

Onboarding Legacy

Backend

The trigger and refresh lambdas for store hours use the same audit collection in the database as expected.

Onboarding Legacy

Backend

The store hours workers retrieves changes and sends notifications in the active region.

Onboarding Legacy

Backend

Updated creation of site documents to use values from company-level master fields.

Onboarding Legacy

Backend

Updated the OL configuration to store Omni database configuration values as environment variables.

Onboarding Legacy

Backend

Onboarded nutrition data for applicable merchants.

Onboarding Legacy

Backend

Added an endpoint to retrieve closed site data.

Onboarding Legacy

Backend

Merchant-specific menu options are onboarded and displayed as expected.

Onboarding Legacy

Backend

Infrastructure improvements.

Onboarding Legacy

Backend

Increased store hour frequency for applicable merchants.

Onboarding Legacy

Backend

The "create_modifier_from_standard" option can apply to complex modifiers.

Onboarding Legacy

Backend

Images are imported as expected.

Data Mapper

Backend

Pipeline requests for companies without an ETL set up are skipped without triggering OL.

Data Mapper

Backend

Added an endpoint to retrieve closed site data.

Data Mapper

Backend

Added "Skipped" and "Bundled" columns to the dashboard grid.

Onboarding Legacy

Backend, UI

Calorie and image data is retrieved and displayed as expected.

Data Mapper

Backend

Infrastructure improvements.

Onboarding Legacy

Backend

Onboarded nutrition data for applicable merchants.

Onboarding Legacy

Backend

Updated Target First and Classic for consistency.

Onboarding Legacy

Backend

Added an endpoint to retrieve closed site data.

Onboarding Legacy

Backend

Added an endpoint to monitor EDM success.

Onboarding Legacy

Backend

Updated lambda concurrencies.

Onboarding Legacy

Backend

Increased the EDM sync process timeout to 15 minutes.

Onboarding Legacy

Backend

Updated the EDM site sync lambda to deactivate during deployment.

Onboarding Legacy

Backend

Variant class products can be retrieved and processed as expected.

Onboarding Legacy

Backend

Removing store hours from MDM removes them from the Xenial database as expected.

Onboarding Legacy

Backend

Discounts exclude modifiers attached to discounted items.

Data Mapper

Backend

Infrastructure improvements.

Data Mapper

Backend

Logs include the URLs of failed requests.

Data Mapper

Backend

Report .csv files contain error reason data as expected.

Data Mapper

Backend

Implemented pruning functionality for lambda versions in the Log Forwarder.

Data Mapper

Backend

Users can refresh store hours with the platform option as expected.

Onboarding Legacy

Backend

Classic OL automatically overwrites company preferences in DM to set the "whether_to_migrate_company" value to "false."

Onboarding Legacy

Backend

Synced the EDM and DM site lists to delete all permanently closed sites.

Onboarding Legacy

Backend

Target First OL handles product variations independently from other entities, and company-specific transformations are retrieved according to rules set by the company's configuration.

Onboarding Legacy

Backend

Removed the "OrderSource" table from the list of required entities for onboarding merchants that do not use that table.

Onboarding Legacy

Backend

Classic OL lambdas can import company names and the "handlers" module as expected.

Onboarding Legacy

Backend

Imported products are created at both the company and site level as expected.

Onboarding Legacy

Backend

Infrastructure improvements.

Onboarding Legacy

Backend

Product "item_type" values follow the expected configuration.

Onboarding Legacy

Backend

Classic OL sends application monitoring data as expected.

Onboarding Legacy

Backend

The store hours lambda only runs one request at a time as expected.

Onboarding Legacy

Backend

Logs include the URLs of failed requests.

Onboarding Legacy

Backend

Requests from Classic OL to Portal contain all expected attributes.

Onboarding Legacy

Backend

Updated lambdas to disable unnecessary processes and implement concurrency.

Onboarding Legacy

Backend

Completed onboarding for all expected merchants.

Onboarding Legacy

Backend

Orders are sent to the expected destination.

Data Mapper

Backend

Added endpoints for retrieving data from store-hours audit collections.

Data Mapper

Backend

Error logs include all expected information for attempts to refresh onboarding for inactive sites .

Data Mapper

Backend

Infrastructure improvements.

Data Mapper

Backend

Notification service messages use external URLs in links to Data Management environments.

Data Mapper

Backend

Configurations and files include the "LOG_LEVEL" variable as expected.

Onboarding Legacy

Backend

Cached all Target First and Classic configurations for all companies in an in-memory database.

Onboarding Legacy

Backend

The database can store history documents containing the tax amount field as expected.

Onboarding Legacy

Backend

Consolidated and added new information to logs.

Onboarding Legacy

Backend

Order destination master documents update as expected after a company switches from Classic to Target First onboarding.

Onboarding Legacy

Backend

Error logs include the expected event name for database connection issues.

Onboarding Legacy

Backend

Classic onboarding lambdas can retrieve company information as expected.

Onboarding Legacy, Data Mapper

Backend

Added support for custom SSR environments with an "SSR_ENV" environment variable.

Onboarding Legacy

Backend

Created new "ol_updates" database with the collection "dm_queue" and updated the history document.

Onboarding Legacy

Backend

Infrastructure improvements.

Onboarding Legacy

Backend

Setup basic ETL for new merchants.

Onboarding Legacy

Backend

Database queries do not run if the requested target is empty.

Data Mapper

Backend

Added API "GET" endpoints for all store hours collections.

Data Mapper

Backend

Requests are answered in the expected amount of time.

Data Mapper

Backend

Infrastructure improvements.

Onboarding Legacy

UI

Destination colors on kitchen screens display as expected.

Onboarding Legacy

Backend

ETL for product data creates a hash map of relevant data and ensures that the correct product and modifier IDs are maintained.

Data Mapper

Backend

The "history" and "config" endpoints have been converted from GoLang to NodeJS.

Data Mapper

Backend

Created endpoint to clear the configuration cache.

Data Mapper

Backend

Infrastructure improvements.

Data Mapper

Backend

The receiver lambda caches the queue URL for a limited time.

Data Mapper

Backend

OL configurations can be read from the Redis and cached.

Data Mapper

Backend

Components can be deployed to any region.

Data Mapper

Backend

Images are cached in Xenial's internal repository.

Data Mapper

Backend

OL configurations are triggered in the Target First queue.

Data Mapper

Backend

The "replay" endpoint functions as expected.

Data Mapper

Backend

Responses from the "history" endpoint include a "total" section.

Data Mapper

Backend

Updated logic to support multiple ETL queues.

Data Mapper

Backend

All messages to OL contain the relevant Company name.

Data Mapper

Backend

Updated the validation scheme of the "history" endpoint to support new refresh types.

Data Mapper

Backend

Updated the logger package.

Data Mapper

Backend

Event logs from an application include the application's region.

Data Mapper

Backend

Logs include all expected application code.

Data Mapper

Backend

Updated Redis client initialization.

Data Mapper

Backend

Created new "schema" endpoint to update configuration schema stored in the database.

Data Mapper

Backend

Connection is maintained as expected during pre-ETL service.

Data Mapper

Backend

Deployment to new regions functions as expected.

Data Mapper

Backend

Reconnection to the database functions as expected.

Data Mapper

Backend

Updated "target group" names to fit web services restrictions.

Data Mapper

Backend

Error information is logged as expected.

Data Mapper

Backend

Endpoints accept all expected access tokens.

Onboarding Legacy

Backend

Automated tests have been added for merchant onboarding.

Onboarding Legacy

Backend

Target first uses a separate lambda and message queue service for individual merchants.

Onboarding Legacy

Backend

"Datetime" validation errors are logged as expected.

Onboarding Legacy

Backend

Event logs from an application include the application's Region.

Onboarding Legacy

Backend

CSV data is parsed as expected.

Onboarding Legacy

Backend

Store hours are handled by separate database collections.

Onboarding Legacy

Backend

Store refresh notifications are received by merchants as expected.

Onboarding Legacy

Backend

Discount definitions include all expected fields, and discounts can be restricted by order source.

Onboarding Legacy

Backend

Store number requests now use an endpoint that contains the Company ID as well as the Site ID.

Onboarding Legacy

Backend

The creators of modifier collections are properly referenced.

Onboarding Legacy

Backend

Modifier collection data is created as expected.

Onboarding Legacy

Backend

Orders can retrieve all expected products.

Onboarding Legacy

Backend

The "Open Amount" discount is maintained during onboarding and has been added to the "seeds_ol" directory.

Onboarding Legacy

Backend

Order source documents are maintained as expected.

Onboarding Legacy

Backend

Infrastructure improvements.

Onboarding Legacy

Backend

The Open Amount discount has been added to the "seeds_ol" directory and is maintained during the onboarding process.

Onboarding Legacy

Backend

The creators of Modifier Collections are referenced as expected.

Onboarding Legacy

Backend

Automatic tests have been added for ETL.

Onboarding Legacy

Backend

Target first merchants have separate lambdas and queue services.

Onboarding Legacy

Backend

Datetime validation works as expected.

Onboarding Legacy

Backend

Logs record the region where an app serviced a request.

Onboarding Legacy

Backend

Store hours from different sources are handled by separate database collections.

Onboarding Legacy

Backend

Target first merchants receive the "store.refreshed" notification as expected.

Onboarding Legacy

Backend

Target first restricts discounts by order source as expected.

Onboarding Legacy

Backend

The dine in function is called by its expected name.

Onboarding Legacy

Backend

Merchants using target first receive the "store.refreshed" notification as expected.

Onboarding Legacy

Backend, UI

Store Hours support has been added to the API.

Onboarding Legacy

Backend

Pre-signed URLs are build using web service provider functionality.

Onboarding Legacy

Backend

The target first history document has been extended with new fields.

Onboarding Legacy

Backend

Components can be deployed to any region specified during deployment.

Onboarding Legacy

Backend

Base images are cached in Xenial's private image repository.

Onboarding Legacy

Backend

The store-hours refresh lambda only updates data streaming services when changes have been made.

Onboarding Legacy

Backend

Unused fields are removed from store-hours data before it is sorted.

Onboarding Legacy

Backend

The store-hours refresh lambda updates the existing audit as expected.

Onboarding Legacy

Backend

A forced update of Store Hours works as expected for absent configurations.

Onboarding Legacy

Backend

Deployment units have distinct values for the "logger" field.

Onboarding Legacy

Backend

The "keep inactive" option is supported in target first.

Onboarding Legacy

Backend

User signatures are assigned the expected expiration period of 1 week.

Onboarding Legacy

Backend

The store-hours refresh lambda writes the history document with values to distinguish between types of refreshes.

Onboarding Legacy

Backend

Logging has been added for incoming requests to the "/history" endpoint.

Onboarding Legacy

Backend

Destinations in target first onboarding work as expected.

Onboarding Legacy

Backend

Logs with internal server errors include information specifying the source of the error.

Onboarding Legacy

Backend

Parent Products are removed as expected when switching between onboarding types.

Onboarding Legacy

Backend

The target first OL-ETL lambda sends a message to data streaming services for empty updates.

Onboarding Legacy

Backend

Item and Modifier prices are copied with the expected Product and entity IDs.

Onboarding Legacy

Backend

Fields and entities in OL's configuration schema have been updated.

Onboarding Legacy

Backend

Infrastructure improvements.

OL History

Backend

New lambda can trigger a store hours refresh on demand, even when no changes have been made.

OL History

Backend

The s3 signer builds pre-signed URLs using the built-in functionality of web service providers.

OL History

Backend

Updated documentation.

OL History

Backend

History documents have been extended with new fields.

OL History

Backend

Components can be deployed to any region specified during deployment.

OL History

Backend

The store-hours flow has passed regression testing.

OL History

Backend

Store hours updates function as expected when the configuration is absent from the company.

OL History

Backend

Image files have been updated to use the new internal image repository.

OL History

Backend

A new "logger" field differentiates logs by the unit that created them.

OL History

Backend

The store hours refresh lambda only updates the web services stream when changes have been made.

OL History

Backend

The sorting function for store hours data only uses necessary fields.

OL History

Backend

The store hours refresh lambda updates audits as expected.

OL History

Backend

The keep inactive option is supported in target first.

OL History

Backend

Infrastructure improvements.

OL History

Backend

User signatures have an expiration period of one week.

OL History

Backend

Configuration schema have been updated.

OL History

Backend

Site reports copy item and modifier prices properly.

OL History

Backend

Logging for incoming requests has been added to the History endpoint.

OL History

Backend

Update messages to DM after a table refresh are correctly formatted to function in Pipeline.

OL History

Backend

Requests to clear the internal DM cache function as expected.

OL History

Backend

Failed messages are only sent to Data Mapper (DA) once as expected.

OL History

Backend, UI

Implemented payment services combo table.

OL History

Backend

Products are properly linked to all associated modifiers and discounts.

OL History

Backend

Menu group entity IDs function as expected.

OL History

Backend

Counters are properly integrated in history documents.

OL History

Backend

Differences between bundle-components for different companies have been reviewed and resolved.

OL History

Backend

Products have the expected number of default items.

OL History

Backend

Modifiers are properly linked to their variation info.

OL History

Backend

Modifier collection items match with other versions as expected.

OL History

Backend

Pay Type order sources can be processed with undefined values set to either "0" or "<null>."

OL History

Backend

Requests are sent to the "pol_api_upload" lambda with the full list of collections, not just collections that were changed.

OL History

Backend

Automated updates only apply to the expected discounts.

OL History

Backend

Data extraction and document creation use strict type transformation.

OL History

Backend

Secondary pricing for deliveries functions as expected.

OL History

Backend

Store hours are configured without duplicates.

OL History

Backend

Xenial point of sale runs as expected.

OL History

Backend

Only documents updated within seven days are archived, and the amounts of deleted and archived documents are logged.

OL History

Backend

The history cleanup handler has been deleted.

OL History

Backend

Order source prices are aggregated in one combined document.

OL History

Backend

ETL runs properly when the data types used by OL's internal server and the client's external server differ.

OL History

Backend

Menu updates initiated by a table refresh function as expected.

OL History

Backend

Seeded menus have been removed.

OL History

Backend

Parent entity IDs have been added to drink items.

OL History

Backend

"Distribute Across Scope" has been added to OL.

OL History

Backend

Target First onboarding processing functions as expected.

OL History

Backend

References to inactive products have been removed from product variations.

OL History

Backend

Master documents for store hours configurations and store hours configuration groups are properly implemented and active.

OL History

Backend

Order creation functions as expected.

OL History

Backend

Onboarding works properly for companies that don't use modifier groups.

OL History

Backend

All modifier collection documents have the expected modifier entity IDs.

OL History

Backend

Entity ID duplicates have been removed.

OL History

Backend

The EDM table can process discount links with "NULL" values.

OL History

Backend

Data creation is consistent between Classic and Target First.

OL History

Backend, UI

Master documents "CARRY-OUT" and "EAT_IN" are set to active and displayed as expected.

OL History

Backend

Support has been added for holiday store hours that are configured by date and take priority over regular store hours.

OL History

Backend

All EIO components have been updated to version 3.2.

OL History

Backend

Modifier definitions include all necessary fields.

OL History

Backend

New Discount Calculator features can be turned on/off.

OL History

Backend

Target First middleware fields function as expected.

OL History

Backend

Lookup documents are only created when necessary, and entity IDs are saved to the "entity_map" document.

OL History

Backend

Regular and holiday store hours have been consolidated through integration with partners' systems.

OL History

Backend

Support for store hours has been added to the API.

OL History

Backend

Tag entities have been updated, and unnecessary tags have been removed.

OL History

Backend

The store hours worker sends site IDs to the refresh lambda as expected.

OL History

Backend

The store hours refresh lambda updates only the expected documents and properly retains other documents.

Onboarding Legacy

Backend

The Store Hours Refresh lambda updates the existing audit on all sites as expected.

Onboarding Legacy

Backend

"Store Working Hours by Date" functionality has been implemented to add support for Holiday Hours.

Onboarding Legacy

Backend

Configuration and PStore values created for merchant store hours.

Onboarding Legacy

Backend

Unused fields are removed from incoming data before the data is sorted.

Onboarding Legacy

Backend

The refresh lambda only sends messages to data processing services if updates have been made.

Onboarding Legacy

Backend

The refresh lambda only makes changes to relevant documents during store-hours updates.

Onboarding Legacy

Backend

Infrastructure improvements.

Onboarding Legacy

Backend

Differences between bundle components in different versions have been resolved.

Onboarding Legacy

Backend

Differences between mismatched modifier collection items have been resolved.

Onboarding Legacy

Backend

Strict type transformation is applied during data extraction and document creation.

Onboarding Legacy

Backend

Distribute Across Scope field added to Classic OL, Target First OL, and ETL processes.

Onboarding Legacy

Backend

ETL processes function as expected for Target First onboarding.

Onboarding Legacy

Backend

References to inactive products were removed from all variations.

Onboarding Legacy

Backend

Master documents for "store-hours-config" and "store-hours-config-group" can be accessed as expected.

Onboarding Legacy

Backend

Companies can be onboarded through Target First as expected.

Onboarding Legacy

Backend

Added missing modifier entity IDs to modifier collection documents.

Onboarding Legacy

Backend

Duplicate modifier entity IDs have been removed.

Onboarding Legacy

Backend

Target First lambda works as expected for discount links with null values.

Onboarding Legacy

Backend

Target First and Classic use consistent methods of data creation.

Onboarding Legacy

Backend, UI

Master documents for "CARRY-OUT" and "EAT-IN" destinations are set to active and visible on the UI.

Onboarding Legacy

Backend

Added missing modifier definitions for "allowed_order_sources" field.

Onboarding Legacy

Backend

Regular and Holiday hours for all merchants and sites have been collected for system integration.

Onboarding Legacy

Backend

Target First updated to function correctly with company middleware.

Onboarding Legacy

Backend

Lookup documents are saved as expected by OL.

Onboarding Legacy

Backend

Added functionality to enable/disable the Discount Calculator and other recently updated OL features.

Onboarding Legacy

Backend

Tag entities have been updated to be compatible with company onboarding through Target First.

Onboarding Legacy

Backend

The store-hours worker sends site IDs to the refresh lambda as expected.

Data Mapper

Backend

JWT tokens are generated by Portal, not by Data Mapper.

Data Mapper

Backend

Daily mail reports now use their own, long-term tokens.

Data Mapper

Backend

Infrastructure improvements for generating stack credentials.

Data Mapper

Backend

Supports updated notification configuration logic.

Data Mapper

Backend

Adds the /store-hours/refresh endpoint to enable forcing a refresh of the store hours.

OL

Backend

XME menu update using OL table refresh works as expected.

OL

Backend

Drink items now have parent entity IDs to support searches.

OL

Backend

OL deactivates seeded menus for target first.

OL

Backend

Improved support for order source pricing.

OL

Backend

Only recent updates are archived and deleted to ensure the operation completes successfully. The number of days that determines a recent update is configurable in an environment variable.

OL

Backend

Store hours can be refreshed on demand.

Data Mapper

Backend

OL pre-generates entity master maps.

Data Mapper

Backend

Audit fields are available for all documents created by Data Mapper.

Data Mapper

Backend

Logs include only the expected details for transaction requests.

Data Mapper

Backend

Supports duplicate checking during reconciliation.

Data Mapper

Backend

The /batch/discard endpoint returns the correct response for IDs in the header.

Data Mapper

Backend

Inactive documents for child-prices are not returned by default.

Data Mapper

Backend

Supports force refresh flag, which updates master documents.

Data Mapper

Backend

All documents created by data mapper include the created_at, updated_at, created_by, and updated_by audit fields.

Onboarding Legacy, Onboarding Legacy History

Backend

Pay type values are updated to match EDM.

Onboarding Legacy

Backend

Error handling is improved for target first.

Onboarding Legacy, Onboarding Legacy History

Backend

The "check_marketplace_liability" flag is added for tax-definitions specified by EDM.

Onboarding Legacy

Backend

Company specific extractors can be defined in OL configuration.

Onboarding Legacy

Backend

Default order destinations can be set in a company's configuration for target first and are applied correctly.

Onboarding Legacy

Backend

Debug mode can be enabled for target first.

Onboarding Legacy, Onboarding Legacy History

Backend

Companies are migrated to target first.

Onboarding Legacy

Backend

The "restricted_order_source_entity_ids" is applied as expected.

Onboarding Legacy

Backend

The order source table is required.

Onboarding Legacy

Backend

OL raises an error when it encounters a failed API call.

Onboarding Legacy, Onboarding Legacy History

Backend

Company configurations are cached in redis.

Onboarding Legacy

Backend

Modifiers are created as expected.

Onboarding Legacy

Backend

Tag list displays in the DM UI.

Onboarding Legacy

Backend

Classic OL obtains "entity_id" values from "entity_map" and randomly generates new "entity_id" values to avoid conflicts.

Onboarding Legacy, Onboarding Legacy History

Backend

The "batch_id" value changes as expected when "is_active" changes.

Onboarding Legacy, Onboarding Legacy History

Backend

Modifier products and bundle components are added as expected and reference the correct groups and parent products.

Onboarding Legacy, Onboarding Legacy History

Backend

Pay-type availability can be determined by order source.

Onboarding Legacy, Onboarding Legacy History

Backend

Only one simultaneous run of OL for each site is possible.

Onboarding Legacy

Process

Variant types are defined and linked.

Onboarding Legacy

Process

Password encryption and storage are updated.

Onboarding Legacy, Onboarding Legacy History

Process

Trigger script is updated to use SQS.

Onboarding Legacy, Onboarding Legacy History

Process

A full data refresh flag is available for troubleshooting.

Onboarding Legacy, Onboarding Legacy History

Process

Product name format is updated, and names are displayed correctly.

Onboarding Legacy, Onboarding Legacy History

Process

Default order destinations are maintained and stored in a properties file.

Onboarding Legacy

Process

Update, delete, and create counters are implemented.

Onboarding Legacy, Onboarding Legacy History

Process

API responses are compressed to reduce internal server errors due to size limits.

Onboarding Legacy

Process

Discounts update as expected.

Onboarding Legacy

Process

Conditional pricing support is added.

Onboarding Legacy

Process

Elastic APM is updated.

Onboarding Legacy

Backend

Supports marketplace facilitator tax-definitions when specified from EDM.

Onboarding Legacy

Backend

Request fails instead of deleting order sources when a 5xx response is returned.

Onboarding Legacy

Backend

Order source is required for all companies the use the order-source extractor.

Onboarding Legacy

Backend

The check_marketplace_liability flag is added to tax definitions to support marketplace facilitator taxes.

OL History

Backend

Tax calculations are updated for accuracy.

OL History

Backend

Error handling is updated to support cases that can be retried.

OL History

Backend

Breakpoint tables are translated to support the "rate above" algorithm.

OL History

Backend

Companies extract tables are now based on a company-specific list of extractors.

OL History

Backend

Product images are hosted by Xenial and include a prepended S3 bucket URL.

OL History

Backend

Default order destinations are set in a company's configuration.

OL History

Backend

Audit document is updated regardless of the extent of an update.

OL History

Backend

Allowed_order_source_entity_ids are updated for products and modifiers.

OL History

Backend

Product_tag_entity_ids are fixed for product_price collection.

OL History

Backend

Entity_id values are updated for consistency and preserved to support rollbacks.

OL History

Backend

Product variations information is updated to support modifiers.

OL History

Backend

Multi-apply criteria can be enabled in the discount-definition object.

OL History

Backend

OL creates time periods from tblTimePeriods to support time periods used for menus.

OL History

Backend

Prices for side items are consistent.

OL History

Backend

Alternate kitchen names are set from the MonitorDesc table.

OL History

Backend

OL imports and populates destination shortnames based on the value stored in IRIS.

OL History

Backend

Product and order source restrictions are updated.

OL History

Backend

Bundled item and discount definitions are updated for consistency.

OL History

Backend

Image URLs are created consistently for products with empty values in the ItemInfo table.

OL History

Backend

Debug mode is available for OL.

OL History

Backend

Order destination definitions are consistent.

OL History

Backend

Restricted order source entity IDs are updated.

OL History

Backend

Order source table is now required.

OL History

Backend

OL returns an error response for failed API calls to EDM tables that are not required.

OL History

Backend

OL builds entity IDs based on the reporting category's document builder.

OL History

Backend

OL attempts to identify configurations in Redis before getting configurations from MongoDB.

OL History

Backend

Product variation construction is updated to work with modifier group members.

OL History

Backend

Tag lists are updated to work with DM UI.

OL History

Backend

Classic OL generates random IDs for entitites and saves them to the entity map.

OL History

Backend

Classic OL adds parent entities to modifier collections.

OL History

Backend

OL creates discount evaluations and application criteria from discount tables.

OL History

Backend

Bundle component IDs are updated for consistency.

OL History

Backend

Default variant types are updated and applied to standard type variants.

OL History

Backend

Password management is updated to save processor cycles.

Data Mapper

Backend

Reduce log volume size for /xenial-proda/da-proda-post-etl.

Data Mapper

Backend

Add /batch endpoint for triggering tablerefresh.

Onboarding Legacy

Backend

OL now fails instead of deleteing order sources when DM returns a 5xx response to a query of the OrderSource table.

Onboarding Legacy

Backend

Added new entities, logic, seeding, and processes to support enterprise datasets onboarded from EDM

Onboarding Legacy

Backend

Added order source restriction for products

Onboarding Legacy

Backend

Products with "modifier" type now set sibling modifier variations to an empty array so the parent is the only modifier that references all related modifiers

Products with "modifier" type that do not have a parent modifier or child modifiers are now set as inactive

Products with "standard" type now have "parent_entity_id" and "variant_entity_it" removed

Onboarding Legacy

Backend

Updated OL to set the alternate kitchen name from the MonitorDesc in EDM when creating or updating product objects

Onboarding Legacy

Backend

When creating or updating destination objects, updated OL to import and populate:

Onboarding Legacy

Backend

When compared, products no longer show different "is_bound" value based on which OL created them

Onboarding Legacy

Backend

Fixed discount differences between the OLs

Onboarding Legacy

Backend

All image paths in an "ItemInfo" table now have a file name instead of having "None" or "<NULL>" values

Onboarding Legacy

Backend

Added ability to edit a single object across multiple sites with different values at each site in cases where the object differs from site to site

Onboarding Legacy

Backend

Added delivery of logs containing all event information in Log Reader under "OL" app code and "ol_logger" logger

Onboarding Legacy

Backend

Added logs for failed cache refresh requests

Onboarding Legacy

Backend

Added ability to add changes to a cart to support scheduling a group of changes at once and redeploy those changes to another group of sites

Onboarding Legacy

Backend

Added "save_cart" property with 3 states: true, false, and absent (which uses default false value)

Onboarding Legacy

Backend

Added ability to create records from "tblTimePeriods" into the time-periods collection to use to establish the starting time per day of week for the different menu time periods

Onboarding Legacy

Backend

Added ability to configure multiple sets of apply criteria so the discount calculator can use it to apply the discounts to the correct items

Onboarding Legacy

Backend

Added new fields to support /history endpoint

Onboarding Legacy

Backend

Added ItemsInfo table which includes ItemNum, display name, and description

Onboarding Legacy, Onboarding Lambda History

Backend

Added new entities, logic, seeding, and processes to support enterprise datasets onboarded from EDM

Onboarding Legacy, Onboarding Lambda History

Backend

Added new ETL process that supports Commander to create a POS onboarding process for Verifone

Onboarding Legacy

Backend

Added "discount_restriction_order_source_ids" variable to restrict discounts by order source to support applying discounts based on where they come from (POS, mobile app, delivery partner, etc.)

Onboarding Legacy

Backend

Added ability to have different prices for the same product based on the order source, such as in-store vs online app vs 3rd party delivery providers

Onboarding Legacy

Backend

Added a priority field to help the price engine select between the order-source price and regular price without an order source

Onboarding Legacy

Backend

Added "company_code" field for ETL to use when configuring instead of "company_id" to make ETL configurable

Onboarding Legacy, Onboarding Lambda History

Backend

Created Fiesta ETL for onboarding

Onboarding Legacy

Backend

"entity_hash" values are now created for "menu_category" and "menu-item-group"

Onboarding Legacy

Backend

Updated auditing for "entity_hash" and "entity_master" collection to verify that new hashes only generate if the entities were changed by adding the following fields: created_at, created_by, updated_at, updated_by

Onboarding Legacy

Backend

Tax amounts using decimal class are now rounded to avoid floating decimal issues

Onboarding Legacy

Backend

Data Mapper now takes ownership of notifications to clients for S3 files instead of OL sending them as well

Onboarding Legacy

Backend

Updated validation scheme for creating and updating configs in OL History to prevent OL configs being created and updated incorrectly

Onboarding Legacy

Backend

Updated Delete & Archive service to check for a flag stored in OL configs for OL to look for is_active false in docs and update them to is_deleted true and set active docs to is_active false and is_deleted false before triggering D&A

Onboarding Legacy

Backend

OL retries processing a batch if it failed to get config until the 5th retry and then Data Mapper performs an attempt to retry the batch until the 5th retry

Onboarding Legacy

Backend

Updated processing to delete entities to use the "entity_map" for "entity_id" preservation, the "entity_hash" to find the difference (hash&cash) and to find the legacy IDs of deleted entities, and the creator's data to find legacy IDs of the updated entities

Onboarding Legacy

Backend

Updated delete operations from autotests to have correct "entities_deleted" section in SNS

Onboarding Legacy

Backend

Updated OL to set the "exclude_modifiers" field in discount definitions

Onboarding Legacy

Backend

Updated table refresh runs to find existing "Change Cart" for the current company and date and:

Onboarding Legacy

Backend

Updated OL to check if all children are restricted by a certain order source and restricts the created parent modifier by the same order source

Onboarding Legacy

Backend

Updated Delete&Archive to allow "is_active:False" entities onboarding and load deleted entities from the DM API with the "include_inactive" flag

Onboarding Legacy

Backend

The "sqs_refresh_start" field values are now defined correctly to prevent schema validation errors

Onboarding Legacy

Backend

Updated queries to "entities_updated" to return documents for TAG entity from DM API and added an extra parameter "use_site_ids_filter=true" and return one document instead of one

Onboarding Legacy

Backend

"api_upload" lambda now gets tag documents from DM

Onboarding Legacy

Backend

OL now marks existing inactive documents with "is_deleted=true" during the creation entity operation

Onboarding Legacy

Backend

Updated speed of parallel data extraction from EDM

Onboarding Legacy

Backend

Updated fields for deployed system packages to required: deployed_at, deployed_by, entity_types, site_ids

Onboarding Legacy

Backend

Deleted old document and old mapping without legacy_id

Onboarding Legacy

Backend

Updated creation of time-periods documentation to group similar days into one and split time blocks that go past midnight into two

Onboarding Legacy

Backend

Documents now stay in DM with "is_active=false" and "is_deleted=false" while the "kee_inactive" feature is enabled

Onboarding Legacy

Backend

Set the "is_required_table" flag to false if the "IRIS_dbo_tblOrderSourceMenus" table is not present or empty

Onboarding Legacy

Backend

Replaced the name of a product from ItemMaster with the value from the "Name" column of the "ItemInfo" table for items specified in the table

Onboarding Legacy

Backend

Updated filtering of bundle components by menu id

Onboarding Legacy

Backend

Updated order source restrictions to add every order source so the id defined for each menu in the "OrderSourceMenus" table is the only order source the menu is available for

Onboarding Legacy

Backend

Updated OL to insert the parent modifier created by OL instead of the modifier defined in EDM

Onboarding Legacy

Backend

Table refresh is no longer failing with errors

Onboarding Legacy

Backend

Changed default destination from 2 to 8

Onboarding Legacy

Backend

Added custom extractor to fetch store hours from an external source since OL doesn't create store hours for sites

Onboarding Legacy

Backend

Updated order source restrictions to apply only to automatic discounts

Onboarding Legacy

Backend

Removed obsolete environment variables to prevent exceeding the 4KB limit for AWS

Onboarding Legacy

Backend

Updated scheduled updates to receive all store hours and check for changes since the previous update and only update the changed store hours

Onboarding Legacy

Backend

Updated config to store SNS name instead of SNS ARN and updated OL to use SNS topic name

Onboarding Legacy

Backend

Lambda no longer fails if the store has an incorrect "bk_store_number" and instead continues and logs a warning

Onboarding Legacy

Backend

The scheduled "store-hours-worker" no longer starts for a specific store every 30 minutes and logs it without any change in API response

Onboarding Legacy

Backend

Carts can now save without a validation error

Onboarding Legacy

Backend

OL no longer combines the child tag price fields when the amount matches

Onboarding Legacy

Backend

OL now recognizes changes made to standard order source pricing

Onboarding Legacy

Backend

Updated "dm_first" fields to be configurable to allow modifications of the same entity from DM and EDM/CDM

Onboarding Legacy

Backend

Changed "OrderSource" table to required and added logging for when it converts table column names and warnings if the table fails to convert

Onboarding Legacy, Onboarding Lambda History

Backend

Improved product document creation time and ETL total time

Onboarding Legacy, Onboarding Lambda History

Backend

Site menu creates using EDM data with proper payload (no missing fields)

Onboarding Legacy, Onboarding Lambda History

Backend

Updated OLH to use new SSR URL

Onboarding Legacy

Backend

Updated "ItemInfo" table to prepend an S3 bucket URL to the image name and store the S3 bucket link in OL configs

Onboarding Legacy, Onboarding Lambda History

Backend

The scheduled "store-hours-worker" now creates store hours with "external_id" value as a string

Onboarding Legacy

Backend

Updated audit document so there are no extra triggers of the "qa_pol_store_hours_worker" lambda

Data Mapper

Backend

Created new company with 100 sites for testing bulk editing of new entities

Onboarding Lambda History

Backend

Added new ETL process that supports Commander to create a POS onboarding process for Verifone

Onboarding Lambda History

Backend

Added new entities, logic, seeding, and processes to support enterprise datasets onboarded from EDM

Onboarding Lambda History

Backend

Added mapping for the delivery order source in configurations to get order sources associated with delivery and add them to the pricing document when the "delivery all" order source is defined for a price

Onboarding Lambda History

Backend

Added ability to have different prices for the same product based on the order source, such as in-store vs online app vs 3rd party delivery providers

Onboarding Lambda History

Backend

Added ability to configure multiple sets of apply criteria so the discount calculator can use it to apply the discounts to the correct items

Onboarding Lambda History

Backend

Added a priority field to help the price engine select between the order-source price and regular price without an order source

Onboarding Lambda History

Backend

Added "company_code" field for ETL to use when configuring instead of "company_id" to make ETL configurable

Data Mapper

Backend

Removed reconciliation for tags and tax groups

Onboarding Lambda History

Backend

Added custom extractor to fetch store hours from an external source since OL doesn't create store hours for sites

Onboarding Lambda History

Backend

Updated order source restrictions to apply only to automatic discounts

Onboarding Lambda History

Backend

Removed obsolete environment variables to prevent exceeding the 4KB limit for AWS

Onboarding Lambda History

Backend

Updated scheduled updates to receive all store hours and check for changes since the previous update and only update the changed store hours

Onboarding Lambda History

Backend

Lambda no longer fails if the store has an incorrect "bk_store_number" and instead continues and logs a warning

Onboarding Lambda History

Backend

Updated OL to support "keep_inactive" functionality

Onboarding Lambda History

Backend

Updated config to store SNS name instead of SNS ARN and updated OL to use SNS topic name

Onboarding Lambda History

Backend

The scheduled "store-hours-worker" no longer starts for a specific store every 30 minutes and logs it without any change in API response

Onboarding Lambda History

Backend

Carts can now save without a validation error

Onboarding Lambda History

Backend

OL no longer combines the child tag price fields when the amount matches

Onboarding Lambda History

Backend

OL now recognizes changes made to standard order source pricing

Onboarding Lambda History

Backend

Updated "dm_first" fields to be configurable to allow modifications of the same entity from DM and EDM/CDM

Onboarding Lambda History

Backend

Changed "OrderSource" table to required and added logging for when it converts table column names and warnings if the table fails to convert

Data Mapper

Process

Updated the following variables to be configurable via export to support autoscaling and task placement:

Data Mapper

Backend

Updated the delta SNS notification by adding new query parameter to check if site id filter is true

Onboarding Legacy

Backend

Update all configuration documents to match on all stacks

Onboarding Legacy

Backend

OrderSource table is now required, added additional logging, and OL now warns you if the table fails to convert

Onboarding Legacy

Backend

Updated Data Mapper to take ownership of notifications so data is not loaded twice and notifications logic isn’t supported in multiple places

Onboarding Legacy

Backend

Created a new validation scheme in OL History for creating and updating configurations

Onboarding Legacy

Backend

Added new “restrict_availability_order_source” flag to indicate if any restrictions are present in the product

Onboarding Legacy

Backend

Created separate SQS for companies and subscribed OL to appropriate SQS

Onboarding Legacy

Backend

Created company-specific lambdas subscribed to appropriate SQS queues to separate “store-refresh” flow for companies

Onboarding Legacy

Backend

Added “sort_price” in the discount definition

Onboarding Legacy

Backend

Added “Name” column to ItemInfo table

OL History

Backend

Added audit fields to ensure new hashes are generated only if the corresponding entities were changed

OL History

Backend

Added logs for failed cache refresh requests

OL History

Backend

Added required fields for deployed system packages

OL History

Backend

Created new lambda focused on DM data creation

OL History

Backend

Created CM API functionality

OL History

Backend

Added “Name” column to ItemInfo table

OL History

Backend

Created new target-first product document that contains all fields the current OL ETL creates

OL History

Backend

Created entities for product price and time period

OL History

Backend

Created entity for order destinations

OL History

Backend

Created a new variable to restrict discounts by order source

Onboarding Legacy

Backend

Updated storing of Portal integrator key credentials in the AWS parameter store as secure strings

Onboarding Legacy

Backend

Updated Item Availability logic to determine whether products should be brought over as active or inactive and set appropriate order source restrictions

Onboarding Legacy

Backend

Serverless configuration had an incorrect parameter

Onboarding Legacy

Backend

Updated OL to do a kill&amp;fill on all documents updated with the new “legacy_entity_id” and “entity_id” fields

Onboarding Legacy

Backend

SNS success notification was sending the wrong message type

Onboarding Legacy

Backend

Removed “is_active” field from the list of fields that are removed before creating a hash

Onboarding Legacy

Backend

OL was acquiring the name instead of the store number from Portal site properties when the two fields had different values

Onboarding Legacy

Backend

Absent “EffectiveDate” field resulted in OL not adding restrictions to products that need them

Onboarding Legacy

Backend

Updated same products to not contain duplicates in the “product-price” collection and the time period entity id after updating “ TimePeriod” value in EDM

Onboarding Legacy

Backend

Changed OL to add “product_tax_inclusive” field with the value matching the “tax_inclusive” value

Onboarding Legacy

Backend

Onboarding Legacy

Backend

Changed default price to be tagged with the type standard and the second price to be tagged with the type conditional when handling multiple standard prices

Onboarding Legacy

Backend

Combos and associated sandwiches in the variations were referenced in the menu structure incorrectly

Onboarding Legacy

Backend

Updated discount creator to:

Onboarding Legacy

Backend

Updated OL to include the “exclude_modifiers” field in discount definitions

Onboarding Legacy

Backend

Updated order source restrictions for all discounts to apply only to Automatic discounts

OL History

Backend

Updated logs to deliver OL logs with all information about events to Log Reader

OL History

Backend

Updated table refresh runs to include:

OL History

Backend

Updated new ItemsInfo table with an item number, a display name, and a description to replace item names from the ItemMaster table

OL History

Backend

Data couldn’t be deactivated for sites with old mappings without a “legacy_id” field

OL History

Backend

Updated creation of time-periods document to:

OL History

Backend

Removing entity from EDM and deleting the document by Delete&amp;Archive was adding “is_deleted” field set to true

OL History

Backend

OL failed to onboard due to requiring tables that haven’t been created

OL History

Backend

Updated variant collection and product variations to align data onboarding flow

OL History

Backend

Updated OL to filter the bundle component items by menu id and to find items belonging to embedded menus and add them as bundled components

OL History

Backend

Updated order source id restrictions to include every order source so the id defined is the only order source the menu is available for

OL History

Backend

Updated OL to insert the parent modifier it creates for group related modifiers when creating a product’s default build

OL History

Backend

Updated product builds to align data onboarding flow

OL History

Backend

Updated data seeded by DM to not be removed or conflicting links created so EDM menus will work with POS and DM UI

Data Mapper

Backend

Added Data Mapper repository

POS Connector

Backend

Receiving SQS messages resulted in a signature expired error

POS Connector

Backend

Updated Xenial Cloud Connector (XCC) to trigger Onboarding Lambda (OL) only once for each XCC start

POS Connector

Backend

Updated XCC to include a log for outage recovery

POS Connector

Backend

XCC was sending sitestatus.json to the Quarantine\Out folder

POS Connector

Backend

Update “FetchError” log to include the response body

POS Connector

Backend

Amazon Web Services (AWS) credentials were cached after being received when the request completed instead of when the first request is made

POS Connector

Backend

XCC didn’t install in the desired folder when using a custom path during command-line installation

POS Connector

Backend

Improved test coverage

POS Connector

Backend

Changed configuration update process:

POS Connector

Backend

Updated SQS readable stream to support long polling

POS Connector

Backend

Updated requests that go through the proxy to include company and site id headers

POS Connector

Backend

Updated proxy default configuration to:

POS Connector

Backend

Portal token was not being refreshed after receiving a 401 error

POS Connector

Backend

Changed JWT key to not be present in the repository

POS Connector

Backend

Large amount of validation errors were occurring and the pipeline attempted to push them. The “messageSizeLimit” has been decreased to force an upload to S3 and reference encoding prior to pipeline delivery to reduce errors

POS Connector

Backend

Change the order of messaging processing in the “out” folder so that sitestatus.json is now processed first

POS Connector

Backend

Updated logging:

POS Connector

Backend

Updated logging:

POS Connector

Backend

Updated XCC to obtain the local start time when service starts and log it

POS Connector

Backend

Installing XCC was being set under the current user instead of in the local machine

POS Connector

Backend

The XCC froze and no longer processed outbound messages if the pipeline sent a 401 error

POS Connector

Backend

Updated XCC to continue retrying if the pipeline sends a 401 error

POS Connector

Backend

Upgraded the AWS software development kit (SDK) to version 2.406.0 to resolve signature not yet current error

POS Connector

Backend

Invalid responses from the pipeline didn’t result in an error message or in resetting the AWS credentials

POS Connector

Backend

For stream transform error: