Page Comparison

...

Task:

Jira Legacy
server System Jira serverId a1b4b5ef-b15c-306f-abe2-636e0c2e7fe6 key PRD-618

Outline:

We need to make a new shopify plugin for Netcomm. This plugin will be copy of their old plugin. Here are the feature list of old plugins:

eKomi Official Shopify Plugin for NetComm

SummaryThis plugin will be made with new Shopify Designs (please check eKomi Plugins for reference ) .

Overview:

A The plugin that will install itself and have basic config settings.
Plugin purpose will be to launch widgets on.
The plugin captures NetcommId and eKomi Shop details.
Segments:

Shopify install → This is broken down into a number of steps:
DB configuration - new table / entity.
Shopify App Admin config → add apps nav uri’s.

Main Dev steps:

1. Request from shopify to the app with the hmac and shop.
   The app recodes and removes the hmac value, sends authorization request with shop api key or client id and with the redirect url. Then it redirects with callback.

2. Request from shopify with callback while process is still actually in the install method.
   app parses request in callback action method, creates a request to shopify to get the access token.
   Then the app registers the un-install webhook.

3. Then upon success the app should return the application settings form.
   This is where the NetcommId and eKomi details are captured.
   Form then validates & saves.

4. Check from start to finish. Shopify has a list of app requirements.

5. Refactor to include omission of Customer & Store Redaction and privileges for shopify are not needed.

https://chatgpt.com/share/5e3dd58f-c441-4606-9683-9b304f7a8034 will run from the Plugin Dashboard system and serve Shopify as an API.
Research is required to implement the new generation of Shopify plugin which is an Embedded App.

The embedded app is served within the Shopify Admin Dashboard.
The app will provide installation and uninstallation functionality.
The main requirement within the app is to capture Netcomm and or eKomi configuration settings and persist that to a DB.

Affected Resources:

Netcomm and eKomi plugins. Shopify is changing and it will affect our future plugins.
Plugin Dashboard DB schema will be changed and a new table introduced for the plugin config settings.
Plugin Dashboard environment variables will have new variables added to their respective config files: list file changes outside of Plugin. System files.

Timeline:

Process:

1. Requirement Gathering. 

   • Local Dev Setup & Plugin Dashboard Onboarding. PRD-642

   • Shopify Onboarding. PRD-643

2. Planning & Design. 

   • Plugin - Coding - Planning & Unassigned time tracking. PRD-644

3. Implementation.

   • Dev setup

     • Local Dev Setup & Plugin Dashboard Onboarding. PRD-642

   • Shopify setup

     • Shopify Onboarding. PRD-643

   • Plugin development

     • Plugin - Coding - Planning & Unassigned time tracking. PRD-644

     • Plugin - Coding - Installation. PRD-773

     • Plugin - Coding - Uninstallation. PRD-774

     • Plugin - Coding - Configuration - CRUD. PRD-763

     • Plugin - Coding - Refactor & Comment & Document. PRD-764

     • Widget Store Front Display Requirements. PRD-855

     • Widget Store Front Display Functionality. PRD-856

Process Breakdown:

1. Requirement Gathering:

   • Plugin Dashboard Repo - Local Dev Setup & Research. 

     • Develop overview of system.

     • Define system purpose.

   • Shopify Dashboard & Research.

     • Develop overview of Shopify system.

     • Define Shopify requirements.
       

2. Planning & Design:
   The plugin is broken down into components, namely:
   Each in their respective page.

   1. Plugin Dashboard Repo - Local Dev Setup & Research

   2. Shopify Dashboard & Research

   3. DB Schema

   4. Plugin Install - Process

   5. Plugin Uninstall Process

   6. Plugin Configuration - eKomi & Netcomm

   7. Widget Token Configuration

   8. Widget Store Front Display Requirements

   9. Widget Store Front Display Functionality
      
      

Main Process Flow Diagrams: