Moving Processors (TYPE PROCESS) between Endevor environments
Article ID: 219693
Updated On:
Products
Issue/Introduction
Would like to implement a lifecycle for the Endevor ADMIN elements to match the lifecycle for standard development. The lifecycle will consist of a Development (coding), System, QA, Pre-Prod and finally Prod. The Prod stage will be where the customizations are active for all Development users. Under one or more of these intermediate stages we will be having an Endevor test environment.
The issue is that in this scenario is it possible to code the processors in the Development stage and migrate them to the next stage via package moves. This has been attempted with a processor and received an error that it is not allowed to move a Type PROCESS to another environment. Is there some way to allow processors to be moved through a lifecycle?
Environment
All Supported Releases
Resolution
Processors do not and cannot follow the same lifecycle as normal elements or ADMIN type elements. Processors can only exist in, at most, two separate stages.
The System Definition panel allows for two stages which can allow for testing of Processor changes:
PROCESSOR TRANSLATION OUTPUT LIBRARIES:
STAGE 1 LOAD LIBRARY: iprfx.iqual.stage1.PRCSLOAD
STAGE 1 LIST LIBRARY: iprfx.iqual.stage1.PRCSLIST
STAGE 2 LOAD LIBRARY: iprfx.iqual.stage2.PRCSLOAD
STAGE 2 LIST LIBRARY: iprfx.iqual.stage2.PRCSLIST
Additional Information
Feedback
