Answers to: Is there any possible way to switch SYSTEM session to another regular user's session in a ProgramStart execution?

Comment by Reto Weiss on haissam's answer

Reto Weiss — Wed, 20 Jun 2018 02:29:54 -0400

In case maps you use normal RequestStart process elements. This topic here talks about a ProgramStart. In a RequestStart you will not be able to get a runtime. This is something that is unique to ProgramStart. What is your use case?

Comment by Genzer Hawker on Reto Weiss's answer

Genzer Hawker — Fri, 27 May 2016 13:16:53 -0400

As of now, we don't have any. But it could be the case that we will introduce an on-demand feature to trigger the same background job. A Signal would be broadcasted to run the process in additional to the existing EventBean.

Comment by Reto Weiss on Reto Weiss's answer

Reto Weiss — Fri, 27 May 2016 10:11:46 -0400

It's not planned for Signals yet. If there is a concrete common use case we can provide support for it in a future version.

Comment by Genzer Hawker on Reto Weiss's answer

Genzer Hawker — Fri, 27 May 2016 10:07:12 -0400

Oooh, I didn't know about this. Guess I need to read more the API then. Will there be support for such use case in Signals? Thanks!

Answer by Reto Weiss

Reto Weiss — Fri, 27 May 2016 08:56:14 -0400

In a ProgramStart you can program which Session should be used to execute the process in the EventBean. The method fireProcessStartEventRequest of the IProcessStartEventBeanRuntime interface takes as first parameter an ISession. The process will be executed in the context of this session. Most EventBean implementors simply give a null value for this Session. In this case the process is executed in the context of the SYSTEM session. To use another session do as follows:

ISession session = runtime.createSession();
try
{
  runtime.fireProcessStartEventRequest(session, ...);
}
finally
{
  runtime.destroySession(session);
}

The method createSession will create an annonymous session. There is also another createSession method that takes two arguments so that you can specify a user and password to create a session with a user. Don't forget to destroy the session otherwise you have a session leak.

For Signals there is no such solution available yet.