WD Software and Salesforce Change Log
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
 
ABCDEF
1
DateComponent & VersionSummary/HighlightsDetails
Personnote
2
8/3/20WDAS 5.1.1
**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

**add function to SalesforceSynchController to delete contact or account from WDDB based on the recycle bin in Salesforce (and lock necessary tables during synch)
**add function transferObjectsLinked to PersonOrg to change linked objects to another POID
*improving code readability by adding informative constants
*add to SynchError logging/email whether report is from WDDev
*change customer_detail.blade so deletion not allowed (and prompted to email Meaghan)
constants.php
--replacing 0,1 with constants WD_is_person, WD_is_organization
--SF_RecordTypeId_Organization and SF_RecordTypeId_Household;
PersonOrg.php -- rename and change saveAfterUnsetLinkedItemInfo();
SalesforceSynchController
--add deletedContactsHandleSF
--this requires using QueryAll instead of Query to access deleted records
--deal with complexity introduced by the way SF handles deletion .. if an account is deleted then SF also deletes contact but does not show it in recycle bin..
--incorporate error catching in multiple places in code

3
7/14/20WDAS 5.1.0
**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
4
7/13/20TIM 5.1.1
**fix problem that TIM is not sensing connection state
5
7/12/20TIM 5.1.0
**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
6
6/26/20WDAS 5.0.9
**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)
**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)
fixing impersonation problems and improving
more flexible creation of $synchLogger
.
7
6/21/20WDAS 5.0.8
improve Salesforce synchronization especially error detection/handling
8
6/1/20WDAS 5.0.7
initiate synchronization of WDDB person_orgs to Salesforce
9
5/12/20TIM v5.0.6
release of 4 month overhaul to Version 5 of database and sottware
10
5/12/20WDAS v5.0.6
release of 4 month overhaul to Version 5 of database and sottware
11
5.8.20wd-dev TIM and WDAS v5.0.3first release of v5 for testing in wd-dev
12
12/2/19WDAS v4.3.31
**better handling of inserts with word 'cut' in comments
*order tab: changing grid height from 600 to 550 (instead of 400 back in March)
*small improvements in utilities: handling inserts with questions: button moved to a row for Cliff, insertnum add to make Steve's SQL manipulation easier

**technical- fixing bug in orderController trap for comments that include "cut"'
**better handling of inserts with word 'cut' in comments
-- in email re inserts with question; add text to further distinguish those triggered by word 'cut' in comment
--include such inserts in the table of inserts with questions
*order tab: changing grid height from 600 to 550 (instead of 400 back in March)
small improvements in utilities: handling inserts with questions: button moved to a row for Cliff, insertnum add to make Steve's SQL manipulation easier


13
11/19/19WDAS v4.3.30
correction posting sheet calculation of DinVS and DinHS
correction posting sheet calculation of DinVS and DinHS
technical: Changing log categories to include "notice" for things that need review
14
11/13/19TIM 4.5.1fix bug with preventing redo orders
15
11/7/19WDAS v4.3.29"customer records with special rate and taxgroup standard will be corrected tax exempt upon create/update
order records with special rate and taxgroup standard will be corrected tax exempt upon create/update
add to utility tab a data integrity check for tax exempt state of special orders and of customers with special rate
change labelling in WDAS to beginning converting ""customer"" concept to ""customer and contacts""
"
16
11/2/19WDAS v4.3.28Customer tab: improve directions on selecting customer to enable open, delete etc



