HELP CENTER
keyboard_backspaceBack to MyConfigura layersNeed Help? Contact Us! bug_reportKnown Issues

Articles in this section

Migration Resources per Feature

Yewsiing Choong
  • Updated
As some of these can be quite complicated to grasp on why should you migrate to, and the amount of effort needed to migrate, we strongly recommend reaching out to our developer support team for guidance.
Or please reach out to Configura Account Managers or Project Managers for a more accurate estimation.
  1. Effort Needed

  2. Higher Priority Migrations: Essential to improving user experience
  3. Lower Priority Migrations: Long-term goals; not needed right away
  4. Code Replacing Migrations: Upgrade Features by replacing code
  5. Migrate if Needed: Migrate only if it's a Feature you want

 

 

Migrating to the latest code will help ensure a better experience for everyone. While there are a few migration efforts that not everyone will need to adapt to, we want to make sure everyone is aware of future efforts and resources needed to keep the CET experience great for everyone.

As we continue to grow and create new updates to CET, some of the older codings may not be as relevant. Migrating to newer coding allows Configura to focus on developing and maintaining new features.

 

Effort Needed

To help plan resources and time needed for migration, we have estimated the "effort" needed.

Large Extension Effort / Small Extension Effort

If you see "6 months/2 months", we are estimating that a large Extension will take approximately 6 months to migrate, and a small Extension approximately 2 months to migrate.

  • Effort means the time/resources needed to migrate to new code and test properly
  • A large Extension is defined as a major manufacturer extension that consists of at least 10 complex product lines and implemented with different methods or technologies.
  • A small Extension means a manufacturer Extension that consists of less than five product lines OR is mostly a data-driven Extension.
Please note that the estimation might vary due to the complexity of the products.
Please reach out to Configura Project managers or Account Managers for a more accurate estimation.

 

 

Higher Priority Migrations

Migrations that will help to improve basic/essential features or improve performance.

Standard Category (Abstract Office)

Effort: 1 month / 2 weeks

If your Extension's office categories have similar sounding categories (e.g. Seats, Chairs, chair) from other Extensions, migrating to CET’s standard categories is a good solution for standardizing office products categories.

 

Configura SIF

Effort: 1 month / 2 weeks

If a user have different manufacturer items in a single drawing, doing a SIF Export will result to order exports where manufacturers implement SIF exports into their code. 

Because all manufacturers haven't updated to this yet, users are still experiencing lots of issues trying to get one SIF to do everything they need it to do.

 

Associative Dimension

Effort: 1 month / 2 weeks

Associative Dimensions is turned on by default. If your Extension doesn't need to use Associative Dimensions, developers can turn it off to help with the performance of the dimension snapper by returning null in associativeLocations() in your Snapper implementation.

 

 

Lower Priority Migrations

These migration efforts should happen after the high priority efforts have been completed and are necessary for keeping the user experience great for the entire CET community.

Lazy Extension

Effort: 2 weeks / 1 week

Lazy Extension addresses extensions that take a long time to load.
The Lazy Extension solution loads only the Extension tabs that are selected and currently in use.
This allows for better performance and faster load time and is a fast solution to help performance for CET users.

 

PBR Materials

Effort: 3 months / 1 month

As part of the 12.5 update, PBR Materials gives higher quality renderings and helps the speed of exports – migration will enhance the new features coming with 13.0.

 

Physical Lightings

Effort: 1 month / 2 weeks

Lighting with precise lumens was introduced in CET 12.0, and migration will help enhance the overall rendering capabilities in CET.

 

 

Code Replacing Migrations

These are the latest codes that enhance and improve on some earlier features related to G2 like ProbObj, animations, PropsScheme and property box that can all be improved with these migrations.

G2-Related Features

A number of features related to G2, like ProjObj, animations, PropsScheme, and property box can be improved with specific migrations.

PropObj

Effort: 6 months / 2 months

A PropObj is an object that holds data that is dynamically defined by PropDefs. It is the basis for several new core features such as G2 properties, G2 animations, PropsSchemes as well as Catalogue Driven Schemes.

 

G2 Property Box

Prerequisite: PropObj
Effort: 6 months / 2 months

The main benefit of this migration is that you don’t need to implement the same properties for both animation and quick if you want it to show in both.
Having your properties in G2 is also the basis for implementing other features such as PropsSchemes.

 

G2 Animation

Prerequisite: PropObj
Effort: 6 months / 2 months

G1 animations used states to control what the animation should do. As a result, an animation would often be overloaded with responsibility if it has several states (think 3-step animations, for example).
Whereas G2 animations allow the spawning of another animation when the state should change, that allowed the code to be cleaner and more encapsulated.

G2 animation also has better interfaces to work with vessels. 

There are no specific resources relating to this feature migration. Please reach out to Developer training and support for further guidance.

 

PropsScheme

Prerequisite: PropObj, G2 Property Box
Effort: 6 months / 2 months

If your Extension users love using Schemes and would love to have more features about Schemes. Look no further than implementing PropsScheme, the next generation of Scheme frameworks succeeding the old CoreScheme.

These are the main features of implementing this:

  • Use Scheme Painter, a CET built-in way to copy properties from components to other components in a seamless way. 
  • Use Advanced selection to precisely select objects with shared tags, categories, part numbers, or levels. Then able to move, delete, rotate, and edit, apply Schemes and Part Tags or new categories.

And many more, which you can learn here:

 

Catalogue Driven Scheme

Prerequisite: PropObj
Effort: 6 months / 2 months

An approach for Catalogue developers to create scheme layouts from Catalogue Creator.

 

 

Migrate if Needed

Features we only recommend for migration only if your Extension needs it.

CollabPro (not released in Marketplace yet)

Effort: 6 months / 2 months

To take advantage of this new working model of CET, there might be some programming requirements to put in place before this is tentatively released on 13.5 (2022-11-21).
Make sure your Extension can fully utilize CollabPro with the correct, compliant programming.

For more information on this topic, please refer to the Best Practices Guide, available here:

 

Mirror Tools

Effort: 6 months / 2 months

Snappers can be mirrored as of 12.0, eliminating the hassle of implementing mirrors from scratch. The Mirror Tools can be migrated for better functionality in 13.0.

Was this article helpful?

0 out of 0 found this helpful
Return to top

Comments

0 comments

Please sign in to leave a comment.

Related articles