Skip to main content
Question

FSM - task dependency - only when task belong to the same request scope

  • January 13, 2026
  • 3 replies
  • 41 views

Marcel.Ausan
Ultimate Hero (Partner)
Forum|alt.badge.img+22

@Alexander Heinze maybe you can help here.

Is there any reason why we cannot have task dependencies between tasks that below to different request scopes?

Goal: Enable combined planning of multiple recurring tasks over different services​

Example Use Case: Maintenance and Safety Check for the same equipment due at the same time → Technician should complete both in one visit. Tasks belong to different Request Scopes/Services.

 

I’m very tempted of commenting the error message but I’m not sure what the implications would be 😁.

Excerpt from JT_TASK_DEPENDENCY:

 

Any hints would be very welcomed!

3 replies

  • Superhero (Employee)
  • January 13, 2026

@Marcel.Ausan there’s no particular reason we blocked this, other than that we haven’t gotten around to implementing it properly yet - and thus blocked it to avoid unintended behavior. We do have plans to remove these restrictions in a future release and provide some clients to create dependencies across scopes. 

Where you may run into problems is with transfer to mobile, scheduling/dispatch console, but for the most part, all of those don’t care about the parent, so it feels fairly safe to try.


Marcel.Ausan
Ultimate Hero (Partner)
Forum|alt.badge.img+22
  • Author
  • Ultimate Hero (Partner)
  • January 14, 2026

Thanks ​@anmise . Any idea what ‘future release’ means in this case? Is it worth waiting for 26.1? Or will it be further away?


  • Superhero (Employee)
  • January 16, 2026

Thanks ​@anmise . Any idea what ‘future release’ means in this case? Is it worth waiting for 26.1? Or will it be further away?

If you can hold out for a few weeks, I’ll know more. There’s a slight chance it’ll be in 26R1.