technical: improving customerController to abort function calls if user validation fails
technical: continuing with user enum (and experimenting with removal of wd-admin (and git) from Windows User folder


17
11/1/19WDAS v4.3.27
*improving utilities tab to make function more self-explanatory
*utilities: add data integrity check for orders with no measurers
18
10/31/19WDAS v4.3.26
*Improving subject lines of email-with-invoice and email-with-question to include ordernum and customer name
*fix measurer viewing more orders than allowed
technical: refactoring and minor improvements of code for emails-with-question
technical: setting up impersonation in ordersController (TIM AND WDAS) for Steve to test problems with individual accounts

19
10/30/19WDAS v4.3.25
*new order list with customer info available for a cut file (that can be exported to a spreadsheet)
*adding new trigger of email to WD QC (Cliff): word "cut" in comment
*adding new button in utility to generate an order list with customer info for a cut file (that can be exported)
*adding new trigger of email to WD QC (Cliff): word "cut" in comment
*technical: refactoring some BuildJob functions
20
10/28/19TIM 4.5.0
**definitive fix of bug: price_before_taxes zero: by fixing handling of failed order save (or server-side merge) by reverting price properties to those before save
**fix payments for order: eliminate rounding errors; refactor code for delete payments (possibly fixing bug in the process of doing so)
**window addition/editing: allow mated sets of unequal size
**TIM user can now choose to get email with invoice attached (after saving an order online)
**Errors in TIM are now reported back to the server to help in debugging
**TIM now shows more improved formatting of institution names (on customers marked as institution)

*order form, ""question"" field; before adding question, confirm with user it needs an answer
*customer form: fix showing customer submission requirements
*eliminate LI3PPAY - eliminate option in html template of choosing LI3PPAY
*improve error messaging for customer create/update on server
*report error to user if order record creation fails
*provide more informative error message to user if mated set offset too large
"
technical: refactor cleanupOrderBeforeSave
technical: improve handling of failed order save by reverting price properties to those before save
technical:ask about emailing invoice only if order has measured windows
technical: fixing the problem with ordernum 0 if merge caught server-side
technical: fixing label vertical strut rather than horizontal

"**definitive fix of bug: price_before_taxes zero: by fixing handling of failed order save by reverting price properties to those before save
fix payments for order: eliminate rounding errors; refactor code for delete payments (possibly fixing bug in the process of doing so)
**technical: no longer need to delete order (and insert) properties that are unique to TIM
technical: fixing the problem with ordernum 0 if merge caught server-side
technical: fixing label vertical strut rather than horiztonal
technical: refactor cleanup OrderBeforeSave
technical: improve handling of failed order save by reverting price properties to those before save
technical: for clarity rename valToTwoDec to strToTwoDec
technical:ask about emailing invoice only if order has measured windows

"
"**window addition/editing: allow mated sets of unequal size
**option for TIM user to choose to get email with invoice attached (for both create and update)
**add to order form an error report that gets returned to server
*extending implementation of customer.is_institution: now names in order form and order detail show institution names correctly
*order form, ""question"" field; before adding question, confirm with user it needs an answer
*customer form: fix showing customer submission requirements
*eliminate LI3PPAY - eliminate option in html template of choosing LI3PPAY
*improve error messaging for customer create/update on server
*report error to user if order record creation fails
*provide more informative error message to user if mated set offset too large
**fix of bug: price_before_taxes zero:
--cleanup the get and set functions
--further cleanup and simplification
--improving strategy by moving to order-utils to separate error check from repricing
-- cleanup of prototype and renaming properties with or _proto of getter/setter//accessor
-- reporting in error report, debugging and improving alerts

technical: extend cleanup related to not needing to delete wdOrderParent now that it is non-enumerable
technical: wdwindow.controller cleanup unneccessary code in cancelAddEdit
technical: make wdWindow.wdOrderParent non-enumerable to fix bug and improving code for duplcation via JSON stringify
technical: making sure order status updates to ""measured"" when order with windows is saved
technical: improving code for order status by implementing enumation in __env and cleaning up Sean mess on status
technical: cleanup wd-form-funcs.factory and add method getTypeOfProperty(object, property)
technical: almost entirely changing indent: spaces to tabs then tab size 2
technical: two small changes related to strut offset, but Steve can quickly find those changes
technical: error checks and attempted bypass for error 9-T145 duplicate inserts with loss
technical: removing changes proved unncessary by solving bug 9-T145
technical: draft of improvements for specifying mset offsets: needs further testing

technical: annotations
technical: improving roomName handling with array.map;
technical: fixing problem with insert.id before server upload (were mostly -1, not decrementing)



"
delaying general distribution utnil perhaps 10/30
22
10/28/19WDAS 4.3.24
**debug and make major improvements in emails for inserts with questions and when chosen by measurer (including invoice and contact information)
**Extensive code cleanup and tab layout improvement
improve email to WD insert support person (Cliff) by including contact people and emails
technical Refactor email list for use by any email
improve email acompanying invoice
: add measurer name/emails and customer name/emailstechnical
: add emailAndName function to user and customertechnical: add measurerIdArray to OrderMeasurer to easily access the measurers ids
technical: debug and simplify massive EmptyOrderForCustomer from former developer and related superfluous code
technical: checking if invoice file exists and handle requested emails accordingly
technical: cleanup debugging loggingtechnical: sendEmailForInsertQuestions: refactor into function and call AFTER creating invoice
technical: emailing invoice refactored to simplify code
WDASServerVersion # should have been updated with previous commit**log error report returned from TIM order form
**handle emailing of invoice to measurer, if requestedtechnical: orderController: make ordernum global
25
10/18/19WDAS 4.3.23
improve email alerting about question on inserts by attaching an invoice
technical: implement constant WDisDevServer which indicates whether app is running on dev server and simplify by using it in several places
improve email alerting about question on inserts by attaching an invoice
26
10/11/19WDAS 4.3.22technical: adding 'rate' to order information in email for error price zero
27
10/4/19WDAS 4.3.21invoice: change wording of request to customer: order number not customer number
utilities: add routine to check for duplicate emails for users.
invoice: change wording of request to customer: order number not customer number
utilities: add routine to check for duplicate emails for users.
technical: clarifying error log that creation of user with duplicate email blocked
28
10/1/19WDAS 4.3.20technical: fixing routine that emails Cliff when error detected (only once per order)
technical: changing button size (from xs to sm) on order grid so easier to click
29
9/29/19WDAS 4.3.19improvements to handle/debug problem with orders without calculated price
admin: adding button on utilities tab for orders price zero
technical:adding logic to orderController in check for ErrorZeroPreTax to distinguish whether price before tax is set

30
9/24/19WDAS 4.3.18order controller: convert li3ppay orders to special (until TIM fixed)
send email for order having inserts with question(s) - to Cliff and Steve"
technical: fixing utilities (moving alert from controller to .js)
technical: order controller: convert li3ppay orders to special (until TIM fixed)
send email for order having inserts with question(s) - to Cliff and Steve
31
9/23/19WDAS 4.3.17error trap for debuggingtechnical: adding error trap for orders save with price before tax =0;
32
9/23/19WDAS 4.3.16add function in utilities to list inserts with questions.add function in utilities to list inserts with questions.
33
9/21/19WDAS 4.3.14simplification and improvement of customer name related to is_institution: single SQL text for "select" used by multiple processes; single function for shortname used both in buildJob and posting sheetssimplification and improvement of customer name related to is_institution: single SQL text for "select" used by multiple processes; single function for shortname used both in buildJob and posting sheets
34
9/19/19WDAS 4.3.13posting sheet generation: full version implemented in WDAS (rather than procedure), handles 2019 data changes (struts and mated pairs), now downloadable as text for formating by word macro
posting sheet generation: full version implemented in WDAS (rather than procedure), handles 2019 data changes (struts and mated pairs), now downloadable as text for formating by word macro
technical: workshop status report: clear previous data from day if run again
35
9/17/19WDAS 4.3.12technical: release with fixed utilities file so Meaghan can run WSRtechnical: release with fixed utilities file so Meaghan can run WSR
in progress: improving posting sheets: query integration into WDAS
36
9/17/19WDAS 4.3.11fixing problem with assigning two measurers in grid (that arose from past code cleanup)
upgrade to agGrid 21.2.0;
modification of many (but not all) WDAS components so that customer can be designated as an institution and in that case the organization name is used as the primary name. [Updates need to be made in the reimainder of places including TIM)
Customer tab in WDAS: many changes: action buttons on top of grid that operate on selected customer; ability to create orders (for admins); must faster load (but links to order,inquiries,payments temporarily removed)
fixing problem with assigning two measurers in grid (that arose from past code cleanup)
upgrade to agGrid 21.2.0;
modification of many (but not all) WDAS components so that customer can be designated as an institution and in that case the organization name is used as the primary name. [Updates need to be made in the reimainder of places including TIM)
Customer tab in WDAS: many changes: action buttons on top of grid that operate on selected customer; ability to create orders (for admins); must faster load (but links to order,inquiries,payments temporarily removed)
techincal: beginning of conversion to posting sheet implementation in WDAS
37
9/16/19php version on serverphp (a basic piece of server infrastructure) was upgraded from 7.0.33 to 7.1.32
38
9/8/19WDAS 4.3.10installing FORREST for Salesforce access from WDAS
39
9/7/19WDAS 4.3.9technical: correcting STATE assigning during customer creation from inquiry (was only "ME")

technical: correcting STATE assigning during customer creation from inquiry (was only "ME")

40
9/7/19Web Siteimprovements in Order Insert Formbetter prompts for second contact and business name
workaround for shadow checkboxes in options field
41
9/4/19WDAS 4.3.8
solving assures that cutjob files downloaded are "fresh" not cached
technical: disabling caching of xlsx and csv to solve cutjob refresh problem
technical: first testing of customer access from Salesforce in UtilitiesController
42
9/2/19WDAS 4.3.7
orders grid: add total for "pretax" in summary row;
cutjob generation: fix numbering of inserts in order (to exclude inactive) and calculate strut materials
orders grid: add total for "pretax" in summary row;
cutjob generation: fix numbering of inserts in order (to exclude inactive) and calculate strut materials
technical: delete xBuildJobOrder.php since no longer used
technical: deprecating inserts: num_struts and strut_offsets_str from Laravael
technical cutjob: fix numbering bug by excluding inactive inserts from count
technical cutjob: fix bug that strut number lengths not calculated
technical: adding error message if no candidate customers retrieved for TIM (since available space error does not trigger error message)
43
8/19/19WDAS 4.3.6fix error in ordercontroller with logging on update
44
8/18/19WDAS 4.3.4 and WDAS 4.3.5releasing and then removing code to create customers from users lacking them
45
WDAS 4.3.3fixing small issues in cutjob labels
46
8/7/19WDAS 4.3.2technical: fixing customer name error in cutjobs
technical: eliminating debugging messages
47
8/6/19WDAS 4.3.1
fix TIM error with duplicate inserts (which overwrites a valid one) 9-T145
1) The data retrieval to populate the order grid is MUCH changed under the hood. It is faster for typical use, because it only retrieves orders from the selected year (unless it is overridden by user request for “all”).
2) on returning to the order page, you get the same column layout (but now the filters and sorting is not remembered)
3) The functionality of the cutjob process is now functional for 2019 (but needs checking and lacks some improvements I would have liked to make).
fix TIM error with duplicate inserts (which overwrites a valid one) 9-T145
orders tabs now faster load, since it loads a single year (unless 'ALL' option chosen from dropdown)
inactived sort and filter restoration from current view
technical: cleanup testing and debugging for above changes
technical: completing deprecation of buidjob_num from orders
technical: *more cleanup of cutjobs: adding bjname to form and controller, adding is_completed, date, comment to database, cleanup of controller logic
technical: overall minor annotation and cleanup
technical: orders.js minor annotation of grid features, removing old attempt fix to invoice caching
technical: to accelerate, trying limiting wdm order index for current season
technical: refactoring "index" retrievals of orders for wdm and wda before introducing improvement
technical: completion of server side filter by season (so changing season requires requery);
technical: orders tab: improving timing logging to console
technical: doWindowsHaveDups($windows) - to detect problem order of type seen by Randy Schaeffer
technical: converting globally to UsedServiceNumController
technical: adding flexibility to queries in utilities tab; including new for DupWindowNames
technical: converting much of wdaRetrieveNewRows to sql rather than iterations customers, bill_to, insert count)
technical: *technical: converting much of wdaRetrieveNewRows to sql rather than iterations customers, bill_to, insert count)
technical: code simplification by delegating construction of refreshed $order from wdaUpdate to wdaRetrieveOrders
technical: improve wdaRetrieveOrders by using primarily sql (for all but payments)
technical: cleanup BuildJob: swap strut drill location onto correct stick; fix the addition of JobID to the check for duplicate cuts of an order











