initial commit, date fixed to isoStr local date

.babelrc

@@ -0,0 +1,12 @@
+{
+    "presets": [
+      [
+        "@babel/preset-env",
+        {
+          "targets": {
+            "ie": "11"
+          }
+        }
+      ]
+    ]
+  }

.gitignore

@@ -0,0 +1,118 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+
+# Diagnostic reports (https://nodejs.org/api/report.html)
+report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+*.lcov
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# Snowpack dependency directory (https://snowpack.dev/)
+web_modules/
+
+# TypeScript cache
+*.tsbuildinfo
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Microbundle cache
+.rpt2_cache/
+.rts2_cache_cjs/
+.rts2_cache_es/
+.rts2_cache_umd/
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+.env.test
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+.parcel-cache
+
+# Next.js build output
+.next
+
+# Nuxt.js build / generate output
+.nuxt
+dist
+
+# Gatsby files
+.cache/
+# Comment in the public line in if your project uses Gatsby and not Next.js
+# https://nextjs.org/blog/next-9-1#public-directory-support
+# public
+
+# vuepress build output
+.vuepress/dist
+
+# Serverless directories
+.serverless/
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+# TernJS port file
+.tern-port
+
+# Stores VSCode versions used for testing VSCode extensions
+.vscode-test
+
+# yarn v2
+
+.yarn/cache
+.yarn/unplugged
+.yarn/build-state.yml
+.pnp.*
+
+adminPortal/
+dist/

babel.config.js

@@ -0,0 +1,3 @@
+module.exports = {
+    'presets': ['@babel/env']
+  }

package.json

@@ -0,0 +1,27 @@
+{
+  "name": "cnarcher-workorders",
+  "version": "1.0.0",
+  "description": "Add's cnArcher Workorder generation to EngageIP through WebComponents",
+  "main": "src/app.js",
+  "scripts": {
+    "build": "npx webpack",
+    "web": "npx webpack-dev-server"
+  },
+  "private": true,
+  "author": "Chris Chance",
+  "license": "ISC",
+  "dependencies": {
+    "qrious": "^4.0.2"
+  },
+  "devDependencies": {
+    "@babel/core": "^7.9.0",
+    "@babel/preset-env": "^7.9.5",
+    "babel-loader": "^8.1.0",
+    "css-loader": "^3.5.1",
+    "file-loader": "^6.0.0",
+    "image-webpack-loader": "^6.0.0",
+    "webpack": "^4.42.1",
+    "webpack-cli": "^3.3.11",
+    "webpack-dev-server": "^3.10.3"
+  }
+}

readme.md

@@ -0,0 +1,22 @@
+This is an internal development project to add cnArcher workorder generation to the Logisense EngageIP Admin Portal.
+
+The primary component of this project is the bundle.js and images that are used for a Custom Web-Component <cn-workorder />, this is a very generic reuseable component, however the sample pageextension is based on our own internal setup, and your various field names and noticeicon values most likely differ and will require tweaking. My recommendation is to examine the sample page extension and adopt it to meet your needs for adding cn-workorder's to your packages in the adminportal.
+
+npm run build - builds output to dist/*, content's should be copied to EngageIP adminportal and accessible as AdminPortal/cnArcher/*
+npm run web - starts dev-server with setup accessible via http://localhost:3000/sample.htm
+
+To deploy: 
+
+- Build with the npm build script.
+- Copy Files as recommended to AdminPortal/cnArcher/ on the adminportal server
+- In the EngageIP admin portal add a new page extension 
+  - Page Setting: Set to overview/index to target customer overview pages only.
+  - Content: Should be set to the static/pageextension.js sample.
+- Test the extension by visiting a customer that has a package with a 0a-00-3e ESN. 
+
+The pageextension-example.js looks through the clients overview page, finds the various package noticeicons that are used for mouse over package data, it then appends a cn-workorder custom element next to that notice icon that is the trigger for the new web-component modal window for generating workorders.
+
+TODO: 
+- Migrate the fixed technicians to a span or some other more modifiable method
+- Possibility to add google calendar creation trigger
+- Possibility to trigger email to technician