Masuk
 
AwalPerpustakaanWikiPelajariUnduhDukunganKomunitasForum
Resources for IT Professionals >
> 
> 
Unable to delete activities from existing Change Requests after upgrade to SM12

Jawab Unable to delete activities from existing Change Requests after upgrade to SM12

  • 02 Mei 2012 10:08
     
     
    Masuk untuk Memilih
    0

    Hi,

    we are facing the following problem:

    We have upgraded SM12 at one of out customers and now we are unable to delete activities from existing change requests. Within a new CR this is no problem. Also we can add new activities to the existing CRs and can delete them if we want. The red cross to delete is disabled for existing activities. Those activities have the status "Pending" so it should not be a problem to delete them.

    Anyone seeing similar issues after SM12 upgrade?

    Thanks!

    Peter Forster | MVP Virtual Machine 2002-2011 | Austria | German System Center Blog: www.systemcenterblog.at

     

Semua Balasan

  • 02 Mei 2012 14:07
     
     Saran Jawaban
    Masuk untuk Memilih
    0

    Hi Peter,

    I can confirm that this behavior can also be observed in our SCSM installations. I believe it has been a design decision in SCSM 2012 to not allow the deletion of activities once they are in pending status. Anybody can confirm this? But please note that, instead of deleting activities, you can now skip them (right-click, skip activity).

    HTH,
    Dieter

     
  • 02 Mei 2012 14:39
     
     Saran Jawaban
    Masuk untuk Memilih
    1

    I can confirm it, same thing in our environment.

    Regarding "skipping" an activity, please be aware that a skipped activity will actually go "In Progress", then another workflow sets it to "Skipped". This can cause unexpected behavior if you have workflows or runbook activities that trigger on an activity going in progress. (In other words, you may expect an activity to be skipped, but your workflow will still trigger)

    The only way I have found to truly skip an activity is to explicitly set its status property to "Skipped". But I don't think you can do this through the console. In the console, when you right-click and "skip activity", it sets the boolean property "Skip" to true. After the activity goes in progress, I believe another workflow sees that "Skip" activity is set to true, then sets the activity status to "Skipped". From that point on, the activity will truly be skipped..for instance, if you return to an activity before the skipped activity, then complete it, you'll notice that the skipped activity really will be skipped.

     
  • 03 Mei 2012 7:28
     
     
    Masuk untuk Memilih
    0

    Hi,

    thanks for the discussion - we are fine with the "skip activity" option - just wanted to make sure that this is the default behaviour.

    Peter Forster | MVP Virtual Machine 2002-2011 | Austria | German System Center Blog: www.systemcenterblog.at

     
  • 14 Juni 2012 6:56
     
     Jawab
    Masuk untuk Memilih
    0

    Hi,

    as we needed a solution for that I've openend a support case with PSS. The outcome was:

    Currently the permission to skip an activity is associated with the "Administrator" and "Release Manager" Role within SCSM. In our case we have created a new Release Manager Role without any further permission within release management and added the necessary users. Works like a charm. A DCR for adding the "Skip Activity" permission for selection within other user roles was created.

    Peter Forster | MVP Virtual Machine 2002-2011 | Austria | German System Center Blog: www.systemcenterblog.at

    • Ditandai sebagai Jawaban oleh Peter Forster 14 Juni 2012 6:56
    •