Document attachments

MacPherson, Graeme (AU - Melbourne) gmacpherson at dc.com
Mon Oct 9 21:09:15 EDT 2000


Hi Sarah
 
As you have discovered, workflow attachments and SOFM attachments are
totally different (and not compatible).
 
As a result of this, I dont think that an office message is going to work
for you here(I presume you are trying to use SELFITEM.SENDTASKDESCRIPTION).
Depending on your situation, you might be able to get away with using a work
item though. If you replace the "send message" task with a task based on
WF_DOC.Display (or SELFITEM.Note_Display) instead and use your "Select agent
for subsequent step" method it might work.
 
Just an additional comment. This may be stating the obvious but the "Select
agent for subsequent step" does not work with background tasks like "Send
message" tasks (based on SELFITEM.SENDTASKDESCRIPTION) which are typically
executed in background. The subsequent step must be a type W work item and
you have to take the resulting container element of "select agent for
subsequent step" and make this container element the agent of the subsequent
step (agent type = expression).
 
Hope this helps,
Regards
 
Graeme MacPherson
Senior Consultant
Deloitte Consulting, Melbourne
Ph +613 9832 7000
 
 
-----Original Message-----
From: Rankin, Andrew AJ [mailto:Rankin.Andrew.AJ at bhp.com]
Sent: Friday, 6 October 2000 10:03
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Document attachments
 
 
Sarah,
        Try putting the Document Attachment into the AdHoc Attachment
Container Element.
 
Regards,
Andrew Rankin
 
-----Original Message-----
From: Jackson, Sarah A [mailto:Sarah.Jackson at let-it-be-thus.com]
Sent: Thursday, 5 October 2000 23:52
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Document attachments
 
 
I'm sure there is a very easy solution to this one, but sadly it is evading
me at the moment! We need to send a form to one recipient, who will then
complete it and forward it on to a number of other users.  It seems to make
sense for the first step to be a 'create document from template' step, which
can then be filled in by the first user. After that, i want that user to be
able to select agents for the subsequent step, which could be a mail
notification with the document attached, however, I can get as far as having
the first user amending and saving the form, but can't work out how to get
the completed form mailed to other users. I have included the select agents
of subsequent steps task, with the subsequent task being a send mail step,
however, I think I need to somehow put the newly amended form in the
bindings for the send mail step. When i try to put &WF_DOCUMENT_0001& in the
binding against ATTACHMENTS, it complains that it belongs to object type
WF_DOC and not SOFM...
 
Thanks,
 
Sarah
________________________________________________
Get your own "800" number - Free
Free voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
 
 
---- On    , Jackson, Sarah A (Sarah.Jackson at let-it-be-
thus.com) wrote:
 
> Hi,
>
> I am working with version 46b and am working on a workflow to
do the
> following - when an external applicant is created and a
reference
> employee
> is available, a mail notification should be sent to that
reference
> employee.
> The object type 'applicant' did not contain the attributes
reference
> employee available or reference employee, therefore I have
created a
> subtype
> and assigned those attributes to it. This all seems to be
working fine.
> In
> the workflow, the first step is a condition step that says if
applicant
> is
> external and reference employee is available, send mail
notification.
> (if
> Applicant.Internal External = 'AP' and Applicant.Reference
Available =
> 'X',
> send mail) If false, workflow ends. I have set up the
condition, but
> when I
> try to test the workflow, the condition step always returns
the value
> false
> and terminates immediately. I have created a number of
applicants who
> are
> external and do have reference employees yet still get return
value
> false. I
> have tried testing the condition step with just the applicant
number as
> the
> condition, and then using that applicant, yet still get the
value false.
> Any
> ideas on this would be greatly appreciated!
>
> Thanks in advance,
>
> Sarah Jackson
>
>
 
EOM
 
NOTICE - This message contains information intended only for the use of the
addressee named above.  It may also be confidential and/or privileged.  If
you are not the intended recipient of this message you are hereby notified
that you must not disseminate, copy or take any action in reliance on it.
If you have received this message in error please notify postmaster at bhp.com.
 


More information about the SAP-WUG mailing list