Welcome to the 12.0 Minor Release QA Testing Guide, please check with your developer to make sure these changes are available in your extension before testing.
In 12.0 Minor Release, there are some substantial bug fixes that were cherry picked and recommended for partner retest, for greater assurance towards CET stability.
Crash when switching to paper space
Developers made a crash fix, as user switches from 'model space' to 'paper space'. We recommend smoke test instructions of:
- Using 'model space' in (2D/3D/Split View) OR create new view by clicking on key 'V' using (2D/3D) , switch to 'paper space'. Repeating the switch back and forth should not crash CET.
- If your extension has auto-papers, try generating and make sure the output is expected.
Crash when deleting part tags when working with multifloor
This crash can be reproduced by deleting existing/new part tags that are in use by different levels in a multifloor. We recommend smoke test instructions of:
- Using your extension, create a multifloor with different snappers, Using new/default/customized tags, tag them in different levels. Then, in the part tagging dialog, delete the tags that are/aren't in use, ensure CET does not crash.
There are some notable new features in CET 12.0 Minor Release, with only some requiring smoke test to ensure CET stability.
This feature will improve how materials would look in CET. This is because materials will be more physically correct and can be controlled by even more parameters in Material Lab upon creation. For example, Metallic, Occlusion, Emissive, etc. However, it will be a silent release involving only the code base and there are no changes on the front end, which will make its full appearance in CET 12.5. Partners will also need to migrate their existing materials into PBR to make use of this feature, more information on this would release in the upcoming Developer's migration guide for 12.5. So, stick around!
But to give a sneak peek, a photo comparison below shows the difference of a non-PBR material (on the Left) and PBR-material (on the Right). Evidently, it has that improved look especially on the wall, and flooring.
To ensure that the code change does not affect CET in all aspects, we recommend smoke test instructions of:
- Using your extension snappers, try:
- Changing to different materials in the quick properties or scheme manager, make sure they look correct as before, watch out in 2D/3D.
- Perform a rendering and ensure the materials still look as accurate.
- Save and Load new/existing drawings to make sure no unintended visual changes happen.
- Create 'Customer Own Materials'(COM) and ensure they still work, refer to photo below.
There are several new features introduced to Catalogue Creator to manipulate the visibility of features and the cost in the bill of material (BOM). These features doesn't pose any direct impacts into the common CET workflow, hence treat this as an information sharing.
Product and Child Part Number
In CET 12.0 Minor Release, catalogue users have the option to control how part number and cost are defined by manipulating the generation of product codes.
Illustration below shows a sample catalogue product with a few product codes attached to different price tags. When the product is placed into CET, the Bill of Material (BOM) shows the final price tag and the product code generated as defined in catalogue.
Here what it looks like with these different options applied:
Omit Product Code.
When ticked, it excluded that product's code in the final part number shown in BOM. Thus only the part number and price of the selected option is shown.
Disabled Functional Lookup.
When ticked, It does not look up to the price set to the particular child product but maintaining the price for parent product. Although the part number for child product is displayed in calculation.
Catalogue specialist can now control the properties that can be shown in property box using the properties visibility feature in catalogue creator. Using this new feature, properties of a main/parent product and additional/child product can be control to either to be shown or stay hidden depending on the product rules.
Sync Group Code
When working with abundant additional product in catalogues, the common feature options can be synchronize grouped together, so that one change can push the effect to all the synchronized additional products.
Take a look below at the configured 'Work from home' catalogue set, with laptop (Left) and monitor (Right) as additional products, by changing the 'Wallpaper' on 1 row, it pushes to all synchronized additional products.
Main Product Column
In 12.0 Minor release, a new column is added in the Bill of Material (BOM) called Main Product. By using this column, user will be able to identify which parent product an additional product belongs to when using catalogue snapper.
In the screenshot below, Table is the Main/Parent product. By referring to the main product column, one can tell that Leg and Accessories is the additional product belongs to Table.
Link to the Webinar Recording: Click Me
Have additional questions?
Links that may come handy to you
Release and Migration Best Practices
As always, reach out to us at email@example.com if you have questions
Please sign in to leave a comment.