You can create Global Resources which, instead of pointing to a static file, read a specific file produced by either a MapForce mapping or StyleVision transformation. In this case, the Altova application which consumes the Global Resource will first call either MapForce or StyleVision, run the corresponding mapping or transformation, and finally fetch the resulting file. This makes it possible to define data workflows between Altova applications (for example, pass the result of a MapForce mapping or StyleVision transformation as input to another mapping or transformation). For an example which illustrates how XMLSpy consumes the result (output) of a MapForce mapping using Global Resources, see Example: Create Application Workflow.
In order to make a mapping result (output) available as a Global Resource, either the transformation language of the mapping must be set to BUILT-IN, or the mapping must contain only components which are supported by the BUILT-IN language.
The workflows mentioned above are meaningful between Altova desktop applications installed on the same computer. It is not possible to consume the result of MapForce and StyleVision transformations as Global Resources in Altova server products and in MapForce Basic Edition.