Resolution:
Scenario
--------
We are using the Call Process activity in BW palette for our project.  It uses the Dynamic
Process Override option wherein we can specify the XPath to call the appropriate
process at runtime based on certain conditions.


Issue
------

We are facing the following issue during deployment.

When the project ear (Enterprise Archive) is created, the processes are added based
on the starter.  Hence it will add only those sub-process which it is linked to.  But the
process which are specified on dynamic process override option are not added
automatically.

Explanation and Action
----------

This is an expected behaviour, The sub-processes which could be called dynamically
should be added in the "Shared Archive" manually in the Enterprise Archive before
building the ear.
>>>>


This fact is described in a few places in the documentation. If you open the
HTML doc and query for the word "dynamic" and "dynamically" you'll see a few
places where this is mentioned.

In particular, this is mentioned in the Call Process page in the Palette Reference
in a section named "Dynamically Determining the Process to Call" At the end of
the section, you can see the following note:

"
If you use the Process Name Dynamic Override field, make sure you include all
potentially callable subprocesses when you create your Process Archive for
deployment. TIBCO Designer cannot determine which subprocesses are
potentially callable at design time, and therefore they cannot be automatically
included in a process archive."

This is also described in the section about building a process archive in TIBCO
BusinessWorks Administration. That section states that you shouldn't manually
add processes that aren't dynamically called (implying that you should add
processes that ARE dynamically called.. and refers to the Palette Ref for more
information).

Keywords:- dynamic, subprocess, call process