Package's Update Type
There are a few different types for package's update:
Minor Content Updates
- When customer product has minor change. (E.g. New products added to their toolbox, changes to existing product, new or changed finishes/materials, pricelist change, etc) Update type which use by customer extensions.
Major Content Updates
- When customer product has major change. (E.g. New products added to their toolbox, changes to existing product, new or changed finishes/materials, pricelist change, etc) Update type which use by customer extensions.
Minor New Features
- When minor new feature added. (E.g. Ability to create 2D view clip in custom shape)
Major New Features
- When major new feature added. (E.g. Ability to create 2D View clip)
Minor Bug Fixes
- When minor bug has been fixed. Bug that will not affect user’s operation but would be good to fix. (E.g. Grammar error/Missing translation/Refresh issue/etc.)
Major Bug Fixes
- When major bug has been fixed. Whichever affects user’s operation like a function which user uses a lot, there is workaround for now, but existence of the bug annoys users. (E.g. Dimension in 2D toolbar is not working, user still able to activate it from Tools component tab as workaround but extra steps needed)
Critical Bug Fixes
- When critical bug has been fixed. Whichever affects user’s operation and no workaround. (E.g. Crash when creating new drawing/Unable to print or create pdf)
How to Set a Package's Update Type
Build Central (CET Operator)
- Go to Build Central.
- Switch to Upload tab after build is done.
- Upload packages of the extension and you can specify the Update Type in the drop-down menu.
Build Center (MyConfigura)
- Go to the MyConfigura page.
- Go to Dev Center -> Build Center.
- Go to Builds, and search select the build you have access to.
- At the right-most side, there should be an edit icon. Click on it:
- And you'll be directed to the page for setting the package type:
The new metadata is only supported when updating from CET 11.5 or later, so meta data set on 11.5-extensions will not be shown for the user when updating from CET 11.0 to 11.5.
If nothing is set, it will default to a Minor Content Update.
Forcing an Update
The developer can (but not recommended) add a due date for users to update. If they do, the users will be forced to update on the next startup.
This update will be forced on the start of CET during/after the due date. This can be an inconvenience to users, so only do this when absolutely needed!
Clicking on the Advanced dropdown will reveal the Due date field where you can set to force the update by that date.
Comments
2 comments
Does major update mean that a drawing saved in that major update (e.g. Critical Bug Fixes, Major New Features, Major Bug Fixes, etc.) will not open on other machine not having that package updated. Please suggest.
Hi Aman! You are correct. When a user creates a drawing in a newer version of CET Designer, it cannot be opened in an old version. Likewise, if they open in old drawing in a new version, then save it, it also cannot be re-opened in the older version, even though that's where it was originally opened and saved. We recommend that people who work on drawings together update all at the same time so that they do not run into this while collaborating.
Please sign in to leave a comment.