myriad of minor changes (see details) including switch to 2023

see Log 2023 wdMeasurer v7.0
MANY changes (and more than 300 hours of development time)
large number of which relate to usability ... many suggested in survey of measurers
Biggest changes relate to overhaul of many aspects of process of offline orders

**added the general strategy of HelpAlerts to wdAdmin (like have been in wdMeasurer)
**adding Alison and Steve M to impersonation
Major improvements in Tax Reports
--added a button" RunAMonthlyTaxReport" on Utilities tab - so director can run reports (not just cio)
—-this required adding a function in UtilitiesController 'runTaxReport' and a web route to it
—-this was also improved by a better query in ReportSalesTax.php createTaxReport so that orders from the last two years are filtered for possible inclusion
--added a button" ReviewOrdersInATaxRun" on Utilities tab
--added helpAlerts for each of the three buttons in 'For TaxReport use'

orders tab and detail - disable change of status for all but administrators
improving utilities tab report of sales tax -- add relevant columns

increased memory limit (so orders from all seasons can be loaded)
disabling of 'set deliveredl in buildevents now fixed

more fixing problem with price_before_tax set to 0

improving handling of potential duplicate customers during salesforce synchronization

certain updates in Salesforce don't get transferred automatically until overnight. I have now improved the utilities tab, so that you have a better explained button to use to force that update from SF to wdAdmin

log ongoing wdDB synchronization with Salesforce

improving buildevents screen and file
--adding an option of assigning orders with status 'cutjob assigned' to buildevent
--changes in the Buildevent file
----renaming xls file from: 'PostingAndMRL' to 'Buildevent'
----renaming tab 'Inserts by Customer and Order' to 'PostingSheets'
----renaming header of summary from 'POSTING SHEETS' to 'BuildEvent SUMMARY'
----adding a line in the summary file for 'Date Summary Created'
----on each posting sheet page for an order with rewraps, adding a line stating the number of rewrap inserts at the end of the list of inserts

improvements in Buildevent handling
store the SF_ORG_ID in the .env file rather than in code
easier impersonation

improved handling of assigning orders to cutjobs and buildevents, especially rewrap only

drop table order_status_codes from learn database
it's not a laravel model and is used in one sql statement that needs to be deprecated

improving integration by allowing buildteam access in sql and simplifying code to models (rather than stdClass) where it is possible

handle num_pine_inserts and num_white_inserts in a more easily usable way;
simplify storage of city tax info more simply in states without local tax;
buildteams now stored in easier-to-use way;
streamline table usage by learn database

improving integration by allowing buildteam access in sql and simplifying code to models (rather than stdClass) where it is possible

wdAdmin web app

changing wdShared to 6e31c84 bcause of fs problem

wdAdmin has bug with wdShared which needs rollback

improved method of storage of buildteams to avoid its occasional disappearance

Log 22-T215 convert wdMeasurer from localtorage to node.js file system storage

fixes of several issues of tax_state
adding submission requiments of buildteam even when offline
fixes of other issues during merge where offline should dominate

changes in CURL and SalesforceController in order to debug the Salesforce problem
Heading comment field to the payment tab in WDAdmin

fixing updateOrderFromRequestAndSave so only orders transitioning to status 3 are recorded

**order.php -- added functionality that saves copy of order before and after its transition to 'measured"
Order-detail -- delete button alert tells user how to delete
user.php getNameAndContactInfo assembles name and email in format to faciltate copy to email

Adding a server-side function to check when any order is saved to determine if its tax_state is OK. Any problems found are logged.
Quite a few small changes, most significant of which is adding callbacks WDOrder functions saveOrder() and FetchOrderDetail()

-fix bug in setting database caused because cookie not valid until first send by browser

