Replies: 1 comment 2 replies
-
|
Great update! Thank you all! 😍 Question about the new label engine tho - is there a way to add custom labels to those that already exist as "templates" @cram42 ? We're probably gonna use the "old" engine for the labels still since I didn't see a way to configure a template / make a new one. But all in all great update! ❤️ |
Beta Was this translation helpful? Give feedback.
-
|
Making a new template is a bit of work - we're happy to work with you on sizing, etc, but there isn't currently a way to do that without touching code. You can see the isolated Dymo PR here which might provide some guidance: #13492 |
Beta Was this translation helpful? Give feedback.
-
|
Alright, the old label still works like a charm so not a problem really :D |
Beta Was this translation helpful? Give feedback.
-
Welcome to the release notes for Snipe-IT 6.2. We've been trying to fix as many bugs (and sneak in as many small features) as we can before Snipe-IT v7 comes out.
Reminder that Snipe-IT v7 WILL REQUIRE PHP 8.1 or higher!! This is a slightly higher version than the PHP 8.0 version we've been saying for a while now, so please make sure you're ready. The reason for this slight bump in minimum requirements is that we've decided to launch Snipe-IT v7 on Laravel 10, which requires that slightly higher version. Our goal is to have Snipe-IT v7 out in a month or two.
Highlights
This release includes lots of bug fixes detailed below. It introduces a new label engine which will hopefully be a big help to those folks who have struggled with getting their specific printers to work with Snipe-IT labels, but also has a legacy fallback, so if you have things just right, nothing needs to change for now.
We've also added back the sticky header for long lists, and column-reordering in those table views:
Screen.Recording.2023-09-15.at.10.04.46.PM.mov
Additionally, we made some improvements to the importer, added a minimum quantity on models so you will get those alerts in your bell icon when you don't have enough of a particular asset model available. And we've fixed a few small inconsistencies in the API with regards to boolean fields.
Important! SCIM support did not previously support changing email addresses via Azure and some other SCIM clients. Under v6.2, that has been fixed, but if you were depending on the previous behavior, you may get unexpected results.
What's Changed
saml_idp_metadatato MEDIUMTEXT by @snipe in Change settings tablesaml_idp_metadatato MEDIUMTEXT #13255qr_code presentby @Godmartinz in fixed margin if qr_code present #13233$this->get_depreciation()returns by @snipe in Check that $this->get_depreciation() returns #13346webhook_endpointdata type from varchar to a text by @Godmartinz in Fixedwebhook_endpointdata type from varchar to a text #13392Company::scopeCompanyablesfromReportsControllerby @marcusmoore in Removed unneededCompany::scopeCompanyablesfromReportsController#13431emailto companies by @Robert-Azelis in Add email to companies #13442LOGIN_AUTOCOMPLETEas env var by @snipe in Fixed #13365 - Added LOGIN_AUTOCOMPLETE as env var #13457strpos()by @marcusmoore in Fixed passing invalid argument tostrpos()#13456changedinfoand removed encrypted values from Asset history by @Godmartinz in Added eager loading forchangedinfoand removed encrypted values from Asset history #13507asset_tagon null (rollbar Windows Platform, Admin-backups, wrong backup path and slash #3541) by @inietov in Fixed ErrorException: Attempt to read property "asset_tag" on null (rollbar #3541) #13547department_idin API patch request by @marcusmoore in Added validation around department_id in API patch request #13575min qtycolumn by @Godmartinz in Fixed nullability on asset modelmin qtycolumn #13595CompanyableTraittoDepartmentmodel by @marcusmoore in AddedCompanyableTraittoDepartmentmodel #13415New Contributors
Full Changelog: v6.1.2...v6.2.0
This discussion was created from the release v6.2.0.
Beta Was this translation helpful? Give feedback.
All reactions