Hi,
I have a problem while implementing planning workflow in STS.
Let's imagine we have following approval hierarchy defined in STS
USER A
-
> USER B
-
> USER C
Mentioned users execute their planning in following order
1. USER C enters his plan and set STS status to Send for approval
2. USER B approves plan for USER C, enters his plan and sets status of his node to Send for approval.
3. USER A approves plan for USER B
After those 3 steps both plans of USER C and USER B are Approved and both userc B and C are not able to correct data (this is ok).
But USER B is able to change status of plan for USER C to "Back to Revision", or unlock the data for user C (even though his level of hiererchy shouldn't be changed, as it is already approved).
Is there any customizing that I could perform to prevent such action?
The only option I found is to perform modifications to BSP tunguska application (but I would like to avoid it, as it's related to changing SAP code)
Thanks in advance for help,
Best Regards,
Pawel
Edited by: Pawel Ogrodnik on Jun 30, 2009 4:59 PM