Solved

Recurring Service Program Default State of Scope and Request

Forum|Forum|2 months ago
December 11, 2025
3 replies
58 views

+6

tunstalltom
Sidekick (Customer)

Hi,

Unlike PM Actions in FSM when a Request is generated from an Recurring Service Program it is created into Status Released automatically.

Below I’ve created 4 scopes from an Recurring Service Program (Object Based). As you can see these Requests and Scopes have automatically been Released.

I do not want this to be the case I’d like to keep them in “New” status for them to be reviewed by a Scheduler (just like PM Actions). Is it possible to configure this behaviour (within the application) without a customisation?

Best answer by anmise

This is being tracked through the following idea.

P

+5

PubudikaW
Do Gooder (Employee)
Forum|Forum|6 days ago
March 4, 2026

Hello @tunstalltom,

Thank you for reaching out.

At the moment, this behavior cannot be configured within the application. However, we have received a few similar requests, and this enhancement is being considered for a future release.

Best Regards,

Pubudika

Like

T

+6

tunstalltom
Author
Sidekick (Customer)
Forum|Forum|6 days ago
March 4, 2026

Hello @tunstalltom,

Thank you for reaching out.

At the moment, this behavior cannot be configured within the application. However, we have received a few similar requests, and this enhancement is being considered for a future release.

Best Regards,

Pubudika

Yeah it would be good to have this functionality OOTB. We ended up doing a mod with a toggle on the RSP that allows a user to select whether or not to have it auto-release upon generation.

When this toggle is set to false. Our RSP Request Tasks, don’t automatically appear in the Dispatch Console which was a big problem for us. A user can prepare the job THEN release it to appear in the dispatch console for scheduling :)