[AMORO-3172] AMS ProcessStatus Miss Running Status

[czy006]

Why are the changes needed?

Close #3172.

Brief change log

• Add Running Status in ProcessStatus

How was this patch tested?

• Add some test cases that check the changes thoroughly including negative and positive cases if possible

• Add screenshots for manual tests if appropriate

• Run test locally before making a pull request

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (not documented)

[tcodehuber]

Is there some conflict between Active and RUNNING status?

[czy006]

Is there some conflict between Active and RUNNING status?

Can use Running Replace Active ? cc @majin1102

[majin1102]

Is there some conflict between Active and RUNNING status?

Can use Running Replace Active ? cc @majin1102

Hi, thanks for pointing this out.

This is an unreasonable reference to ProcessStatus(this belongs to process api which has not been used), the original ref is OptimizingProcess.Status.
I guess this error is introduced when refactoring ams-common module, OptimizingProcess.Status is hard to be pulled out to common thus used ProcessStatus.

Anyway I suggest to add RUNNING and QUEUEING to take place of ACTIVE. QUEUEING means pending external process(submitted but not running)

[majin1102]

I left one comment, PTAL

[majin1102]

LGTM

[tcodehuber]

LGTM