Answers to: Differences of public api

Comment by Flavio Sadeghi on Flavio Sadeghi's answer

Flavio Sadeghi — Tue, 10 Jan 2017 11:18:50 -0500

hi @trungdv. I have copied you last question into a new one and edited it, as I have understood the question. Feel free to commet it if I have misunderstood it. See here: http://answers.axonivy.com/questions/2364/how-is-the-handling-when-loading-business-data-in-different-pmvs

Comment by trungdv on Flavio Sadeghi's answer

trungdv — Tue, 10 Jan 2017 10:23:57 -0500

hi @Flavio Sadeghi ♦♦ Continuous with PMV, i have a case as below:

In my app, we store the task in two places, when creating task, for the main data model, we store in our persistence (BusinessReposiroty) and we take out the id from there then store to Ivy Task.

Q1: When user open task, we have that id then load business data from Repository. this case will work.i guess it will load with classLoader of pmv which the task belong to. is it correct?

Q2: for the case we have that id then load directly data model from repo(not start from task), it could be an issue? any way to avoid it?

Thanks

Comment by Flavio Sadeghi on Flavio Sadeghi's answer

Flavio Sadeghi — Mon, 09 Jan 2017 14:05:00 -0500

hi @trungdv

The deployment wizard decides on the basis of the project version (IvyProject -> Definitions -> Deployment -> Project Version) if a new PMV has to be created or an already existing PMV can be used. And yes, there were some fixes since 6.3...

Comment by trungdv on Flavio Sadeghi's answer

trungdv — Fri, 06 Jan 2017 02:31:46 -0500

hi @Flavio Sadeghi ♦♦

thanks a lot.

I just realize that somehow is a problem of deployment wizard tool, when i use it to deploy, it always deploy latest version on PMV1 (even i select PMV2 as the target). that's why i see the new logic on old cases.

So when i try with Deploy button on each PMV, it work as you said. I'm using version 6.3.0, don't know whether this is an issue or not.

Comment by Flavio Sadeghi on Flavio Sadeghi's answer

Flavio Sadeghi — Thu, 05 Jan 2017 09:51:22 -0500

Hello @trungdv

How do you start a case/task of PMV1 from PMV2? I would argue that the the case/task is started in PMV1 and that classes of PMV2 are not visible in PMV1, since this would lead to conflicts, because classes exist in both PMVs, at least the class of the process itself... (except you have some application-wide caching , which is not allowed in such use cases)

If it should be possible, I would classify this as an bug. Of course, I would be happy for the test projecte to verify the behaviour.

Comment by trungdv on Flavio Sadeghi's answer

trungdv — Thu, 05 Jan 2017 05:50:41 -0500

hi @Flavio Sadeghi ♦♦

Yes, i have another question, as you said "Case/Task lives always in the PMV the Case was started in". so for example i have a project A then i deploy it to PMV 1, i create some cases/tasks on this version.

Then i change implementation of Project A (i keep all task elements, just implement some new java class, new api, new logic). Now i deploy project A to PMV 2 (new version) and make it Active and Released.

Question: What happen if i start cases/task of PMV1 from released PMV (version 2)? which classes will be loaded?

I have some small test and i saw the old task will run on released PMV (PMV2), is it correct?

Thanks

Answer by Flavio Sadeghi

Flavio Sadeghi — Fri, 30 Dec 2016 12:55:25 -0500

First we have to separate between configuration and runtime data:

Configuration data are in the system database stored data, like Applications, Cases, Tasks, Users, etc.
Runtime data are not persistent and exists only at runtime, like the requests or sessions.

All API calls on the Ivy-Bean returns either configuration or runtime data related to the current execution context. E.g. the current executing request or the task of the current execution process.

The following APIs return runtime objects:

Ivy.request() Returns the current execution IProcessModelVersionRequest
Ivy.session() Returns the related IWorkflowSession to the current request

The following APIs return configuration objects:

Ivy.wf() Returns the IWorkflowContext of the current execution Application.
Ivy.wfTask() Returns the ITask of the current process
Ivy.wfCase() Returns the ICase of the current process

Further calls on a configuration object returns always further configuration objects:

ITask.getCase() Returns the ICase the ITask belongs to
ICase.getProcessModelVersion() Returns the IProcessModelVersion the ICase belongs to
ITask.getProcessModelVersion() Is equivalent to ITask.getCase().getProcessModelVersion()
ITask.getProcessModel() is quivalent to ITask.getCase().getProcessModelVersion().getProcessModel(). Basically each ITask belongs to a ICase, ICase belongs to a IProcessModelVersion, A PMV belongs to a IProcessModel and PM belongs to a IApplication. So the following two API calls are equicalent
Ivy.wfCase().getApplication().getProcessModels() returns all Process Models of the Application the current Case belongs to. As well as the call Ivy.wfTask().getApplication().getProcessModels(). Because a task and a case belongs to the same pmv, pm and application.
IProcessModelVersionRequest.getProcessModelVersion() Returns the IProcessModelVersion the IProcessModelVersionRequest belongs to
Ivy.request().getProcessModel().getReleasedProcessModelVersion(): The current IProcessModelVersionRequestbelongs to a Process Model, this process Model has one single ‘released’ Process Model Version. This is returned here and this has not to be the same as ivy.request.getProcessModelVersion(), because a Case/Task lives always in the PMV the Case was started in. Etc.

Hope this information will help. Don't hesitate to ask further question as comment. I will update the answer.

Comment by trungdv on trungdv's question

trungdv — Fri, 30 Dec 2016 10:13:45 -0500

Yes, thanks. Actually i can create test and check for myself but can't do fo everyone. They need a clear documentation. This post here for them. They dont need to ask around everytime they use it. :)

Comment by Flavio Sadeghi on trungdv's question

Flavio Sadeghi — Thu, 29 Dec 2016 14:34:23 -0500

Yes and no. If you do not understand it, I think we have to update the java-doc...

Comment by Genzer Hawker on trungdv's question

Genzer Hawker — Thu, 29 Dec 2016 12:09:41 -0500

We can write some small test processes to check it right? :D