Hi Olivier, you still need to obey the rules of the state machine. This means, if you want to execute an action "Set the change to successful", the change needs to be in a state before from where the transition to 'successful' is allowed of course. If you want to test this more easily, and to simulate some things, you can also enable in the sysconfig to manually set the change state (in the change edit screen). ITSM Change Management -> Frontend::Agent::ViewChangeEdit ITSMChange::Frontend::AgentITSMChangeEdit###ChangeState set to "Yes". But as Markus wrote before, usually the change state was meant to be set by conditions and actions. Best regards, Udo On 11.05.2010 12:41, osallou wrote:

I did try to add a condition: When all Workorder State is Closed, action = change Change State to Successfull. Though status is still the same.

Documentation do not precise how conditions are "executed", e.g. scheduled, or analysed on-the-fly when looking at Change.

Le 11/05/2010 11:19, Markus Esche a écrit :

...

Hi Oliver,

On 11.05.2010, at 10:54, osallou wrote:

...

I do not understand however how Change State is modified. State machine shows what are the possible transitions, but I do not see any way to change the status of the Change State. I made a try, and all my WorkOrders are in State Closed. However my Change State is still Requested, and no menu give me the possibility to change this...

You can and should use the Condition& Action functionality to modify parameters of Changes or Workorders. The Condition& Actions are available in the ChangeZoom dialog.

Regards, Markus

--

Markus Esche Customer Development

OTRS AG Europaring 4 94315 Straubing Deutschland

T: +49 (0) 9421 56818 0 F: +49 (0) 9421 56818 18 I: www.otrs.com/

Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.: DE256610065 Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann

NEU: OTRS::ITSM 2.0 - jetzt mit dem brandneuen Change Management Modul. -Die erste ITIL® V3 kompatible und nach PinkVERIFY zertifizierte Open Source IT Service Management (ITSM) Lösung weltweit! http://www.otrs.com/de/produkte/otrsitsm/

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/

Hi Arthur,

- I hope the complete logic can be saved in templates as well :-)

yes, a complete change including all workorders and conditions/actions can be saved as template.

- The approval WO's are a bit... uneasy. When I can already set the CAB, it would be cool if there was some mechanism to automagically request approval from each CAB member.

You can set up a notification based on events, such as "ChangeCABUpdate"..

- Use Ready or Accepted for the WOs?

The idea of the workorder states are documented in this overview image: http://doc.otrs.org/itsm/2.0/en/html/x1075.html But, of course, you can change the behavior of the workorder state machine.

- Not sure how I can do a successful close/failed/... depending on the PIR.

You could define a PIR workorder, and set up a condition that if this workorder is "closed" then the chage should be set to "successful", and if it is "canceld" the change should be "failed". Best regards, Udo