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

processing can be rejected

I create a simple one step workflow with a decision step using task TS00008267. I turn on advance with dialog and processing can be rejected. Agent is initiator. When I test, it displays the decision and I can cancel it and then reject from inbox. Everything seems to work fine.

The problem is any time I go back into the decision step and then leave, it tells me it will delete the processing rejected outcome if I save the step. Even if I don't change anything, it still deletes the outcome path. If I cancel out, it will still work. If I save, it deletes the path and even though the checkbox for rejection is still checked, rejection from inbox isn't possible anymore. If I go back into the task and turn rejection off and then back on and save, it works again.

I've searched SAP notes and didn't see anything specific to this. I've tried it both our dev and sandbox environments and it does it both places. Any ideas?

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Jan 16, 2008 at 06:48 AM

    Sometimes weird behaviour is observed, and the only explanation is that something has gone completely wrong internally. What you could try is to add a new step to the workflow with the same definition, and see if the behaviour is the same. Or, I suppose it is even better if you use a sandbox to create a new workflow and define it in the same way.

    It's a long shot, but no-one else has suggested anything yet - perhaps they are still sleeping?

    Seing my great idea about the sandbox (😊 I decided to give it a shot myself. I observe the same behaviour. However, the Processing Rejected outcome is never visible in the "Outcomes" tab for the step, so that's why the workflow builder insists on deleting the branch - just as if you had removed another outcome.

    If you try a different standard task you will notice that "Processing rejected" will be added to the outcomes if you check the flag.

    The decision tasks are special in their behaviour - with outcomes decided by step input data, and therefore SAP must also have some special handling of them internally. I suppose they didn't foresee someone checking this flag for a decision task.

    A new OSS Message seems inevitable 😊

    Add a comment
    10|10000 characters needed characters exceeded

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.