Non Persistence and Death

PointsWell

I'm looking at Non Persisted BOs as an alternative to writing all my variables to the LoggedInRegularUser and instead using a (or more than one) Non Persisted BO

My question is at what point does a Non Persisted BO get extinguished?

I was aiming to use it to keep multiple panels on a VP in sync, but there will be other operations that happen between setting the BO and its reuse.

Is this a sensible or stoopid way to go?

customaware

A NP BO only lasts as long as the Context in which it was created Sean.

I very much doubt you will find any joy with what you are trying to do using NP BOs.

Use LoggedInRegularUser

PointsWell

eagles9999 wrote
A NP BO only lasts as long as the Context in which it was created Sean.

I very much doubt you will find any joy with what you are trying to do using NP BOs.

Use LoggedInRegularUser

Thanks

johntalbott

I'm not sure if this is exactly what you are looking for, but I have used a NP BO to pass variables between processes.

PointsWell

johntalbott wrote
I'm not sure if this is exactly what you are looking for, but I have used a NP BO to pass variables between processes.

I can see how that would work as it is being passed along the chain of process so presumably doesn't ever come out of the context.

I was looking at it to set a search element in a series of Queries which may or may not have other processes working in between. It doesn't sound appropriate for what I am trying to do so I am just going to go ahead with the LoggedInRegularUser BO and jut try to monitor how many BOs I am putting in there.