direct link on windowdressers software page for downloading either MAC or PC wdMeasurer
Much faster download of software updates
White finish now allowed
User prompted to confirm they have checked laser
Buildteams available offline and must be assigned (to calculate tax)
Better tabular formatting of both lists of orders (all orders, and empty orders)
Many deep changes to improve software (e.g. removal of duplicate identifier of orders; multiple authentication improvements; upgrade to electron v16)

suppress logout messages for users other than CIO

fixing bug in payment update (introduced in 6.3.7.9)

wdAdmin', 6.3.7.10workaround for fact that order->id is not available until after order is saved -- so use the expected id with auto-increment

getting rid of the unnecessary complexity of duplicate unique identifiers 'id' and 'ordernum' in the orders table (remaining identifier 'id' has value previously in 'ordernum')
This involves complex changes in more than 26 files, and a complex set of SQL statements for the database migration; but those changes have been extensively checked
change was made in a mnner that does not require simultaneous upgrade for wdMeasurer;

removing 'build_code" as record identifier so it can now be saeful updated in salesforce;
improving management of orders.status codes in software code (and changing status code 1 from 'not contacted' to 'assigned'

fixing sort and filter of buildteam
workaround for redirect when wdMeasurer retains validation

This release includes MANY updates of underlying components. For example it has a new version of the Grid (AgGrid). So functionality like mouseover (discussed by Laura and I regarding summary row) may be better or worse.
Cliff (thanks!) and I have tested functionality, but there is always a possibility for undetected problems. Although wdMeasurer was not updated, wdMeasurer depends on wdAdmin, so it could have changes. (I, of course, worked to assure compatibility and have not found any problems).
The only functional change in WD code is that the identity of the user who creates an order, customer or payment is now stored. It’s not yet visible in the front end, but that’s coming.

composer install - many updates including Laravel 8.83

cutjobs - relax date constraints, so previous season is included as well as current

Laura's requested changes in summary row and filter by > in 'status'

see wdMeasurer 6.3.7;
also impose consistency on all code for buildteam selection

1) changing default season to 2022 (a minor change)
2) changing to a new 2022 price (5% increased). This was pretty easy because it uses most of the code from previous price changes
3) adding a shop-built rate (50% above residential) (a pretty small change)
4) changing sales tax calculation based on the assigned build team

key technical issue is creation/use of a wdData offline store, which is used initially to store buildteams for offline use;
also move logic of assigning build team into wd-Shared (wdOrder)

implementing "BuildEventSpreadsheet aka Posting sheets for cutfiles -- intended for shop-built
it can be run only after cutjob is marked as complete --
when it is run, it dynamically creates an html button to download the file

improvements in tax_reports - see https://docs.google.com/document/d/13-qvMmdZHucK2yqgIc0wQxI9Ge1eMTxW/edit
--rename column tax_payable to tax_paid -- which is the sum order payments to WD
-

MAJOR improvements in sales tax reports -- fully operational with tests so far
improving data recording - tax_reports -- add 'rate; orders add 'tax_report_state_id', 'tax_report_city_id',
provide tool for correction of tax_state based on buildevent as point of sale
utilities.js improve the columns in the tax_reports listing
ReportSalesTax -- mothly report saves in the order record the id of tax_report in which sales tax is reported both for state and for city; and updates if neceesary if report changes

wdAdmin', '6.2.9.1' -- mostly updates of Buildevent and ReportSalesTax
But comes after accidental chgmod

I am putting more emphasis on upgrading underlying components of WindowDressers software to minimize long-term problems (and possibly solve some ongoing low grade nuisances). Laravel is one of the biggest underlying component of wdAdmin (and therefore of wdMeasurer). I have made 2 successive major upgrades of Laravel (to v8) which means we are finally on the current version (Hallelujah!).

changing from a two step software cycle (wd-dev and wd-admin production) to a three step (wd-dev, wd-rc, and wd-admin) with 'sites' for each
Steps forward in buildevent user interface (and file structure)
better alerts from server problems
cleaning up dependencies (remove Excel, add phpSpreadsheet)
updating js files in public/js

