1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
Not disclosed information.
2. What version of Windchill are you currently running?
Windchill 11.1, CPS18
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
Here are the steps to reproduce:
We open a Change Object (Change Notice, Promotion Request, etc.), tasks are generated automatically (OK). They depend of a process (cf. table named "routing/process history"). This process is named after the inital name of the Change Object and so are the tasks (when we open them) (OK).
When we rename the Change Object (actions > modify), the name of the routing/process is not renamed neither the tasks (NOK). They keep the initial one.
Purposal: when renaming a Change Object, the current routing option and its related tasks should also be updated with the latest name.
4. What is the use case for your organization?
See above description.
5. What business value would your suggestion represent for your organization?
The main improvement would be the consistency of the information of change objects (on tasks and routing options). Some users might be confused to see tasks that are named after a previous naming of the related change object.
