Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Global search: Find components with given distance (e.g. "0") in assemblyAcknowledged

1. Describe the ProblemWe would like to have a functionality in creo to find certain components in assemblies by given distances. The command should sound e.g. like, "Please creo, show me all "floating" objects in my assembly".While "floating" means a distance of e.g. 0 or 0.1 mm or greater than XY to any next component,  Following picture with a primitive example should be comprehensive:  The green component has a distance of greater than 0 to all other components in the assy. All other parts are tangent (coincident) or penetrating the housing. My idea should reactivate that one:https://community.ptc.com/t5/Creo-Parametric-Ideas/Improve-the-SEARCH-FIND-tool-to-find-components-with-additional/idi-p/458025Sadly, the original idea was archived.2. Are you using a workaround?As existing functionality does not deliver quick and complete results (Pairs clearance, global clearance, Search tool...), some of our users found a workaround in CCX-module (clearance and creepage extension). With that, it is possible to create electrical nets by selecting components and exclude them later from selection. So, it is a misuse of a quite expensive license for global geometrical distance analysis. And, we need to doublecheck measurements, and in the end combine this with simplified reps and/or similar selection methods. Furthermore, the user has to know every single component in the assembly. This gets difficult with huge assemblies including lots of 3rd-party models. So, our woraround isn´t 100% reliable.3. What is the use case for your organization?We could detect all components that are not touching other models. With these models, our thermal and flow simulaition results wouldn´t be corrupted anymore by misleading distance measurements. Manual preparation could be saved.4. What impact does this problem currently have on your organization?- Long preparation time, - Wrong simulation results as we can´t detect all areas for fluids in our assemblies, - We have to use a rare, specialized and expensive license for a more or less easy geometrical task.

Modify/erase post regeneration relations with ModelCHECKArchived

