Change Script-Steps to Steps that can be Scripts or provided Java-Classes

Description

At the moment script steps can be applied to the requisition before it's returned to the user. This script steps have to be bsf compatible scripts. Having the option to add predefined steps based on java-classes would reduce the amount of customization and provide a simple mechanism for basic manipulations on the requisitions.

how should the config look like?
It has to be possible to provide parameters for steps. If a step is used multiple times, different parameters have to be configurable.

pc.1 = scriptname
pc,1,parameter = value
C-v R j 9
pc = f:foo x:foo z:print
pc.f.mode = killer
pc.x.false = true

or

pc = script(param = value) \ script2(param = val) \ pc = script(file = a/b/c, \ file2 = d/e/f, \ file3 = x/y/z)

Lucidchart Diagrams

Activity

Markus Neumann March 17, 2014 at 9:28 AM

Change is bitter as expected due to the configuration requirements. Moved to 2.0

Details

Assignee

Reporter

Components

Sprint

Affects versions

Priority

PagerDuty

Created March 12, 2014 at 9:31 AM
Updated May 25, 2023 at 12:05 PM

Flag notifications