Testing an Endevor Processor in a production environment
search cancel

Testing an Endevor Processor in a production environment

book

Article ID: 252204

calendar_today

Updated On:

Products

Endevor

Issue/Introduction

Testing changes to Endevor Processor in the production Environment.

The TYPE and the processor group also must match what is used in production.

 Would like to do this without impacting users that use the existing processor.

Environment

Release : all

Resolution

Two ways to do this:

1)  Use IF statements to limit who/what is tested.

     For example you can test the element called TEST. Only test this element. Code this in your processor.

     //IF IF (&C1ELEMENT = TEST) THEN

     .....(changed code)

     //     ELSE

     .....(existing code that is currently used by users)

     //    ENDIF

2) Have a different processor that is stored based on different system name. Note Subsystem and Stage are not used with type process. If they are used then the most current processor with the same name/system is used.

Copy/compile the updated processor to a new TEST system name and test it there. Then you can copy it back when ready to go live.