1. Describe the ProblemIt's only possible to erase or modify the initial relations but it's not possible to modify/erase the post regeneration relations 2. Are you using a workaround?We create a Real Number parameter DATE_POST_REL_PRT_ACTUAL with the value 20240203.000000 (which is the date of the actual configuration) by ModelCHECK, if it is not available. In the .mcs file there are to lists which have the possible values inside ###LISTS STD_USER_LIST_FILE text/error_post_rel_prt.txt STD_USER_LIST_FILE text/error_post_rel_asm.txt These two text files are located in the text folder of the ModleCHECK configuration files. Inside the error_post_rel_prt.txt file there is only one line LIST_ERROR_POST_REL_PRT Use Mapkey uspr to update post relations The same at the error_post_rel_asm.txt LIST_ERROR_POST_REL_ASM Use Mapkey usar to update post relations In the .mcs file I have this for parts #Additional parameters for post relations check PRT_PARAMETER DATE_POST_REL_PRT_ACTUAL REAL EQ 20240203 PRT_PARAMETER ERROR_POST_REL_PRT STR NEQ LIST_ERROR_POST_REL_PRT and this in the assembly section #Additional parameters for post relations check ASM_PARAMETER DATE_POST_REL_ASM_ACTUAL REAL EQ 20240203 ASM_PARAMETER ERROR_POST_REL_ASM STR NEQ LIST_ERROR_POST_REL_ASM Additional I have a mapkey (uspr) which erases the post regeneration relations in the part and loads afterwards the actual post regeneration relations from a text file which is located in the text folder of the ModleCHECK configuration files. The same I have for assemblies (Mapkey named usar) with assembly post regeneration relations also located in the text folder of the ModleCHECK configuration files. Does the parameter DATE_POST_REL_PRT_ACTUAL not fit at parts, it will show the hint "Use Mapkey uspr to update post relations" in the ModelCHECK report until you used the mapkey uspr (I created a button for the mapkey ad stored it in the creo_parametric_customization.ui) The same I have at assemblies Does the parameter DATE_POST_REL_ASM_ACTUAL not fit at parts, it will show the hint "Use Mapkey usar to update post relations" in the ModelCHECK report until you used the mapkey usar (I created a button for the mapkey ad stored it in the creo_parametric_customization.ui) Here my mapkey for assemblies mapkey usar @MAPKEY_NAMEupdates the asm post regen relations to newest version;\ mapkey(continued) @MAPKEY_LABELupdate post regen asm rel;\ mapkey(continued) ~ Activate `main_dlg_cur` `page_Tools_control_btn` 1;\ mapkey(continued) ~ Command `ProCmdMmRels` ;~ Open `relation_dlg` `PrePostOM`;\ mapkey(continued) ~ Close `relation_dlg` `PrePostOM`;\ mapkey(continued) ~ Select `relation_dlg` `PrePostOM` 1 `PostRegen`;\ mapkey(continued) ~ Select `relation_dlg` `MenuBar1` 1 `Edit`;\ mapkey(continued) ~ Close `relation_dlg` `MenuBar1`;~ Activate `relation_dlg` `PBSelectAll`;\ mapkey(continued) ~ Select `relation_dlg` `MenuBar1` 1 `Edit`;\ mapkey(continued) ~ Close `relation_dlg` `MenuBar1`;~ Activate `relation_dlg` `PBDelete`;\ mapkey(continued) ~ Update `relation_dlg` `RelText` 0;\ mapkey(continued) ~ Select `relation_dlg` `MenuBar1` 1 `File`;\ mapkey(continued) ~ Close `relation_dlg` `MenuBar1`;~ Activate `relation_dlg` `PBRead`;\ mapkey(continued) ~ Trail `UI Desktop` `UI Desktop` `DLG_PREVIEW_POST` `file_open`;\ mapkey(continued) ~ Activate `file_open` `Pro|Library_shortcut`;\ mapkey(continued) ~ Activate `file_open` `Pro|Library_shortcut`;\ mapkey(continued) ~ Select `file_open` `Ph_list.Filelist` 1 `Modelcheck`;\ mapkey(continued) ~ Activate `file_open` `Ph_list.Filelist` 1 `Modelcheck`;\ mapkey(continued) ~ Select `file_open` `Ph_list.Filelist` 1 `config`;\ mapkey(continued) ~ Activate `file_open` `Ph_list.Filelist` 1 `config`;\ mapkey(continued) ~ Select `file_open` `Ph_list.Filelist` 1 `text`;\ mapkey(continued) ~ Activate `file_open` `Ph_list.Filelist` 1 `text`;\ mapkey(continued) ~ Select `file_open` `Ph_list.Filelist` 1 `post_regeneration_asm.txt`;\ mapkey(continued) ~ Activate `file_open` `Ph_list.Filelist` 1 `post_regeneration_asm.txt`;\ mapkey(continued) ~ Activate `relation_dlg` `PB_OK`;\ mapkey(continued) ~ Command `ProCmdRegenAuto`;\ mapkey(continued) ~ Activate `main_dlg_cur` `user_custom_page_304141424_control_btn` 1; And here my mapkey for assemblies mapkey uspr @MAPKEY_NAMEupdates the post regen relations to newest version;\ mapkey(continued) @MAPKEY_LABELupdate post regen prt rel;\ mapkey(continued) ~ Activate `main_dlg_cur` `page_Tools_control_btn` 1;\ mapkey(continued) ~ Command `ProCmdMmRels` ;~ Open `relation_dlg` `PrePostOM`;\ mapkey(continued) ~ Close `relation_dlg` `PrePostOM`;\ mapkey(continued) ~ Select `relation_dlg` `PrePostOM` 1 `PostRegen`;\ mapkey(continued) ~ Select `relation_dlg` `MenuBar1` 1 `Edit`;\ mapkey(continued) ~ Close `relation_dlg` `MenuBar1`;~ Activate `relation_dlg` `PBSelectAll`;\ mapkey(continued) ~ Select `relation_dlg` `MenuBar1` 1 `Edit`;\ mapkey(continued) ~ Close `relation_dlg` `MenuBar1`;~ Activate `relation_dlg` `PBDelete`;\ mapkey(continued) ~ Update `relation_dlg` `RelText` 0;\ mapkey(continued) ~ Select `relation_dlg` `MenuBar1` 1 `File`;\ mapkey(continued) ~ Close `relation_dlg` `MenuBar1`;~ Activate `relation_dlg` `PBRead`;\ mapkey(continued) ~ Trail `UI Desktop` `UI Desktop` `DLG_PREVIEW_POST` `file_open`;\ mapkey(continued) ~ Activate `file_open` `Pro|Library_shortcut`;\ mapkey(continued) ~ Activate `file_open` `Pro|Library_shortcut`;\ mapkey(continued) ~ Select `file_open` `Ph_list.Filelist` 1 `Modelcheck`;\ mapkey(continued) ~ Activate `file_open` `Ph_list.Filelist` 1 `Modelcheck`;\ mapkey(continued) ~ Select `file_open` `Ph_list.Filelist` 1 `config`;\ mapkey(continued) ~ Activate `file_open` `Ph_list.Filelist` 1 `config`;\ mapkey(continued) ~ Select `file_open` `Ph_list.Filelist` 1 `text`;\ mapkey(continued) ~ Activate `file_open` `Ph_list.Filelist` 1 `text`;\ mapkey(continued) ~ Select `file_open` `Ph_list.Filelist` 1 `post_regeneration_prt.txt`;\ mapkey(continued) ~ Activate `file_open` `Ph_list.Filelist` 1 `post_regeneration_prt.txt`;\ mapkey(continued) ~ Activate `relation_dlg` `PB_OK`;\ mapkey(continued) ~ Command `ProCmdRegenPart`;\ mapkey(continued) ~ Activate `main_dlg_cur` `user_custom_page_304141424_control_btn` 1; Important! I have my modelcheck configuration in a folder called Modelcheck which is located in the creo Library! In the config.pro there is the line modelcheck_dir $LIBPATH\Modelcheck\ In this folder there is the config folder with all subfolders which contains the ModelCHECK configuration files (complete config folder copied from path C:\Program Files\PTC\Creo 8.0.9.0\Common Files\modchk\text\german to Library\Modelcheck and modified to the company rules) This works perfect as workaround3. What is the use case for your organization?Important relations for mass/volume calculations are located in the post regeneration relations and should not be modified by the user4. What impact does this problem currently have on your organization?No big impact because we use the workaround but this is complicated to set up

