OO instance in container of workflow

[Florin Wach]

Hello Simon,

other attributes than the object identifier, represented by the structure SIBFLPOR(B), are not part of the persistence.

Everything you need to have persistent, needs to be stored in the database (by yourself). Updating an object's member attribute (by making it "public" and "writeable") will last only for the duration of the process. When you look at the container again, in a separate session, your instance will be created again, using the object identifier.

Two avoid unintenational changes, I would recommend to make all member attributes, which are public, "read-only" and provide setter-methods to offer other implementation to change the value. Within these setter methods, e.g.  set_company_code(),  you log your changes and hook in a functionality, that triggers on a database commit your changes along with that into a custom table.


With the very best wishes,
   Florin



-------- Original-Nachricht --------
> Datum: Mon, 8 Oct 2012 12:51:02 +0000
> Von: "Simon, Tom" <Simon.Tom at aoins.com>
> An: "\'sap-wug at mit.edu\'" <sap-wug at mit.edu>
> Betreff: OO instance in container of workflow

> I have a question regarding the wf container and an object instance that
> is stored in the element of the work flow container.
> After the object is instantiated and I update an attribute in the instance
> I noticed that it is not stored in the attribute field of the wf
> container.  The key field is transported back to the container and stored in the
> instance object element but not the other instance attribute that I updated in
> a task.  When I call this instance in a downstream task, the attribute is
> used to complete the task.
> It is not apparent to me where the object instance is stored.  I expected
> to see the attribute in the "persistant" container of the workflow.
> Can someone explain why the attribute is not available to be viewed in the
> wf element object.
> 
> Tom Simon,  CPCU
> Systems Analyst
> Financial Systems
> Ext. 1442
>