Workflow Container Limiations & Design Considerations

[eneko.bilbao@accenture.com]

Hello All,

 

I'm looking for some design considerations and recommendation regarding
workflow. 

 

We have a client who is asking for very complicated workflows, (6-14+
steps!!) with a large amount of data stored in the workflow container.
The requirement is for each recipient to add approximately 1 page of
data, (comments, recommendations, reviews etc) to the workflow. At the
end of this workflow they would like all of this data posted to some
custom HR Infotypes. However, the client does not want to access and
process these "essays" in the GUI only in the UWL.

 

My questions are regarding technical limitations of SAP and possible
negative impacts of the above approach. 

 

Can the workflow container handle this amount of data? Would you
recommend storing this data in the container? If not, why not? Can the
UWL display this much data? What are some possible alternative
approaches we could recommend?

 

Any suggestions would be welcome.

 

Thank you.

 

Eneko Bilbao

Email: eneko.bilbao at accenture.com <mailto:eneko.bilbao at accenture.com> 

 



This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20071207/5093f9cf/attachment.htm