Invoking long-lived process through API

Question

I am trying to invoke a long-lived process using web service API.
It doesn't create a task (workspace endpoint) as a initiation point. It directly moves on to the next task assignment activity.
Is this the default behavior ?
What's the harm?
It is not known to the next actor who initiated this task.
Any suggestions are welcome.
Nith

Answer 1

"It doesn't create a task (workspace endpoint) as a initiation point. It directly moves on to the next task assignment activity. Is this the default behavior ?"
Yes, this is the default behavior. As I'm sure you know, there are different ways you can initiate a process in LiveCycle: REST, Soap, Email, Workspace, etc.
If you use Workspace to initiate the process, we give you an interface to load a form and start the process with that data. If you decide to use the API, you need to provide the initial parameter through code.
In both cases you're just calling your process using different invocation methods. Once the process is invoked, it'll go to the first step in the process. This is the step with the small green arrow beside it.
It doesn't make sense to initate a process through the API, and then initiate it again in Workspace.
"It is not known to the next actor who initiated this task."
There's always a account under which the process in invoked. If  you use the API it'll use the account you specify in the connection properties.
Does that make sense?
Jasmin