Lead Management Monorepo

Releases

This repo contains two projects -- the manage ember application, and the monorepo. Both of the versions for these projects must remain in sync. Before releasing the monorepo, check if changes to the ember application should be deployed. If so, increment the ember app's package.json version accordingly before releasing via lerna.

For example, if the monorepo is at version 1.2.3, the ember app is at 1.2.3, and a new feature was added:

1. Increment and commit the version in the manage application's package.json file manually to match the expected lerna version (1.3.0).
2. Release the monorepo: cd monorepo; lerna version minor

Omeda Migration Notes

• need "click stream" api that can search for all click events during a certain date range
• need to determine if the deployment name can be included in merge vars
• fix ad creative trackers to use new customer IDs... see graphql/resolvers/ad-creative-tracker.js
• fix allExtractedUrlsForSend and searchExtractedUrlsForSend queries
• fix identity references in excluded-email-domain schema
• determine how to handle not-found customers
• need to update omeda-email-deployment-urls when urls or hosts change
• fix cache of extracted urls
• legacy excluded/inactive identity data needs to move to the new DB so the old DB can eventually be removed
• use https://www.omeda.com/knowledge-base/customer-change-lookup/ API for customer updates
• drop behaviors - this can be done in onq now
• re-enable Identity.inactiveCampaigns and Identity.inactiveLineItems resolvers
• review campaign and line item resolvers
• handle LineItem.formLineItemLeads query, and LineItem.formLineItemChoiceFilters,createFormLineItem mutations
• restore EmailCampaign.urls,hasEmailSends,urlCount,urlGroups
• restore or move emailReportService.buildEmailMetrics
• test new ad click/impression trackers
• add meta tags to website for scraping companies/tags
• do not cache indm websites when crawling

Onboarding

1. Duplicate an existing namespace and reconfigure containers. Use new GAM, Omeda, Brightcove credentials
2. Add tenant to lead-management.tenants on Aquaria
3. Add permissions to LM user db.grantRolesToUser('lead-management', [{ role: 'readWrite', db: 'lead-management-TENANTKEY' }])
4. Generate DB/Indexes: Set tenant key and boot dev instance to auto-index