You can do this in the <transitions></transitions> in each state. Here the documentation about this. Follow : Classes > Class > Lifecycle > States > State > Transitions > Transition > Flags > Attribute.
Romain
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Romain,
After a long time, I'm having trouble arranging the fields on the transition form again. I also tried the way you suggested but it didn't work.
Here is my code:
<classes>
<class id="user-content-UserRequest">
<lifecycle>
<states>
<state id="user-content-assigned">
<transitions>
<transition id="user-content-ev_resolved">
<target>resoved<target>
<flags>
<attribute id="user-content-service_id"></attribute>
<attribute id="user-content-servicesubcatelogy_id"></attribute>
<attribute id="user-content-solution"></attribute>
</flags>
</target></target></transition>
</transitions>
</state>
</states>
</lifecycle>
</class>
</classes>
Thanks,
Edward
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How to reorder fields in Form Stimulus when changing status?
Who can help me? pls!
Hello Edward,
You can do this in the
<transitions></transitions>
in each state.Here the documentation about this. Follow : Classes > Class > Lifecycle > States > State > Transitions > Transition > Flags > Attribute.
Romain
Hi Romain,
Thanks you so much!
I have tried it. But is it still the same and nothing has changed?
Last edit: Edward 2021-06-18
Hello Romain,
After a long time, I'm having trouble arranging the fields on the transition form again. I also tried the way you suggested but it didn't work.
Here is my code:
<classes>
<class id="user-content-UserRequest">
<lifecycle>
<states>
<state id="user-content-assigned">
<transitions>
<transition id="user-content-ev_resolved">
<target>resoved<target>
<flags>
<attribute id="user-content-service_id"></attribute>
<attribute id="user-content-servicesubcatelogy_id"></attribute>
<attribute id="user-content-solution"></attribute>
</flags>
</target></target></transition>
</transitions>
</state>
</states>
</lifecycle>
</class>
</classes>
Thanks,
Edward
That's a known limitation of iTop, in the console, transition form cannot be defined, it is auto-computed and order is wierd
Thank you for the quick response. If it was sorted it could be more perfect.
iTop is open source and we are open to contributions :)
See Contributing to iTop