Skip to Content
author's profile photo Former Member
Former Member

ARQ: MSMP Workflow version Activation and Existing Requests' Fate???


Our current Workflow solution is working fine to cater the current business requirements. Now an addition is made to the MSMP workflow to address the "Default" roles. In this regard, routing rule is enabled at Manager level. This is successfully moved to Quality System and I generated the MSMP workflow version in Quality System. After that I tested the scenario and it worked as expected.

Now it is moved to Production system. Currently, there are multiple requests with "Pending" status in Production system. If I activate (generate) the MSMP workflow version, all the existing requests would become "Invalid" and cannot be processed because of MSMP version change!

May I have your valuable inputs to address this issue? I believe, I need to generate the MSMP workflow version to bring "Default" roles functionality in effect. What should be the reasonable solution to:

1. get current requests approved seamlessly?

2. get "Default" roles functionality introduced?

Please advise.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Sep 25, 2014 at 05:01 PM

    If you did not have the Runtime Config check OK checked, the existing workflows will continue as normal in the version that they were created in.

    Now, I will guess that Manager stage is the first stage in your path, any requests that are past that whether you allow them to move to the next version or not would not have any issue (as long as you still have role assignment owners on the role) should have no issues.

    The end users in either case, unless you have something strange in the follow on stages in your path, should not even be aware that something has happened. They might think its strange if you have let the Role Assignment approvers that you have dealt with these differently going forward after a specific date.

    You should be ok to move forward at a good cutoff (end of day) so that if an approver gets a request that is before a certain date, it may contain these default roles and requests created after that date would not.

    For the Default Roles functionality, you should be good to insert the master data in NWBC when you need to. You will only get the default roles for NEW requests that are created after the data has been created.

    Hope this helps.

    Kevin Tucholke

    Principal Consultant

    SAP America

    Message was edited by: Kevin Tucholke

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Kevin Tucholke

      Dear Kevin/Ameet,

      Let me share the interesting case with you.

      I followed as mentioned above: Moved the WF changes and then generated the new version of WF. I have "Runtime cnfg check ok" checked at all the stages.

      As per above discussion, I had understanding that old+new requests will be processed without any errors. Unfortunately, I noticed that old requests got failed!

      Whereas, new requests are getting processed successfully. I dont know why system is behaving like this

      May I know if I missed anything here?



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.