Use SIMD GPU for faster edge highlighting instead of CPUAcknowledged

1. Describe the ProblemI’ve created a model with over 1 million components while the performance is quite good as shading, It is extremely slow when painting and highlighting all the edges. Many of the bottlenecks in edge visualization—such as geometric calculations and hidden line removal—are inherently parallelizable and could benefit greatly from GPU-optimized SIMD operations. Here’s how this could work: How SIMD on GPUs Can Accelerate Edge Rendering 1. Parallel Processing of Edges• With SIMD, groups of edges (or even multiple vertices within edges) can be processed simultaneously in parallel on the GPU. Tasks like:• Edge visibility testing (z-buffer checks).• Crease angle calculations for highlighting sharp edges.• Silhouette determination for edge lines.• Instead of looping through edges serially on the CPU, thousands of edges can be processed at once using GPU SIMD pipelines.2. Hidden Line Removal• GPUs can leverage SIMD for ray-based visibility testing, where multiple rays can simultaneously determine if edges are occluded.• This is similar to the ray tracing acceleration used in modern GPUs with hardware like RT cores (e.g., NVIDIA RTX).3. Line Rasterization• Modern GPUs are designed to rasterize triangles, not lines. SIMD could be applied to optimize thin line rendering by processing multiple lines as vectorized operations, reducing the computational load of each individual line.4. Edge Culling• Tasks like view frustum culling (removing edges outside the camera view) or back-face culling (hiding edges on obscured surfaces) can use SIMD to evaluate multiple edges simultaneously.5. Bounding Volume Hierarchies (BVH)• If edge rendering is integrated into a BVH-like structure (common in ray tracing), SIMD can traverse multiple BVH nodes or check multiple edges in parallel, greatly accelerating visibility tests. Why the GPU is Better Suited Than the CPU • Massive Parallelism: GPUs have thousands of cores designed for parallel workloads, ideal for edge rendering tasks.• Vectorized Hardware: GPUs are inherently SIMD machines, making them better suited for workloads like edge calculations.• Specialized Hardware: Technologies like NVIDIA’s RTX or AMD’s RDNA can accelerate geometry processing, visibility testing, and rasterization more effectively than CPUs. Why CAD Software Hasn’t Fully Exploited This Yet 1. Legacy Architecture• Most CAD systems were designed when CPUs were the dominant compute resource. Edge rendering pipelines may still rely heavily on CPU-bound calculations.2. Focus on Precision, Not Performance• CAD tools prioritize geometric accuracy, often requiring double-precision math for edges, which many GPUs struggle with compared to CPUs.3. GPU Workload Partitioning• Current CAD systems primarily use GPUs for shaded rendering, leaving edges and hidden line calculations to the CPU. What Could Be Done to Improve This 1. Move Edge Computations to the GPU• Modern CAD software could offload edge computations (e.g., visibility, culling, silhouette detection) to GPU shaders using CUDA, OpenCL, or Vulkan.• For example:• Silhouette Detection: Compute edge normals and back-facing edges directly on the GPU.• Hidden Line Removal: Use parallel z-buffer tests in fragment shaders.2. Leverage Ray Tracing Hardware• With modern GPUs supporting ray tracing, edge visibility and hidden-line removal could use hardware-accelerated BVH traversal to speed up computations.3. Optimize Edge Rendering Algorithms• Use SIMD-friendly data structures like structures of arrays (SoA) instead of arrays of structures (AoS) to better align with GPU memory access patterns.4. Adopt Real-Time Rendering APIs• Integrate real-time rendering APIs like Vulkan or DirectX 12, which provide better GPU control and optimization for tasks like edge rendering. Future Potential GPU-based SIMD acceleration for edge rendering could enable:• Near-instant edge visualization for massive assemblies.• Real-time hidden-line rendering for interactive design workflows.• Better scalability as models grow larger and more complex. If CAD vendors adopt more GPU-centric approaches to edge rendering, tasks like displaying edges in a 1-million-component part could be as fast as shading today. Some forward-looking CAD systems (e.g., Unreal Engine CAD imports) are already moving in this direction. 2. Are you using a workaround?None. Simplified reps3. What is the use case for your organization?Performance4. What impact does this problem currently have on your organization?Heavy regeneration and frozen screen waiting to repaint.

