The process editor allows enterprises to freely customize craft rules while minimizing the cost of feature development and program code maintenance.
The process editor, starting with countertop moldings as a pilot, assists in generating class models (including sinks and merged no-handle models), successfully unlocking multiple feature links, and continues to expand its application scenarios and business fields. A brief introduction is provided below~
Custom script generation is the starting point of the craft editor. The original intention is to address different merchants having different generation demands for countertops, moldings, virtual hardware, etc. We provide a set of "ability to generate rules customized by merchants", allowing the writing of external scripts through the process editor to customize and modify the generation logic, thereby enabling personalized manipulation of the generated model results. Here are some typical case representations:
Common Issues:
In the fields of countertop moldings and handles, etc., in addition to model entities, it is often necessary to add hardware accessories. What product adds which accessories, how many, and what model are all enterprise calculation rules and are related to production quotation and delivery. Previously, it relied on designers manually adding it on the panel, which is error-prone and increases the design burden, unfavorable for management.
Feature Advantages:
To solve similar problems as described above, the process editor can be used to formulate custom rules for the merchant, configure the relationship between the main and auxiliary parts, write scripts, and automatically generate auxiliary accessories when generating model entities.
In actual production of countertop moldings, different customers have their production specifications. For instance, how long the line is before it breaks, when to thicken the countertop, partial visible process, etc. These customized process rules will affect the actual effect of the generated model, like some merchants want the countertop flush, some do not, some lines need cutting, and some do not, so we cannot use uniform generation rules to satisfy all business scenarios, especially when there are conflicting rules.
To address the similar issues mentioned above, the process editor can be used to adjust the generation logic within a limited scope, allowing the generated model effect to be as the script presets.
Large enterprises have strict control over production, with inherent regulations on what can and cannot be done with process. Therefore, they strictly monitor the compliance of the model drawn by designers. If a process cannot be executed, it cannot be drawn. If it can be drawn, it can be produced. Thus, the tool must strongly constrain the designer's design behavior.
To solve issues similar to those above, the process editor can preset some conditions to configure the modifiability of front-end parameters, including: display/hide, ash, options, value range.
Even though we have applied some entry constraints on designers' operational behavior, the actions of revision and modification may cause the current model not to meet the process requirements. Therefore, it is necessary to detect the model after generation to determine if it is correct according to the previous "process configuration". Alternatively, write scripts to judge the relationship between the generated model and other models (such as between sinks and countertop fasteners), alert designers on the compliance of the current model, and achieve order interception. Unlike rule detection, the process editor has relatively flexible advantages in writing complex geometric calculation scripts and manipulating generated models.
Generated models are a one-time transaction, with the generation script confirmed at generation, and parameter information of the model set once generation is complete. Each generated model is independent. In actual business scenarios, models are interrelated with each other and with the environment. These associations may not be related to design behavior, merely required by enterprises during output and quotation to calculate and record this information for downstream partners. If the information accompanies the model at generation, it cannot change with the environment, requiring the model to add these related information further downstream.
To resolve similar issues above, the process editor can be used to write relationship scripts that operate model parameters when outputting data after design completion, supporting addition and modification.
Generated class models differ from regular parametric models when creating products: parametric models are specific products established by users through parametric editing based on their needs, while generated class models are pre-scripted by Coohom, belonging to the public library as hidden products. Enterprises cannot customize product information of public library hidden products. Therefore, downstream backend software cannot interface with models through recognizing product codes and such.
To resolve this issue, the process editor can be used to write mapping tables (generation parameters corresponding to product codes) and pre-store product codes corresponding to the model during generation, allowing modification of the model’s product code when exporting. Currently, modifiable product information includes: product code, model number.
Generated model scripts being Coohom pre-written scripts do not allow users to customize generation parameters. Yet, users need to add custom variables to express auxiliary information of the generated model, and these variables must be visible, modifiable, and exportable by the frontend designer.
To solve this problem, the process editor can be used to add custom parameters to the outline products.
What went wrong?
This will change the display language on this website.
We use cookies and similar tools to bring you a smooth and convenient experience on our site. To learn more about how we use cookies, view our Statement on Cookies here.
Along with User Agreement and Privacy Policy provided by Coohom Inc. and its affiliates (“we”, “us” or “Coohom Group”), this Notice provides you (or “user”) with information about the cookies that are used by the features and services of Coohom official website or Coohom Platform (“Coohom Platform”). This Notice will be reviewed from time to time to ensure that its content is kept up-to-date. If any changes are made, we will publish the latest version of the Notice here. When we make significant changes, we will notify you of the change the next time you visit Coohom Platform or by other means of communication.
When you visit Coohom Platform, the site asks your browser to store a small piece of data (text file) called a cookie on your device in order to evaluate the performance of the site. We also use third-party cookies, which are cookies from a domain different than the domain of Coohom Platform you are visiting, for marketing efforts.
We use the following categories of cookies:
Strictly necessary cookies are necessary for Coohom Platform to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but that will cause some parts of Coohom Platform to not work.
Performance cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site.They help us to know which pages are the most and least popular and see how visitors move around the site.If you do not allow these cookies we will not know when you have visited our site and will not be able to monitor its performance.
We also cooperate with third-parties that deploy cookies when users interact with marketing communications. Marketing cookies collect personal information such as your IP address and clicks. Collected information is used to evaluate the effectiveness of our marketing campaigns or to provide better targeting for marketing. We do not always have control over those cookies.
The "Cookie Settings" can be utilized to customize your cookie preferences. The "Cookie Settings" will record when you have consented to or rejected our Notice and will ask for consent once a year to ensure users stay up-to-date with changes to our Notice. All the performance cookies and marketing cookies are controlled by the "Cookie Settings". You can also access the “Cookie Settings” anytime from the link in the footer of Coohom Platform.
All of the cookies used on Coohom Platform, on third-party websites and through emails can be enabled or disabled through your browser. To control cookies through your browser, follow the instructions usually located within the “Help”, “Tools” or “Edit” menus in your browser. Please note that disabling a cookie or category of cookies does not delete the cookie from your browser unless manually completed through your browser function.
Your data collected from cookies can be deleted. If cookies are deleted, the information collected prior to the preference change may still be used. However, we will stop using the disabled cookie to collect any further information from your user experience. For marketing cookies, when a user opts out of tracking, a new cookie is placed to prevent users from being tracked.
You can set your browser to block strictly necessary cookies, but that will cause some parts of Coohom Platform to not work.
You can accept or refuse the use of performance cookies or marketing cookies at any time. If you choose to reject the use of performance cookies or marketing cookies, you will still be able to use Coohom Platform, and your use of all the features and areas of Coohom Platform will not be limited.
We may update this Notice from time to time or for other operational, legal or regulatory reasons to make changes in the cookies we use. Therefore, please re-read this Notice periodically to learn about our use of cookies and related technologies. The date at the top of this Notice indicates when it was last updated.
If you have any questions about our use of cookies, please feel free to contact us via email at support@coohom.com.
We will respond to your questions, comments or suggestions within 30 days after we receive them and verify your user identity.