refresh customer list after customer added or edited (to fix bug with new customer not appearing)
reduce risk of problems by exhaustive update of the huge number of sofware components on which wdMeasurer is built (as an approach to fixing very rare problem with software freeze);
simplify the directory organization of components to increase clarity and make maintenance easier

fix login nuisances (e.g. "you are no longer logged in") - especially on the Mac
fixes interrupted internet connections (by allowing up to 3 successive missed "pings" rather than none)
fix failure of auto-detection of new version -- by update electron-builder (and maybe npm)
adding sales tax for NY

adding ability to mysqlCopyProductionToDev from utilities tab via utilities controller running a shell script
Build events
--generating posting sheets, including rewraps and change in order retrieval to catch rewraps only
partial draft of BuildEvents handling user interface
better handling of some Salesforce exceptions

MRL, FileSpec, accept affiliations Active as well as current

cutfile order selection tools
--also released recently (by cherry-pick or direct save) -- email to CIO with exception; authentication workaround based on php cookie; fixing authentication bug

fixing bug that a $arrOidsAllowed with no members allowed seeing ALL orders
wdShared: adding NY tax
continuing improvement in handling caching -- selective prevention of cache of the wd js files only
--creating a public/js subfolder 'wdjs' to store all the wd javascript files that will NOT be cached
--moving relevant js files into that folder (and changing path to them in master.blade)
--specifying no js cache in wdjs folder (but allowing js file cache elsewhere in public)

no cache javascript'
wdShared: seasons fixes
volunteers - improving date validation for volunteers -- max date (tomorrow) for dates and required for volunteer hours start
adding phone # PersonOrg::emailAndName();

adding option of "Canceled' as a pseudo-season to save canceled orders;
This involves a change in database design (storing 'season' as string rather than number) and will not be properly implemented in wdMeasurer until next release

many improvement in inquiry handling; deep change in inquiries table from order_id to ordernum

fix terrible problem that payments not being stored (since March)

adding mirroring for "localStorage" for offline files using nodejs fs module (to deal with 2-3 occurences of offline file loss)

adding navbarMessage,
adding impersonation
fixing bug warning that measurer would not have access

adding navbarMessage,
adding impersonation
include navbarMessage and DB_RootName with fetchSharedData

fix problem wdMeasurer did not go back to home screen for login when the user has lost “authorization” (ie no longer logged in because software was left open too long)

1. Rewrap" of inserts can now be handled.
2. You can now enter window measurements with fractions
3. Your volunteer hours (and miles) and COVID vaccination status can now be recorded.
4. You can learn/practice the software in a ‘learning database’
5. The software incorporates a failsafe option for offline orders.

1. Rewrap" of inserts can now be handled.
2. You can now enter window measurements with fractions
3. Your volunteer hours (and miles) and COVID vaccination status can now be recorded.
4. You can learn/practice the software in a ‘learning database’
5. The software incorporates a failsafe option for offline orders.
**Other lower-profile 2021 improvements
The software incorporates a small price increase from the 2019 rate to the 2021 rate
The software handles state tax appropriately for VT vs ME
The software provides many more ‘tooltip’ help information (marked by ? in blue circle)
The software provides more field validation and clarity on required fields (but further is work needed)
There are more indications what you need to do when an item you want is greyed out
‘Measurers’ dropdowns now are better sorted, show more information (including current used at top, and inactive names) and allow unassigning.
‘Build’ dropdowns now are better sorted, show more information (including inactive builds) and allow unassigning.
Handling of error messages from the server has been systematically overhauled - to provide more information to the user when something goes wrong.
The software assists in better communication with users by alert messages at login.
Many operations in the order form are faster because information is batch-loaded when you log in
The software warns a user if they are about to upload an order which they could not later “see” (because of permissions).
The software informs uses that white inserts are usually not possible in 2021
**Important but ‘invisible’ 2021 improvements
Information on builds and volunteers jobs is now (better) managed in the new WindowDressers Salesforce database
It is now easier for WD staff to keep in touch with customers and contacts using the new WindowDressers Salesforce database (with synchronization so that wdMeasurer/wdAdmin data stays current.)
The software which runs our server (such as Laravel) was updated so it is more secure and less likely to fail when other software changes.
Our software was moved to a "dedicated server" used only by WindowDressers, which improves security and decreases risk posed by human error in server management.
Major simplification of storage of measurer identifiers
We are expanding the recently implemented strategy of sharing javascript code between wdAdmin and wdMeasurer. This reduces complexity, redundancy and development effort.
The permissions (for record viewing/updating) for each kind of volunteer (measurer, LC, admin etc) are based on more specific volunteer jobs ( stored in Salesforce) and better implemented in wdMeasurer/wdAdmin (including account creation).
The ‘alert’ and ‘confirm’ boxes are now consistent in style (and using a software component that is compatible with underlying software)