Enable mobile devices for point cloud scanning to Creo ParametricAcknowledged

1. Describe the ProblemDesign requires information on surroundings/interfaces to make sure form, fit and function of products. The legacy method to genereate massive point clouds and utilize them on product design is not really supported optimally at Creo Parametric. The Reverse Engineering Extension (REX) exist, but it is a dedicated tool for those, who want to crate surfaces based on scanned data. For general engineerig purpoces, where one just wants to use scanned points as rough surroundings to the design, the REX approach is a overkill. The ability to put stationary images to backround of Creo Parametric design has some value, but positioning those photos to 3D is sometimes a tideous task, that requires time and effort.2. Are you using a workaround?Sketchbook and ruler, stationary photos and maby videos, that are not connected to design. Currently there is some applications and mobile devices, that allow scanning 3D. The data from these applications are of intrest, particularry should there be easy integration to Creo Parametric. Currently one can go through STL to import geometry to Creo Parametric, which will require steps for data cleanup etc.3. What is the use case for your organization?Routed system design: piping and cabling. Generic 3D design to support manufacturing, operation and R&D. The feature is general purpoce at its nature. The company Varjo has released an Teleport platform, that allow sharing of 3D data, captured by camera to be shared. It would pormote efficency to allow Creo Parametric users to embed the 3D immersive experiences to design and utilize them for the design refrences. https://teleport.varjo.com/share/80a3f6815bfd4d6fb5fc3092acd6b631/ https://teleport.varjo.com/share/70029249cbc54133b0c23a973f5616af/ https://www.linkedin.com/posts/varjo_were-thrilled-to-announce-that-teleport-activity-7266815947192029185-4XB3?utm_source=share&utm_medium=member_desktop4. What impact does this problem currently have on your organization?Time to market, operational efficiency -just name the few.

Hole centermark size on drawing (axis offset)Acknowledged

The suggestion is that have Creo check the size of the hole or feature and extend the centermark/axis offset as a percentage of that measured/defined size.Currently the lines are extended as much for small holes as for large holes.Only on a certain cases is there an exact match that pleases engineer, which now results in most of them manually resizing the centermarks or changing the drawing properties (which is again one-size-fits-all)   1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.All industries using 2D drawings and documenting models that have holes.I'm an external consultant visiting multiple firms designing with creo, this question comes up everytime.2. What version of Creo Parametric are you currently running?Creo parametric up to version 9.0.1.0 as of posting this idea.3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.see screenshot above. Worst case is a drawing with a lot of small holes and some big that get the same offset rule applied.4. What is the use case for your organization?as mentioned , documenting models with holes.5. What business value would your suggestion represent for your organization?This will reduce engineering time on detailing, saving hours if not days when cumulated over multiple engineers.

