reverting SAP STD Workflow from Modified to Original and more....

Mark Pyc mark.pyc at gmail.com
Tue Dec 4 14:14:54 EST 2007


G'day Praveen,

You can use version mgmt to restore the original. It'll still show as
repaired, but will be back to how it was.

There are some rare hardcoded cases where there is no mechanism to configure
which WF will be started (no events used, hardcode 'start wolkflow' logic
inside the application with a fixed TS or WS). In these cases one of the
choices is to repair the WF, the other is to repair the standard calling
code. Pros & cons either way.

In all other cases you should always take a copy of the WF and work on that,
no matter how simple the change. The flexibility of the event linkage
concept or application specific configuration means that taking a copy and
using it should be straight forward.

Have fun,
Mark

On 03/12/2007, Praveen johri <praveenjohri at gmail.com> wrote:
>
> Hi Guys,
> I feel probably this is not right forum to approach this issue but i am
> sure there are many intelligent people here who might have faced same issue.
> Here it is, someone has created a repair transport to affect a new rule
> for role resolution in one of the SAP Std Workflow. Now, Project wants it to
> be reverted to Original , copied to a 'Z' version and changes applied.
>
> We are on test stage of the project and on ECC6
>
> 1) how can we do that? ( my guess ...SPAU...but that can only be used when
> applying packs )
>
> 2) As a policy, will changing the role resolution  in Std Workflow will
> come into the category of 'Repair' apart from the fact it creates a repair
> transport,  just want to know how others approach this small change which i
> m sure is needed everywhere.
>
> --
> Have Fun!!
> Praveen Johri
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20071204/dae13331/attachment.htm


More information about the SAP-WUG mailing list