General FAQ
Last updated
Was this helpful?
Last updated
Was this helpful?
Self-maintenance encompasses the activities you might undertake with your project after initial implementation and delivery by Threekit. There is no action needed to “keep things running”, but you may want to make modifications to aspects of your implementation, such as:
Adding new products
Changing the options available for existing products
Tweaking visual assets for improved quality or performance
Adding access tokens for embedding configurators on additional domains
Exploring/testing new platform features which you might consider augmenting your implementation with
Etc.
These are often small-scale, documented and/or exploratory efforts that don’t necessarily warrant engaging professional services to do for you.
The community knowledge base will help admins get their bearings and understand a lot of the basic tasks involved in setting up product configurations and visuals. Beyond that, what skillsets are required depend on what needs to be maintained. For example, if there is ongoing work on visual assets, a 3D artist background would be ideal. And if you need to make frontend integration changes to align with changes you make to your catalog and visual assets in the Threekit platform (ex. adding a new UI component connecting to a new product option, or embedding your existing product configurator in a new website), then you'd want someone with a web development background.
Threekit has a growing network of implementation partners with the expertise and flexibility to support our customers’ various needs across various engagements. Feel free to browse our partner list at , and speak with your Threekit account team for recommendations and introductions.
Knowing what will need to be self-maintained, and how, can affect some decision-making during the design and implementation of a project. Often there are things that could be designed/built in several different ways, and a need for self-maintenance can affect that decision. Thus, it is important for the project team to be aware of and discuss the need for self-maintenance and the trade-offs. For an oversimplified example, if you have a product that has an option for its paint color, and you need to easily modify the set of colors available from time to time in the future, you'd want to ensure a design and workflow that makes those changes simple. On the other hand, if you know the set of colors will never change, that might lend itself to a faster, simplified implementation.
If you do have plans for self-maintaining post-implementation, you would want to make sure you have sufficient discussions and/or handoff documentation from the implementation team regarding any specific workflows to make your desired changes (ex. "to add another product in a given product category, take the following steps...").
Keep in mind that migrations can take some time and updates will incrementally appear in the destination org. You would want to work with your initial implementation team to align on the considerations and workflow for safe and effective migrations into your production environment. This may involve bringing your site down for maintenance until migration and smoke testing are complete, or approaches that involve migrating new copies/versions of catalog items and assets, and only switching your integrations over to pull these new versions once everything is migrated and smoke tested.
David: Depending on the nature of the issue, there are a few resources available:
Sign up to receive notifications directly to your inbox regarding platform availability or issues, upcoming maintenance, and new releases.
It is in a limited capacity. At the time of this interview, it’s possible to pull player views as well as render usage by heading to the "Analytics" section:
We’ve also been listening to customer feedback and understand customers want more. Threekit is looking to provide detailed self-service metrics in the coming releases. We encourage you to keep an eye out for the latest product release info in your inbox and in the Threekit Community.
The general development workflow we recommend is to make and test out changes on your preview org (). For testing integrations, you can set up an integration environment that points to this preview org, for example to confirm your platform changes are coming through correctly in your website, or to build out new integration code/UI to go along with changes you make in your org. Once happy with your changes, you can initiate an org migration to copy those changes over to your production org ().
Although larger features are delivered on a quarterly release cycle, bug fixes and minor enhancements still occur from time to time throughout the year. To track various feature and bugfix releases, you can refer to release notes - you can check in periodically, review recent changes, and see if anything catches your eye that may benefit your setup or workflow. Upcoming releases and maintenance windows can also be found at our page. Lastly, platform updates are visible in the notifications area of your org (the "?" in the upper right - see image below). You can click on the notification and Select “Product Updates” to see recent platform updates:
Issue with platform service availability:
Problems with the Threekit platform:
Support access is required. If you can’t login and password reset doesn’t work, contact the customer success team at .
Unsure how to accomplish certain tasks or how to use parts of the platform: Visit the ThreeKit Community site where there are various guides, tutorials, and the platform documentation. You also have access to the to ask specific questions.
