Early Archiving + IXOS

[Becker Stephan (extern)]

Just to clarify the second paragraph, attributes are read from the internal
buffer until the object is either explicitely refreshed (macro
swc_refresh_object self, for example invoked in a separate method), or newly
instantiated. So in order to catch all new assignments of scanned documents,
you would need to refresh the object just before each dialog step, and that
would then not cover cases where an attachment is added between workitem
creation and its completion.
Stephan
 
-----Original Message-----
From: Susan R. Keohan [mailto:skeohan at mit.edu]
Sent: Mittwoch, 13. Februar 2002 16:06
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Fwd: RE: Early Archiving + IXOS
 
 
Forwarded on behalf of Felix Hassine (Fhassine at pmiancam.com)...
 
Lola,
 
You are totally in the right direction. Create an attribute to your FIPP
document , that you can name "Images", state it as a multiline attribute (by
experience, there are plenty of cases when more that 1 document is archived
against a document, this is why it should be mulltiline), and build your
attribute by calling 'ARCHIV_GET_CONNECTIONS', followed by a statement
"swc_create_object' image 'IMAGE' <KEY>.
That way you can access easily from within the workflow all of the scanned
images.
 
This method offers the advantage to be more dynamic than just assigning a
container value in the workflow to the IMAGE object(s), since the attribute
is re-calculated by the WIM every time the object is invoked. So if a
workflow instance runs, and someone "adds" another scanned invoice to the
pile of scanned documents assigned to your FIPP document, your workflow
"sees" immediatly the new additional one.
 
Another pitfall you must consider is if someone posts a FIPP without
scanning first the invoice...(don't say never...users are sometimes very
creative !). You should consider either to create a "blank" document in the
system, either return an exit_object_not_found.... but then you need to test
your attribute every time you invoke it, this is heavy.
 
Hope this helps, best regards,
 
F. Hassine
 
-----Original Message-----
From: Lola Oluwa [mailto:Lola.Oluwa at outokumpu.net]
Sent: Wednesday, February 13, 2002 1:40 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Early Archiving + IXOS
 
 
Hi!
I have defined an early archiving scenario as follows:
1. A workflow multistep task is inatiated when the document is "moved" into
R/3.
2. The final step is document parking. The event  'parked' (own event)
triggers another multistep task.
 
Question: The 'IMAGE' object is passed to the first task. How do I retrieve
this object for my next mutistep task. I have looked at finding the link
created using: FUNCTION 'ARCHIV_GET_CONNECTIONS'  am I going in the right
direction.....(Is the link already created at the parked stage??)
 
Any help will be much appreciated.
 
 
Thanks in advance.
 
Lola.
 
----- End forwarded message -----
 
 
 
 
----------------------------------------------------------------
This mail sent using MIT WebMail. See http://web.mit.edu/webmail