48
7/11/19WDAS masterTemp 83cc4bd234c00c0d407b43683067f49d24e8020c*fix error with duplicate inserts (which overwrites a valid one) 9-T145
49
7/11/19WDAS masterTempadding flexibility to queries in utilities tab; including new for DupWindowNames
50
7/10/19WDAS masterTemptechnical: temporary patch of orderConttroller to catch orders with duplicate window numbers
51
7/2/19WDAS v4.2.25technical: Remove references to BuildJobOrder to fix problem created with release 4.2.24
52
7/2/19WDAS v4.2.24*orders tab: further improvements in summary row (orders measured. rate, order number list in invoice column)
*orders grid tooltip: use tooltip to show value of cells (all columns except the buttons, in which it is overriden);
*implementing part of solution so PDF invoice files won't be cached
*technical: still deep in process of adapting cutjobs (incuding first draft of formatting for 2019 cut labels)


orders tab: add to summary row: orders measured and rate (including # and %, suggested by Cliff)
orders tab: adding tooltip on rate, build_code, measurers (to see long lines and to fill in missing builds)
orders grid tooltip: use tooltip to show value of cells (all columns except the buttons, in which it is overriden);
technical: improving default colDef with menuTabs: ['filterMenuTab'],
technical: deleting BuildJobOrder class and instead use direct link to Build_job_id in orders
technical: first draft of formatting for 2019 cut labels
*technical: improving logic of Workshop Status Report count of previous week inquiries
*technical: adding logic to .htaccess so PDF files won't be cached (will see when apache config is updated)
*technical: still deep in process of adapting cutjobs

53
6/21/19WDAS v4.2.23changing grid theme to ag-theme-blue to get more prominent alternating row discrimination;
bug tix technical: fixing bug introduced with 4/2/20 that LCs with multiple workshops see only orders from one; it involved fix in getLCOidArray by reverting QueryBuilder and simplifying;
technical: customer view -- setting default view if missing -- quick patch that will likely need improvement
changing grid theme to ag-theme-blue to get more prominent alternating row discrimination;
bug tix technical: fixing bug introduced with 4/2/20 that LCs with multiple workshops see only orders from one; it involved fix in getLCOidArray by reverting QueryBuilder and simplifying;
technical: customer view -- setting default view if missing -- quick patch that will likely need improvement
54
6/20/19WDAS v4.2.20technical: counting INSERTS not windows in retrieval of orders for grid and in function in orders.phptechnical: counting INSERTS not windows in retrieval of orders for grid and in function in orders.php
55
6/20/19WDAS v4.2.19order grid: adding summary for donation and senior
technical: rounding totals to two decimal places

order grid: adding summary for donation and senior
technical: rounding totals to two decimal places

56
6/20/19WDAS v4.2.18"**orders grid improvements:
--add header row with distinct color for colu,m totals
---show total # orders for total: special, due
---show sum for #pine, #white, #all inserts, $total, $paid
-- show more orders in grid with narrower rows (and accent alternate lines with better background color)
**measurers selection list: change sort to case-insensitive
*TIM order list retrieval: speed up by restricting relrieval to relevant info
**orders grid improvements:
--add top pinned header row with distinct color for colu,m totals
---show total # orders for total: special, due
---show sum for #pine, #white, #all inserts, $total, $paid
-- show more orders in grid with narrower rows (and accent alternate lines with better background color)
**measurers selection list: change sort to case-insensitive
*TIM order list retrieval: speed up by restricting relrieval to relevant info
technical: store cut job # directly in order rather than by linked table
tecchnical: fix permissions limit on LC updating record of users associated with their builds
technical: begin overhaul of cutjob process
57
5/13/19WDAS v4.2.11**add label and help alert to text filter on customers and orders tabs
**add utility for admin, show inserts for order


**add label and help alert to text filter on customers and orders tabs
**add utility for admin, show inserts for order
technical fix error caused by customer name trim, when property is not defined
technical: fixing Sean's old errors in path of script files
technical: initial changes to begin update of cutjobs for 2019 - inserts loops within windows; strut specifications

58
5/7/19WDAS v4.2.5**develop tools to easily develop new complex queries, display results in agGrid and export
**use these new tools in UtilityTab to retrieve results for Weekly Status Report
**develop tools to easily develop new complex queries, display results in agGrid and export
**use these new tools in UtilityTab to retrieve results for Weekly Status Report
*trimming customer names to remove leading and trailing spaces
59
5/2/19TIM 4.4.2*fixing pricing bug
*improving speed and simplicity of customer list retrieval
technical: many behind the scences improvements/simpifications
*highlighting required 'urgent' updates with a red button ("button alert")
*fixing pricing bug
*improving speed and simplicity of customer list retrieval
*highlighting required update with a red button ("button alert")

technical fixing scrolling after choice of rate (so disabled during form load)
technical: reorganzing order page logic/flow by the four types of pageClass
technical: change users to arrMeasurers in orders form
technical: remove $scope for many functions/params where not needed
technical: begin function fetchMeasurers to replace fetchUsers
technical: bypassing update of insert price if not 'editable'
technical: improved error notification: fixing alert syntax ( + instead of ,)
technical: correcting customer selection from name to fullname due to server changes
technical: wdWindow: include setting rate when setting wdOrderParent
technical: fix error of 'editable' moving from wdInsert to wdWindow




60
4/25/19WDAS 4.2.1major overhaul of 'users' tab
-- adding column 'current measurer' to allow exclusion of former measurers from measurers list
--adding column 'comments" for confidential comments by WD staff, seen only by admins
--revealing many fields in users tab for admins, related to users usage of TIM and WDAS, (new this year)
--improve layout of buttons and grid
--improved process for deleting a user: user name shown during confirmation, first step is setting current_measurer = 'N'
**major overhaul of 'users' tab
-- adding column 'current measurer' to allow exclusion of former measurers from measurers list
--adding column 'comments" for confidential comments by WD staff, seen only by admins
--revealing many fields to users tab for admins related to users usage of TIM and WDAS, (new this year)
--improve layout of buttons and grid
--improved process for deleting a user: user name shown during confirmation, first step is setting current_measurer = 'N'
technical: handle retrieval of measurers list for TIM and WDAS with single query (eliminating complex duplicate code)
technical: change 'date_last_login', 'date_last_TIM_login',
technical -- configure eslint for wd-admin
technical: technical: cleanup UserControl - wdaIndex - deleting superfluous and renaming for clarity
technical: fixing security problem: auth not required for user create, update, deactivate
technical: moving functions to "model" customer.php from controller
technical: self-documentation: prefixing server returned variables with "phpecho"
technical: user: turning view states back on; and further refinement of column layout

61
4/15/19TIM 4.3.2*many small improvements in usability of order form**make changes necessary to override authorization when taking over an empty order from another measurer
--allow wdOrder-update to specify bypass_authorization
_specify bypass_authorization when user opts to take over an empty order from another measurer
*add 'get' (in wdWindo)w for priceForDisplay which adds '($0 from customer)' for special and Li3ppay
*reformat Window Overview table so window names usually don't need to wrap and comments have more space
*on order form move 'resident senior' up 'customer info'
*on order form disable "add new window" until rate is set
*change wording to "complete the Add/Edit.."
*on order form when storing offline, when possible duplicate found give user details to inform good choice
62
4/15/19TIM 4.3.0**provide informative prompts to lead user through customer selection for order;
*When modifying a window, the field 'finish' has moved to immediately following room
** adding advanced mode for admins; its first feature is being able to edit single order by ordernum;
*improve error message on failed order update;
*speeding up fill of customer selector field on Orders form
**set focus on customer-selector to reveal names automatically
*order form: reorganizing "manual name" just below ordernum (and outside customer information from database)
**fix bug with assigning customer to offline order
**in new window fieldset, move 'finish' to immediately follow room
** adding advanced mode for admins; its first feature is being able to edit single order by ordernum;
*improve error message on failed order update;
*speeding up fill of customer selector field on Orders form
**provide informative prompts to lead user through customer selection for order;
**set focus on customer-selector to reveal names automatically
*order form: reorganizing "manual name" just below ordernum (and outside customer information from database)

technical: adding 'div' to later use to conceal most of order form under merge options selected
technical: cleanup code logic of merge vs new order
technical: add customer info help as target for focus and scroll after customer selection
technical: handle alerts in wdWindowController with wdSweetalert2 queue
technical: creating wdSweetalert2 service to handle queue for multiple alerts
technical: provide developer with tools based on user.id
technical: fix order lookup urls related to adding option of ordernum
63
4/15/19WDAS 4.1.1*OrderController: - add property bypass_authorization to update query and respond to it in wdmConstruct
64
4/14/19WDAS 4.1.0**improving preset views for orders and customer by
- adding help button
- limiting impact to column formatting, not to filters, text etc
- changing layout to row not column to save space
**speeding up fill of customer selector field on Orders form
**upgrade ag-grid from v15.0 to v20.2 : "community" and enterprise
tehnical start gitignore of ag-grid folders in resources/assets






**upgrade ag-grid from v15.0 to v20.2 : "community" and enterprise
technical start gitignore of ag-grid folders in resources/assets
technical: renaming vestigial files related to agGrid from Sean
*modify agGrid configuration in order.js amd orders.blade.php necesssary after update to v20.2
technical: remove vestigial ag-Grid scripts in public/js
**add WDAS log to server log and update to users record
**add error trap in invoice controller for missing customer or order
*fix error in orderController introduced with adding ordernum option
**speeding up fill of customer selector field on Orders form
*OrderController: add error trap if no such order
**recreate logic for wdmEmptyOrdersList based largely on raw SQL to fix bug found but not pinned down in Sean's logic
**adding Help for Preset views (on customer and order tabs)
**reorganizing buttons above grid to improve function organization (filter-related on left, others on right) on both orders and customers
**Limit preset views to column formatting, not to filters, text etc
*increasing heights of customer and orders grid (from 400 to 600 px)
**consistently use "default season" (now 2019) in WDAS
**change display format of preset views (in ORDERS and CUSTOMERS) to save many rows at top of form
technical: correct loop in function index in customer controller: move view retrieval outside the customer loop
technical: move JS variables from autoload.php to wda-global-js-constants



65
4/4/19WDAS 4.0.18**Enable server to retrieve orders by ordernum (rather than only ID)
*Technical:Improved error handling for undefined objects

66
3/29/19TIM 4.2.3** MAJOR: fixing a bug that payments are retained from one customer to another;
**adding price to the form for adding/editing windows (once windows measurements are complete. So you see price impact of any change you make.
**bug fix: Big_plastic was not being set in windows (although it was being correctly priced). This version adds "big plastic" designation to the form for adding/editing windows as well as properly recording it in the record for the window itself.
**:much improved logic for forcing price change when approved by user, and blocking many edits if not repriced (e.g. blocking edits of inserts or price changes thereof. Also assuring that users are not bothered about repricing of empty orders
**major revisions of logic for repricing leading to much more reliable and efficient code.
** MAJOR: fixing a bug that payments are retained from one customer to another;
**MAJOR: much improved logic for forcing price change when approved by user, and blocking many edits if not repriced (e.g. blocking edits of inserts or price changes thereof. Also assuring that users are not bothered about repricing of empty orders
**fix error causing failure of repricing
*improve download help message to make it platform specific
*improved wording for MAC installing -- referring folks to Ray Yardy

**adding price to the form for adding/editing windows (once windows measurements are complete. So you see price impact of any change you make.
**bug fix: Big_plastic was not being set in windows (although it was being correctly priced). This version adds "big plastic" designation to the form for adding/editing windows as well as properly recording it in the record for the window itself.
**implementing "getter" strategy for price for both order and window objects. This involves renaming properties (with "_" prefix on load and reversing on save. It also involves major revisions of logic for repricing. But it leads to much more reliable and efficient code.
67
3/26/19WDAS 4.0.15**when user logs into TIM, update information in their user record about software usage
**when user logs into TIM, update information in their user record about software usage
*by analogy to other controllers that bomb if user not authenticat, use same logic in BuildJobController, Inquiry Controller and UtilitiesController
*expand the 'users' table with information about their use of sofware and email
68
3/25/19WDAS 4.0.14technical cleanup of codeconsidered Adding build_Test to all users, but then did not for fear it would cause confusiino
JSS begins to use and enhance functions provided by 'user' object
remove unused function in 'user' object
remove unused function and route for orders-no-edit
69
3/25/19TIM 4.1.1**TIM makes the quality control proves more reliable by indicating that QC has not been done on an insert after it has been edited
**before submission of an order by an LC, TIM checks that the LC will have credentials to see the saved order
**TIM now prevents rare occasions when user's credentials were not reset upon startup (previously seen as not having to login)
**TIM now provides more complete information to the server so that it can save information on the server regarding who logged in, what platform this use, and what version of the software there were using
improving information sent with login query: revising names and adding app_name
**add optionsAccessLevel enumeration to .env
**add choice of shaw accounts in .env for debugging
**try allowing enter key in sweetalert2 confirm
**set qc_done = -1 when insert is editted
**add function blnQCOkForSubmission which checks before submission whetherf LC will be unable to subsequently edit this order
**revise main.js evGetRunningVersion to return runnng version (which can be run early)
**add __env.wdConsumeVariable = function(varPassed){ --hack to deal with eslint detection of unused variables
**prevent holdover of user authorization upon startup, by adding window.removeItem('wd-auth-cookie') immediately after startup'
**prevent stop and start of connstat when moving between pages
**with user authorization add OSplatform and Running version so they can be logged on the server

70
3/25/19WDAS 4.0.13**adding logging of user "logins" to TIM along with information on platform, appname and versioncorrecting the JSS prior $e->getErrorMessage to getMessage()
add table "logins" to database and in it keep record of user logins to TIM
renaming ACCESS_LEVEL constants
add error messages to save_current_user_view in customers and orders

71
3/24/19WDAS 4.0.12**increasing expiration time of password reset link from 1 hour to 24 hours
72
3/23/19WDAS 4.0.10**fixing crash when user attempts to reset password. The "noreply" account was switched to noreply@windowdressers.org, which re-established credentials for SMTP mailingannotating and tidying up text of public function index() after implmenting the array merge fix
improving logging when adding new user
updating email address that sends out mail from WDAS (noreply@windowdressers.org) -- must also change .env file

73
3/23/19WDAS 4.0.9**fix error in orders retrieved in list for LCs, that ALL orders are filtered to exclude "deleted" onescomplexity of order retrieval for LCs who see both their builds, and orders on which they are measurers. The laravel code seems to have a bug in "unions" (attempted with .orWhereIn())
74
3/22/19WDAS 4.0.5**write to log the logins of TIM users
**write error traps for several errors being logged to Laravel server logs
logging TIM logins to Laravel file
trap for apparenty undefined user in jwt
orderController public function index()
orderController public function saveCurrentUserView()
undefined user Middleware WDGenAddJwt


75
3/20/19TIM 4.1.0**Improved the facilitated download of new software versions (a) fixed failure on MAC b) distinguished urgent vs routine; 3) provided help button
**Improved strut centering prompts and help
**Narrowed restriction on window names to -A,-B
**Improved warning message about order from prior season
changing terminology about updates to "urgent" vs "routine"
adding help button for the download new version software
improved warning message about order from prior season
adding help button on centering struts
clarifying warning on strut centering
narrowing restriction on window names to -A,-B
making sure rate_season is set to 2019 on new orders
changing strategy for MAC download -- simply putting the file path info clipboard
ix failure of wifi connection slider to update based on responses to connstat queries
76
3/19/19TIM 4.0.2**Overhauled the wifi connection and reconnection logic to make clearer and eliminate bugs.
**Start overhaul of new version download on MAC.
overhaul of connstat so it does not repeat
small reorganization of env to be more logical
planning window.__env.ApplicationName = 'WD Measurer' or 'WD Measurer DEV' to show as title of application shown by index page
overhaul "download" button on home page - show different for MAC and PC -- distinguish required and optional
for download on MAC open window to directory with files
cleanup main.js with eslint
add alert information to all 'err' in server responses
simplifying "runningVersion" from two variables to one

77
3/16/19TIM 4.0.1**Prevent old versions of TIM corrrupting some records by Incorporating features that distinguishes (for the server) 2019 versions from 2018 versionsdealing with problem that old version of TIM can still do some updating
so I embedding appVer into new version queries to server (and will check on server)
78
3/16/19TIM 4.0.0The 2019 version will look and feel quite familiar (even though a huge amount of cleanup and code improvement has occurred behind the scenes).

There are also many usability improvements, including especially:
Wi-Fi connection can be suppressed or enabled.
Dialog boxes for choosing options are more easily understandable.
The order split functionality has been made more user-friendly
More help text is provided for elements on the forms
Users are notified within TIM of new software version availability.
Software version upgrade is much easier on PC’s

The principal functional changes are in specifying window details.
Struts can be centered by the software and their centering is checked.
‘Mated pairs’ has been changed to ‘mated sets’ of up to 5 inserts. They are no longer listed by insert (in the overview) but as a single window (comprised of multiple inserts).
There is an optional “advanced mode” which gives experienced users more options (but is made optional to provide a simpler form for less experienced users).

Additional quality control features have been added
Editing is prevented on orders already cut, or from a previous season
There are many more error checks on the window data entered.
The rate at which the order is priced now has an associated “season” which is checked and update suggested when appropriate.
Window names ending in –A, -B etc are disallowed to prevent confusion with mated sets


PLANS FOR OTHER CHANGES IN 2019
Efforts so far have been almost entirely on TIM, but WDAS will need many small improvements and bug fixes.
TIM handling of customer adding/editing is clunky and hopefully will be improved in a subsequent version. Also, the intent is to add ability for mated sets of unequal insert size, and of specifying crossed struts.

79
80
11/14/18WDASimplement strategy for global js constants in WDAS; update agGrid license key8-W118 implement strategy for global js (not PHP) constants WDAS
update agGrid license key
Stevee270ddc; b244a88
81
11/7/18Toolsimprove mated set calculator on Google driveI have uploaded to Google Drive the version that includes for non-equal mated pairs and called it “_Mated Set insert Calculation ver2”. I have also protected the sheets so that only the cells that you need to use to enter the parameters are available to editing. I have also disabled editing by users other than Cliff BabkirkSteve
82
11/7/18Reportsinclude li3ppay in Weekly report8-D111 fix failure to include li3ppay in insert count in weekly report;Steve
83
10/30/18WDASfix problem of outdated invoices due to browser caching; begin utilities toolkit on separate tab8-W108 circumvent caching that results in showing outdated invoice
8-W109 Create Utilities tab in WDAS to contain toolkit of functions like export from SQL queries
Stevea2ddbb8
84
10/22/18WDASfixing and improving invoice8-TW096 include "cut" and Question field in inserts lists in TIM and invoice
8-W084 in invoice change customer ID to CSN makes it he customer not the "bill to"
begin using Laravel server-side logging
Steve97a0862
85
10/21/18WDASimproving exports from grid to spreadsheet8-W098 fix export for special ratios
customize the exported file name for each tab (eg orders.csv)
Steve15df356
86
10/20/18WDASadd button for admin on order detail to refresh invoice8-W104 add button for admin order detail to refresh and view invoice
add name and ordernum to title for order detail
add '-DV; to title for WDAS tabs in wd-dev database
Stevee38e80d
87
10/19/18WDASadding columns to "Builds" tableadding columns to builds table, and to corresponding fields to grid and input formSteve98bbc49
88
10/9/18Reportsenhancements of Workshop Status Report to include more info on queriesSteve
89
9/27/18ReportsFixed posting sheets and WSR to exclude soft-deleted insertsSteve
90
8/26/18Google DriveTransition Board of Directors from Team Drive to Google DriveTransition Board of Directors from Team Drive to Google Drive folder; cleaning up folder structure and beginning to assign correct permissionsSteve
91
8/25/18Web SiteCreating Board of Directors web pageCreating Board of Directors web page as a "starting point" for critical links for Board Members ( but containing no private information)Steve
92
8/24/18Reportsupdating process of posting sheet generationupdate of the SQL procedures (run in Phpmyadmin) and word macros used to create the PDF files listing order/inserts for posting by the workshopsSteve
93
7/20/18WDAScut file correction for wider stock and reduction of field adjustment8-W074 modify cut file generation to wider stock, governed by defined constants
8-W075 modify cut file generation to include calculation version
Steve
94
7/10/18Reportsmajor enhancements of Workshop Status Report4 new parameters (senior, surface area ClearMount, County)
1 improved parameter: estimated insert number includes estimate in order
adding two workshops
providing a filter to view workshops alphabetically
Steve
95
6/24/18no change TIM v3.0.9code-signing of TIM for PC installation8-T076 Buy and use code-signing certificate for PC authentication of TIMSteve
96
5/25/18TIM v3.0.9fixes 11 problems, most importantly adding to TIM the fields "senior" and "est_num_inserts", fixing idiosyncratic loss of dates or status; and fixing problems with rates 'special' and "redo"; also improve 9 aspects of usability8-D051T add required "senior" field in TIM and its help note
8-T062 fix idiosyncrasies of loosing measuring date or status under specific conditions of merge of offline orders
8-D032T add "estimated insert num" field in TIM
8-T063 do not enforce requirement for "rate"and "senior" until status="measured"
8-TW034T in the standard insert list, make a bug fix and change width before height
8-T064 setting rate to "special" caused block due "pine" in wrong context
8-T060 setting redo rate does not set price to zero
8-T029 make non-TIM (editable=0) status block insert price update
8-T066 deal with merge conflicts for senior and est_num_inserts
8-T067 assure that offline orders without new fields can still be uploaded
8-T072 fix problem of adding inserts to offline order (updated 12 hours after release)

8-T061 improve logic on TIM ORDERS so box "still needed" shows only when needed and is synch'd to Submit button
8-T042 eliminate "my customer only" (since not used)
8-T043 Add field group "Order Handling" in Order Screen
8-TW049a change "Build" to "Workshop" in TIM
8-TW054T change "volunteer" to "participate" in TIM
8-T065 improve wording for Strut Locations (Horizontal)’ in TIM add measurements
8-T069 for user clarity, change BorderStyle on Field Groups in Order Screen to blue
8-T070 add Developer Message strategy to alert them to runtime events
8-T073 fixing incomplete instructions regarding download and install ((updated 2 hours after release)
Steve
97
5/17/18 6:00 PMWDASadding two fields/columns (senior & est_num_inserts) 8-D051W add "senior" field to order controller and show in order tab in WDAS
8-W058 add "senior" and "est_num_inserts" to Order Data screen for editing; and move "SAVE" button to top
8-W053 during inquiry processing transfer inquiries.num_inserts into orders.est_num_inserts
8-TW054W change "volunteer" to "participate" in WDAS
8-W056 add "tooltips" to orders columns headers
8-W057 rationalize the sequence of order columns in tool picker
8-W059 add strong indication when working in development database
Steve8543efa
98
5/12/18MySQL databaseorders table: add two columns and sort 8 mothballed columns to endchange windowdressers_v3.ORDERS table: add columns 'est_num_inserts' and 'senior'; sort 8 mothballed columns to end; start adding explanatory comments to columnsSteve
99
5/8/18WDAScorrecting hgt/width order; fixing WD address; restrict customer preset views; add change log8-W046 fix bug that preset views of customers can be created all users
8-TW034 in the standard insert list in invoice, change width before height and column title "Plastic"
8-W047 create change log and add link on WDAS "home" and windowdressers.org/software page
8-T038 correct WD address in invoice x2
8-W048 shorten browser tab names to "WD:Orders" etc
8-TW049b change "Build" to "Workhop" in WDAS
Steved7fa5a3 or e7a0387
100
4/17/18TIM 3.0.8fix program in memory after quit and order submission without customer info8-T037 TIM program remained in memory after some modes of quitting, and blocked restart on MAC
8-T040 Customer information was not required for order submission in some contexts
8-T021 Users view of screen (scroll) was misleading in some contexts when starting the order screen
8-T041 Incomplete screen message for warning during order submission when a matching empty record was found
Sean/Nate
101
102
103
Loading...