|
Application Model (in practice with Workbench 9.0 and latter
versions) allows multiple process developers to share assets across
applications. It also allows securitization of confidential assets
and applications shared on a AEM forms Server for restricted usage.
Legacy artifacts (AEM forms assets) that exist as Resources (processes,
forms, form fragments, images, ddx files, etc.)in the upgraded environment
can be extracted and bundled in to a single container called Application.
Applications can be versioned. This means that the resources do
not have versions of their own and they inherit the versions of
their application containers. Application version numbers are uneditable,
meaning the version numbers do not change even if they are migrated
across servers or development environments.
When the AEM forms environment is upgraded to AEM forms, the
properties of legacy processes, resources, and events are unchanged.
For example, if a process was locked before the upgrade in Workspace,
the process appears with a lock icon on it after the upgrade. Consider
unlocking all processes, resources and event types before you import
them to AEM forms. In Workbench, you cannot lock/unlock processes.
The following summary describes what occurs to an upgraded legacy
asset:
-
Processes and process versions:
-
Remain in the Processes view. Lock, activation, and recording
properties remain unchanged.
-
Resources:
-
Remain in the Resources view. Resource locks remain unchanged.
-
Event types:
-
Remain in the Events view. Locks and activation properties
remain unchanged.
After you upgrade, check-in and deploy the
process, process version, resource, or event to remove the lock
property.
The run-time instances of legacy processes, resources,
and event types continue to execute in the AEM forms environment.
References between processes, resources, and events are persisted:
Additionally, service endpoints remain
unchanged. Processes can be invoked using the same endpoints that
existed in the AEM forms environment.
In Workbench, interaction
with items in the Processes, Resources, and Events view is limited.
Many features and commands have moved from these views to the new
Applications view. For example, you cannot open resources for editing or
viewing from the Resources view.
Review the AEM forms run-time environment:
Open the following
perspectives and views:
-
AEM forms Runtime View perspective
(includes the Applications, Resources, Services, and Events views)
-
Processes view
|
|
|