"add order page" changed to include
a) num_rewraps and price_rewrap
b) information on why "add window" is disabled and
c) marking address fields as required (and forcing state entry as 2 char abbreviation)
d) simplifying view until required address information is added

migration to v6 -- MANY changes;
biggest relates to roles/permissions
-- retrieving user roles from Salesforce (and identifying them by SF ID);
-- strategy for impersonation now much better
-- set up a simple system for admin changing access_level for debugging
--a lot of code related to permision has also been depulicated and improved
second big one is retrieving builds from Salesforce (and identifying them by SF ID)
third critical one is distinguishing sales tax by state
lots of better practice, including a strategy for combined fetching of multiple data arrays, which is shared by wdAdmin and wdMeasurer

migration to v6 -- MANY changes;
biggest relates to roles/permissions
-- retrieving user roles from Salesforce (and identifying them by SF ID);
-- strategy for impersonation now much better
-- set up a simple system for admin changing access_level for debugging
--a lot of code related to permision has also been depulicated and improved
second big one is retrieving builds from Salesforce (and identifying them by SF ID)
third critical one is distinguishing sales tax by state
lots of better practice, including a strategy for combined fetching of multiple data arrays, which is shared by wdAdmin and wdMeasurer

Laravel 6.20
initial tests of volunteer page and connection to SF WD-Vol

SalesforceSynchController - minor fix in catch for errors not caught by SF

increase memory limit for PersonOrg (customer) needed due to table growth

final updates before migration to new server wd-sh
minor issues fixed related to functions called by utilities.js

improvements in synchronization and checking WDAS to SF record match

fixing assignment of order address if it needs to be copied from billing address

**huge (but not fully complete) cleanup of form and logic for processing inquiry

**add function to SalesforceSynchController to delete contact or account from WDDB based on the recycle bin in Salesforce (and lock necessary tables during synch)
**change customer_detail.blade so deletion not allowed (and prompted to email Meaghan)
**add piece of MERGE functionality: transferObjectsLinked to PersonOrg to change linked objects to another POID

**update inquiry table structure, grid, import to handle new inquiry form
**-add trap to reject login on MAC by v5.0.6 going to wrong directory

**fix problem that MAC version 5.0.6 is accessing the v5_dev database
**change logic of setting "is_organization" requires active choice and cannot be changed after set
**improving logic of customer assignment -- deselecting; disabling add when customer selected, etc
**handling choice re potential duplicate customer

**change logic of setting "is_organization" requires active choice and cannot be changed after set
** exclusion from synch PersonOrgs records identified as 'Test' (first name, last name, beginning of org name)
**log a Synch error if a personorg record is made inactive (deactivated, deleted)
**fixing dup customer handling (logic was inverted)

improve Salesforce synchronization especially error detection/handling

initiate synchronization of WDDB person_orgs to Salesforce

release of 4 month overhaul to Version 5 of database and sottware

release of 4 month overhaul to Version 5 of database and sottware