{"id":13325,"date":"2023-10-12T16:06:06","date_gmt":"2023-10-12T20:06:06","guid":{"rendered":"https:\/\/help.strongtietech.com\/pipeline\/?page_id=13325"},"modified":"2023-10-12T16:06:06","modified_gmt":"2023-10-12T20:06:06","slug":"pipeline-2023-3","status":"publish","type":"page","link":"https:\/\/help.strongtietech.com\/pipeline\/release-notes\/pipeline-2023-3\/","title":{"rendered":"Pipeline 2023.3"},"content":{"rendered":"

[vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n

New Features<\/p>\n

[\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n

Trades Scheduling Activity <\/strong><\/h3>\n

[\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]Pipeline Purchasing and Scheduling users can now communicate with the Vendor when a scheduling activity has been assigned to them without a purchase order. \u00a0Previously this was not done at the time of the work associated with the purchase order, but now it is a dedicated scheduling only task.\u00a0 By associating the Trade\/Vendor to the Scheduling activity in Pipeline, it is now possible to pass that Trade\/Vendor over to Scheduling, for the schedule to be updated to include the Trade\/Vendor on any Scheduling only task.[\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n

Improve Product Drop Down Selections for Large Data Sets <\/strong><\/h3>\n

[\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]Pipeline is improved with better UI and functionality when working with large Product data sets.\u00a0 Products, within Pipeline pages, listed as drop-down selections are now searchable, which reduces the number of Products within the list, and is more efficient for the user.\u00a0 This feature is updated within the BOM Logic Rules also.\u00a0 Descriptions are now added to Products to assist in search efficiency.[\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n

Enhancements<\/p>\n

    \n
  • Pipeline users can now see Product descriptions on the House Import page, allowing for better knowledge of what is being imported.\u00a0 Product descriptions are located next to Product name on the import page.\u00a0 PIPE-29840<\/li>\n
  • Pipeline Copy House Quantities functionality is enhanced to maintain parameters when copying to another House or Option.\u00a0 PIPE-29973<\/li>\n
  • Pipeline Scheduling page, within Jobs, is updated for better usability and navigation.\u00a0 Verbiage on card holder is changed to read \u201cScheduling Tasks\u201d.\u00a0 The left side navigation menu is enhanced to position the Scheduling Tasks page to the top of the section, under Documents. The page has a nested table to display schedules with milestones.\u00a0 PIPE-30342<\/li>\n
  • To match the functionality of Pipeline Styles, when importing House quantities, the Building Phase column now has a dropdown to select the desired created Building Phase. \u00a0PIPE-32761<\/li>\n
  • The Options Per Configuration grid, on the Jobs Options page, is revised to fit either items to be displayed or the \u201cNo records to display\u201d label.\u00a0 PIPE-34382<\/li>\n
  • Pipeline is updated so that the Set Tax Group button within Costing will prompt a modal by the same description.\u00a0 This provides consistency and uniformity to the tool.\u00a0 PIPE-34459<\/li>\n
  • The Community Sales Tax screen within Pipeline Costing is enhanced to show a toast message notification when Tax Group Override has been updated.\u00a0 PIPE-34460<\/li>\n
  • Large product datasets within Pipeline now function with increased speed and efficiency.\u00a0 PIPE-35437<\/li>\n
  • A Pipeline user, on the Vendor Assignment page, can now choose to multi-select all the communities in a division using multi-select functionality.\u00a0 This allows for a more comprehensive and efficient Vendor assignment process. PIPE-35831<\/li>\n
  • Within Pipeline Purchasing, only Vendors assigned to a Trade will be displayed in the Vendor drop down list.\u00a0 PIPE-35843<\/li>\n
  • A loading icon has been added to the process of navigating between pages in the Advanced House BOM. PIPE-35851<\/li>\n
  • Synching a Scheduling task from Spec It Up now only adds new data.\u00a0 PIPE-35958<\/li>\n
  • Improvements to the House BOM page include reducing session usage and changing page size. \u00a0PIPE-37328<\/li>\n<\/ul>\n

    Fixes<\/p>\n

      \n
    • The Product import tool was previously returning multiple errors for duplicate data, missing data, and differing data.\u00a0 This is now fixed to result in a successful import. \u00a0PIPE-23183<\/li>\n
    • Pipeline is fixed to display an error message if a user tries to Add Series without populating any required text fields.\u00a0 Additionally, all required fields within Pipeline Series are noted with an asterisk to prompt the user to populate the required field.\u00a0 PIPE-25869<\/li>\n
    • A server error displayed when generating Cost Comparison in Pipeline Purchasing has been addressed and fixed. \u00a0PIPE-27655<\/li>\n
    • Previously a User was able to edit a Building Phase type to the name of an existing Building Phase type.\u00a0 This is resolved to not allow duplicate Building Phase types.\u00a0 PIPE-28462<\/li>\n
    • It was discovered that a Pipeline User could change their username to sysadmin and gain system admin access, including login to other User accounts.\u00a0 This is fixed by validation that the User username is unique.\u00a0 PIPE-28463<\/li>\n
    • When adding or editing Building Groups in Pipeline Estimating, Pipeline is fixed to require that Code is a mandatory field.\u00a0 PIPE-28465<\/li>\n
    • There was found a discrepancy between the Job BOM quantity and Job BOM trace, when the page is set to view by: Option, Phase, Product.\u00a0 This is fixed to display the quantities as the number displayed on the UI.\u00a0 PIPE-28466<\/li>\n
    • Previously, when Job Quantities have a Community Specific Product included that doesn\u2019t have a style the Job BOMs would fail.\u00a0 This is addressed so that Pipeline will successfully generate the Job BOM, but also display a message to state that some Products are missing because of missing Styles. \u00a0PIPE-29207<\/li>\n
    • The Expand All button on the Community Spec Sets page of Pipeline is fixed to properly expand all Spec Sets listed on the page. \u00a0PIPE-29427<\/li>\n
    • House BOM generation is fixed so that an error message will populate if a user tries to create or edit a Spec Set Style where original and new Styles are the same, or where there are missing data values.\u00a0 Previously, the BOM generation would loop indefinitely. \u00a0PIPE-29770<\/li>\n
    • Time displays in Pipeline are set to display within the Users local time zone.\u00a0 This is specifically true on the House Import page, Job BOM page, and House BOM page.\u00a0 PIPE-29820<\/li>\n
    • Pipeline is fixed to display Community Override House Name on the Community Spec Sets page, The Jobs page, and the Estimating Spec Sets page.\u00a0 \u00a0PIPE-29974<\/li>\n
    • Importing Spec Set groups in Pipeline Estimating was giving users an error message if the import file listed duplicate Spec Set groups.\u00a0 This is resolved so that Pipeline will successfully import the file and create an empty Spec Set as a default.\u00a0 PIPE-29976<\/li>\n
    • It was discovered that the House Copy and Advanced Copy function of Pipeline was not populating Sales House Name when copying from existing to new House.\u00a0 It was also noticed that Community Specific House Quantity was missing in newly copied House.\u00a0 These issues are both fixed. \u00a0PIPE-29978<\/li>\n
    • The House BOM export is fixed to no longer display a server error when settings are changed in Advance Mode and saved without refreshing page.\u00a0 Additionally, the Generation Status and Import Date columns are now working properly. \u00a0PIPE-29991<\/li>\n
    • The process of adding and saving House Custom Fields in Pipeline Estimating was found to not function correctly resulting in a displayed error message.\u00a0 This is now fixed.\u00a0 PIPE-29997<\/li>\n
    • The process of removing and saving House Custom Fields in Pipeline Estimating was found to not function correctly resulting in a displayed error message.\u00a0 This is now fixed.\u00a0 PIPE-29998<\/li>\n
    • Previously, a broken page\/server error would display when a user tried to export Advanced House BOM in XML format.\u00a0 This is fixed so the XML files successfully export without error or issue.\u00a0 A loading icon was also added to the Advanced House BOM to show the process of House BOM generation. PIPE-30038<\/li>\n
    • When a User would import house quantities with existing product and existing Style, but new Manufacturer, the product would include all Manufacturers associated with that Style into product details.\u00a0 Pipeline is fixed to only utilize the new Manufacturer-Style selected from the User Import file. PIPE-30059<\/li>\n
    • Within Pipeline Assets, in Houses navigation menu, the Copy House \/ Advanced Copy process is a six step process.\u00a0 Previously, the page would break and cause a server error message at step 3 of 6.\u00a0 This is now resolved to process through all six steps. \u00a0PIPE-30082<\/li>\n
    • After using Bulk Delete Actions, Advanced Update export was hidden when the list of Product export selections was expanded on the Products default page of Pipeline.\u00a0 This is now resolved to display correctly. \u00a0PIPE-32560<\/li>\n
    • Fixes to the House Quantity import allow for importing three times with new Product, New Building Phase, new Style without issues or errors at each import interval. \u00a0PIPE-32765<\/li>\n
    • House BOM Tracing previously experienced issues when View Mode was set to Mini and when Chart Type was set to Detailed.\u00a0 This is fixed so that the site generates BOM Trace data correctly.\u00a0 PIPE-32783<\/li>\n
    • It was discovered that the default Style shown on the House BOM when configuring the Style Conversions with the Style is not accurate.\u00a0 This is fixed so that the Style added on the quantities page will show on the House BOM. PIPE-32784<\/li>\n
    • Pipeline is fixed so that the Total Cost column will update correctly when updating the quantity on One Time Products.\u00a0 PIPE-32779<\/li>\n
    • Within the House BOM, when Spec Sets is configured to convert between different Products and Styles, the Quantities of Use were found to be incorrect.\u00a0 This is fixed.\u00a0 PIPE-32793<\/li>\n
    • When a user would try to click a Community on the Community Phases grid, on the House Details screen, the user received a Server error. \u00a0This is fixed to function correctly.\u00a0 PIPE-32796<\/li>\n
    • A syntax error was occurring in Pipeline when a user would try to select a Product that contains the apostrophe (\u2018) character.\u00a0 This was true on multiple pages where Products are listed.\u00a0 This error is fixed to no longer occur. PIPE-33033<\/li>\n
    • Job orientation on the Job BOM could not previously be set to \u201cright\u201d despite Pipeline settings for Job orientation being updated by the user.\u00a0 This is now resolved to allow Job orientation adjustment within the Job BOM.\u00a0 PIPE-33034<\/li>\n
    • When applying system quantities for a Job, it was discovered that the system uses all Community quantities for the Community listed on the Job.\u00a0 Pipeline is fixed to use Community quantities listed on the Job when applying system quantities rather than pulling all Community quantities into the Job BOM.\u00a0 PIPE-33035<\/li>\n
    • Pipeline login issues are fixed so that; an error message will display if licenses are reached, those that do not use licenses are always allowed access, a single user in multiple browsers is not utilizing multiple licenses.\u00a0 PIPE-33037<\/li>\n
    • Previously the Product drop-down field within House Option Quantities would fail to load Product while \u201cShow Category\u201d setting was enabled. This is fixed to list all related Products.\u00a0 PIPE-33187<\/li>\n
    • Previously the Product drop-down field, within Product Conversion in Spec Sets, would fail to load Product while \u201cShow Category\u201d setting was enabled. This is fixed to open successfully, and filter Products based on Category.\u00a0 PIPE-33188<\/li>\n
    • It was discovered that adding a Building Phase to a Product during House Import deletes the Product description. This is now fixed so that the Product description is not deleted. \u00a0PIPE-33203<\/li>\n
    • Duplicate data in the database was found to cause issues in House BOM generation. This is fixed so that BOM generation is successful. PIPE-33205<\/li>\n
    • In House Imports, it was found that Products would end up in the wrong Option rather than the Option the Product is associated to on the XML file. This is fixed so that Products are shown in the correct Option. \u00a0PIPE-33210<\/li>\n
    • All Improved Product Drop Down Selections, in Pipeline Estimating, are fixed to display the results of description matches. \u00a0PIPE-33212<\/li>\n
    • Pipeline Estimating Community House BOM generation is addressed to ensure that generating large Community House BOMs will not max out memory usage. PIPE-33718<\/li>\n
    • Purchase Orders being created for Sage integration are addressed so that the number 10 no longer displays as \u201c0010\u201d.\u00a0 This was disrupting integration functionality.\u00a0 PIPE-34223<\/li>\n
    • The Approved Config button, on the All Jobs Options page of Pipeline, would previously display a configuration modal despite being disabled.\u00a0 This is fixed so that if there are no configurations to approve the button is disabled in appearance and functionality. PIPE-34274<\/li>\n
    • Previously in Pipeline Costing, Community Sales Tax screen would stay in active edit mode even when selecting other fields\/actions on same page.\u00a0 This is resolved. PIPE-34461<\/li>\n
    • The Trades field in Pipeline Costing is fixed to not auto populate when the Vendor Details page text fields are saved.\u00a0 PIPE-35073<\/li>\n
    • Pipeline would lock up the page when a user would use a large dataset of Products in the All Building Phase selections of the Selective Copy of the Copy Subcomponents modal.\u00a0 This is resolved so that loading a large dataset of Products can be done without issue.\u00a0 PIPE-35112<\/li>\n
    • It was discovered that if the Vendor Code, which is required, in the table does not match the Vendor Code listed in the UI, which is not a required field, then the Vendor Import will not work causing an error message.\u00a0 If both the table and UI have missing Vendor Codes, then the import would act as if there was duplicate data causing error.\u00a0 This has been resolved. \u00a0PIPE-35441<\/li>\n
    • Pipeline Estimating previously did not allow users to create a new Building Phase Type.\u00a0 Upon opening the Add Type modal, an error message would display. This is now resolved so that a Building Phase Type can be successfully created. \u00a0PIPE-35559<\/li>\n
    • Pipeline is updated to generate an estimate for Costing when a user assigns a Vendor to a trade.\u00a0 PIPE-35589<\/li>\n
    • When importing Products using an export file, a Pipeline user would get a time out error.\u00a0 This is fixed to ensure users can successfully import Products.\u00a0 PIPE-35609<\/li>\n
    • Previously, if a Product CSV import file contained invalid data, the error log table would not show the error log.\u00a0 This is fixed with updated source code. \u00a0PIPE-35611<\/li>\n
    • Pipeline Purchasing Cost Comparisons would time out due to a large amount of comparisons causing the query to time out.\u00a0 This is fixed by creating separate stored procedures for each of the cost tiers so that the time for each block of scripts does not compound. \u00a0PIPE-35620<\/li>\n
    • The tooltips in both the Building Phase and Scheduling Tasks modals, on the Purchasing \u2013 Trades page, were partially covered by the overlap of the Building Phase and\/or Scheduling Tasks in Add or Edit mode.\u00a0 This is fixed.\u00a0 PIPE-35723<\/li>\n
    • Within Pipeline Purchasing, when Trades do not have a company vendor set, the field has a default character of double hyphen. This default character setting was fixed to not be set as a clickable hyperlink. \u00a0The same is true for the Building Phases and Scheduling Tasks columns.\u00a0 PIPE-35734<\/li>\n
    • Pipeline Vendor Assignment is fixed so that a Vendor assigned to a Trade at the company level will show up for all Divisions and Communities for that company unless a Vendor has been assigned at a lower level.\u00a0 Vendor hierarchy is: 1. Company 2. Division 3. Community PIPE-35832<\/li>\n
    • Errors and issues were found in Advanced House BOM grid within the Settings column and Parameter value column.\u00a0 These are addressed to ensure that no errors occur when saving Columns settings. PIPE-35924<\/li>\n
    • Pipeline Purchasing Budget was found to show total quantities but no associated line-item cost. This is resolved.\u00a0 PIPE-36174<\/li>\n
    • Error messages were found when trying to delete Building Phases in Pipeline Purchasing.\u00a0 This is now fixed. PIPE-36377<\/li>\n
    • Pipeline client test sites were found to run extremely slow and display a 504 Gateway error when trying to load House BOM page on version 2022.1.6.\u00a0 This has been fixed through assessing RAM and coding functionality.\u00a0 PIPE-36531<\/li>\n
    • The Building Phase column on the Advanced House BOM page included the Building Phase Code but previously did not include this Code when searching the column.\u00a0 This is fixed.\u00a0 PIPE-36852<\/li>\n
    • It was found that the BOM Generation on Community and House pages are not consistent with each other. The Global Option, not assigned to the House, was showing in House BOM report if the report was generated in Community House BOM.\u00a0 This is resolved so that both BOMs are consistent.\u00a0 PIPE-37034<\/li>\n
    • Previously, the Supplemental quantity in House BOM did not have Use Value, yet Use Value is included in Community House BOM. This is corrected by removing the Use Value in Community House BOM for Supplemental quantity, creating consistency. \u00a0PIPE-37319<\/li>\n<\/ul>\n

      [\/vc_column_text][\/vc_column][\/vc_row]<\/p>\n","protected":false},"excerpt":{"rendered":"[vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text] New Features [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text] Trades Scheduling Activity [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]Pipeline Purchasing and Scheduling users can now communicate with the Vendor when a scheduling activity has been assigned to them without a purchase order. \u00a0Previously this was not done at the time of the work associated with the purchase order, but now […]","protected":false},"author":346,"featured_media":0,"parent":705,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"template-page-full-width.php","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-13325","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/help.strongtietech.com\/pipeline\/wp-json\/wp\/v2\/pages\/13325","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.strongtietech.com\/pipeline\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/help.strongtietech.com\/pipeline\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/help.strongtietech.com\/pipeline\/wp-json\/wp\/v2\/users\/346"}],"replies":[{"embeddable":true,"href":"https:\/\/help.strongtietech.com\/pipeline\/wp-json\/wp\/v2\/comments?post=13325"}],"version-history":[{"count":0,"href":"https:\/\/help.strongtietech.com\/pipeline\/wp-json\/wp\/v2\/pages\/13325\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/help.strongtietech.com\/pipeline\/wp-json\/wp\/v2\/pages\/705"}],"wp:attachment":[{"href":"https:\/\/help.strongtietech.com\/pipeline\/wp-json\/wp\/v2\/media?parent=13325"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}