Allow the Find tool in Creo View to search in multiple Views without reopen the Find dialogDelivered

Allow the "Find" tool in Creo View to search in multiple Views without having to reopen the "Find" dialog again after changing the view 1. What product and version are you running?Creo View 10.02. What is the problem?It is not possible to search for the same parts, body or attribute names in different views leaving the "Find" dialog open. A search is always limited to the view in which the "Find" dialog was opened.(view in My Videos) 3. Are you using a workaround? If yes, please describe it.Close the "Find" dialog box, change the view and reopen the "Find" dialog.If you want to search for the same parts in different views, this can result in a lot of unnecessary mouse clicks.4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.Locating parts by item number in very large assemblies when there are multiple views of smaller assemblies or assembly units.Creo View is primarily used in machine assembly. The positive effect would be that there would be fewer mouse clicks and mouse travel paths.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)The Customer design and build packaging equipment for pharmaceutical, consumer, nonwoven and life science products. They have more than 2.800 employees in more than 10 subsidaries world wide and have around 350 designers working with PTC's CAD and PLM products.All users in assembly, sales and purchasing could work more efficiently and quickly and would save a lot of clicks and mouse meters.Related to article Article CS407329  

Creo View: multiple objects open in one session, save annotation set by individual objectAcknowledged

1. Describe the ProblemIf you use Creo View annotations to review multiple objects in the same Creo View session all annotations are saved in one annotation set on the primary object instead of an annotation set by individual object. Saving an annotation set requires filling in attributes that do not feel intuitive for a user. This makes the review process inefficient if you would like to have review feedback documented by object. 2. Are you using a workaround?After making annotations on an active object, save the object’s annotation set first, then switch to a second object and make it primary.3. What is the use case for your organization?When reviewing a product, you would like to review several objects (3D, PDF, etc) in one Creo View session and put remarks on the opened objects. At closure of Creo View you expect the remarks to be saved automatically in an annotation set by individual object without manually adding attributes. Creo View could know that the representation is opened from a specific object (e.g., promotion request, problem report, change notice) and should be able to use this to set the required attributes of an annotation set (if required at all). Possible other solution would be to make the active object primary automatically when switching between objects in Creo View. I see this as a work around and not as an efficient solution.  4. What impact does this problem currently have on your organization?All users reviewing product data using Creo View.

Allow MBD Hole Note to be according to ISO 129-1 , no capital XAcknowledged

1. Describe the ProblemAs of https://www.ptc.com/en/support/article/CS351946 the hole note token exclusively conforms to ASME standard Y14.5 section 1.9.5 and does not adhere to ISO 129-1 since it consists of a capital 'X' letter.In standard ISO 129-1 chapter "Repeated dimensions" it is stated: 'When a feature is repeated on the drawing, it is possible to simplify the indication of its dimension on the drawing by indicating:— on one instance of the feature, the nominal dimension (with a property indicator symbol if appropriate), preceded by the associated number of repetition, followed by a multiplication symbol (×) and a space (e.g. 2× ⌀18).Since this also applies to MBD hole notes, we Creo users cannot use the token that evaluates from HOLE_INSTANCE_X_SYMBOL because it always results in a capital 'X'.On the other hand, PTC claims Creos MBD features to be conforming to ISO 129 multiple times, and there is even a DTL setting for a similar requirement that also results in using the multiplication sign:DTL setting datum_target_area_multiply_sign:Default and Available Settings:• capital_X*—For ASME symbols, set this value when displaying datum target area for a rectangle.• lowercase_x—For ISO symbols, set this value when displaying datum target area for a rectangle.• multiplication_sign—For ISO symbols, set this value when displaying datum target area for a rectangle. So this idea is to support conforming to ISO 129-1 where ISO mode is used (not everywhere).Of course, this is a mutual exclusive thing - it cannot be at the same time × and X, as models are not at the same time metric and imperial in tolerance mode.Ideally that would be without any interaction for the user, but it would also make sense to introduce a DTL option like above, or even treat this hole note topic as part of an existing DTL option for MBD.Best Regards2. Are you using a workaround?no workaround except manually editing each hole note - who should pay that?3. What is the use case for your organization?Use case is to be compliant with ISO 129-1 which is also a prerequisite for some suppliers in automotive for example.4. What impact does this problem currently have on your organization?We advise not to use hole notes as the result using them would mean too much manual work.

