Archiving decision tasks

[Michael Pokraka]

The log does, but not once it's been archived. The outcome is stored in a container element which is not archived.
Personally, I think the archiving setup is still a little iffy - the container is after all one of the basic constructs of a workflow....
 
Thanks for the feedback though..
Cheers
Mike
 
On Wed, Apr 16, 2003 at 07:40:23AM +0200, Kjetil Kilhavn wrote:
> For the purpose described, wouldn't this also be solved if you named all
> the possible (activated) outcomes?
> The workflow log includes the names of outcomes.
> --
> Kjetil Kilhavn
>
>
>
>
>
>                     "Soady, Phil"
>                     <phil.soady at sap.com>        To:     SAP-WUG at MITVMA.MIT.EDU
>                     Sent by: SAP                cc:     (bcc: Kjetil Kilhavn)
>                     Workflow                    Subject:     Re: Archiving decision tasks
>                     <Owner-SAP-WUG at MITVM
>                     A.MIT.EDU>
>
>
>                     16.04.2003 01:19
>                     Please respond to
>                     "SAP Workflow Users'
>                     Group"
>
>
>
>
>
>
> Some ideas...
> WorkflowInfoSystem with the user exit to record your container element with
> the decision outcome.
>
> Alternative to make the log more readable.
> Dummy - Empty background task , with task description "APPROVED BY &VAR&"
> Extra WIs but the log is easier to read.
>
>
>
> Phil Soady
> Senior Consultant
> Business Technologies
> SAP Australia
> * : 0412 213 079
> * : phil.soady at sap.com
>
>
>
>
>
> -----Original Message-----
>> From: Michael Pokraka [mailto:workflow at quirky.me.uk]
> Sent: Tuesday, April 15, 2003 11:48 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Archiving decision tasks
>
>
> Hi folks,
> I think I know the answer to this myself, but...
>
> As I understand, the workflow container is dustbinned during archiving,
> never to return. Thus any decision outcomes (= container elements) are also
> lost, and the only way to retrieve any audit info for an approval is by
> looking at subsequent steps. That means that an approval without subsequent
> steps won't have a result if we need to see it from the archive (some of
> the flows in question look very confusing when there are change events wich
> cancel and trigger a new flow - archives are a complete nightmare by the
> looks of things!)
>
> Am I correct or am I missing something?
>
> Thanks
> Cheers
> Mike
>
>
>
>
>
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL and is
> intended for the addressee only. Any unauthorised use, dissemination of the
> information or copying of this message is prohibited. If you are not the
> addressee, please notify the sender immediately by return e-mail and delete
> this message.
> Thank you.