Make ModelCHECK ready for MBD - facilitate supersession of drawing centric workflowUnder Consideration

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?9.0.5.0 and testing 10.0.1.02. What is the problem?ModelCHECK does not report many drawing centric 'things' that are obsolete to do in a Model Based Definition centric workflow. This includes existing drawing dimensions, number of parameters designated, unwanted symbols, unwanted relations, number of different kinds of notes (the default NOTE_INFO is not helpful as it's not distinguishing between shown parameter values in table cells and manually created notes (not) attached to models on the drawing), unwanted balloon types, unwanted balloon content, unwanted dimension text, update symbols from file, etc...When referring to https://support.ptc.com/help/creo/creo_pma/r10.0/usascii/index.html#page/model_analysis/modelcheck/Drawing_Mode_Checks.html then even regeneration errors, regeneration warnings, start parameters, parameters to rename et al. are not available in drawing mode with ModelCHECK.In essence, ModelCHECK should be able to help us report on all non-MBD like things in drawings in order to get on the good path of MBD.What are your thoughts about things that ModelCHECK should report in drawings?3. Are you using a workaround? If yes, please describe it.not really possible - how to get this type of information in a valid and efficient (non-manual) way?4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.Lots of information is hidden in drawing details and not explicitly available to turn into MBD based workflow. In order to turn to Model Based Definition, preventing doing the wrong things in drawings means less errors, more integrity of information (no drawing notes for example5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Not being able to decide based upon this missing information means more uncertainty in planning tasks and projects, and discovering lakes of problems hidden in drawing files which otherwise would have been sorted and prioritized according to valid data. In effect, that results in business processes being much longer and less stable than it would be if accurate information was used to execute. 

Modelcheck for a Drawing should catch errors where a view is missing a geometry referenceAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We design and manufacture high-end electronics. I am the CAD Manager / PTC SME. Stakeholders for this idea include our Creo user community. 2. What version of Creo Parametric are you currently running?8.0.6.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. Reference Ticket: 16620599  When running modelcheck regenerate on the drawing, the drawing is not updating to the extent where any lost orientation references of a general view are not in the message log. We can't use modelcheck to flag that as an error. Only when the drawing opens do we see in the message log:"Geometry needed to orient the general view "new_view_1", on sheet 1, is missing."We would want modelcheck to flag this, but we would need it in the message log first.It does work when there is a lost reference for a detailed view. For instance, the below message appears when running modelcheck:"The geometry which serves as the origin of the detailed view "A", on sheet 1, is missing."     If we run modelcheck regenerate WITH the model, the message goes appear. However, that would mean the model needs to get regenerated and modified. When working with Windchill, this isn't always the ideal scenario. We would like some way to check this without needing to run modelcheck with the model. 4. What is the use case for your organization?Sometimes an engineer might not understand what is happening to their view and end up redimensioning without the correct orientation. This will ensure the user is aware of the lost reference and will need to rereference. 5. What business value would your suggestion represent for your organization?Instead of recreating dimensions with an inaccurate orientation, they will be aware of the cause and fix the view first before recreating the dimensions. @lwestbrook 

Creo Illustrate - Options to manually type edit Renumber/Resequencing of calloutsAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo Illustrate 10.0.0.02. What is the problem?Options to manually type edit renumber/resequence of callouts from Renumbering/Resequencing options selection box (Sequence Number :). Current behavior is to select the callouts by clicking on the up/down arrows for every increase in number. So, when we have to renumber from 10 to 75, the arrow has to be clicked 65 times to get to that callout.3. Are you using a workaround? If yes, please describe it.We are using the existing functionality.4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.When the callouts have to be renumbered, the Illustrators has to iterate from the existing callout value to the new value through the up/down button in Sequence Number Text Box selection box. For ex. when we have to renumber from 10 to 75, the arrow has to be clicked 65 times to get to that callout.This is a huge time-consuming work, where Illustrator has to click as many times as the callout difference are.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)User affected: 70+ (All Production users)Approx: 140 hours per month.