Relocate entity record to another assessment scheduler without deleting previous related assessment

[jkng]

Hi everyone,

I’m facing an issue with the Risk Assessment Scheduler and would appreciate some guidance.

I need to move an entity from one Risk Assessment Scheduler to another. Currently, an entity can only be associated with one scheduler at a time, so the only way I can do this is by removing the entity from the existing scheduler and then adding it to the new one.

However, when I remove/delete the entity from the current scheduler, all related risk assessments are also deleted, regardless of their state (in progress, completed, archived, etc.). This is a problem because those existing risk assessments need to be preserved.

My question is:

• Is there a supported way to relocate or reassign an entity to a different Risk Assessment Scheduler without deleting or impacting the existing risk assessments?

• Alternatively, is there a recommended best practice or configuration to handle this use case?

Any insights or suggestions would be greatly appreciated.

Thank you in advance!

[Matthew Green2]

• Is there a supported way to move an entity to another Risk Assessment Scheduler without deleting existing risk assessments?
  No. This is not supported out of the box and the deletion behavior is by design.

• Why are risk assessments deleted when the entity is removed?
  Because the entity–scheduler relationship is the parent record; removing it triggers a cascade delete of all related assessments, regardless of status.

• Recommended best practice?
  Do not remove entities once assessments exist. Instead, deactivate the old scheduler and create a new scheduler for future assessments (scheduler versioning)

• Any workaround?
  Only unsupported customizations or cloning entities—neither I recommend.

At the End of the Day: You cannot relocate an entity without impact; use scheduler versioning to preserve historical risk assessments.

[jkng]

Hi @Matthew Green2 ,

Thank you for the explanation.

I’d like to clarify on one point further — when you mention “scheduler versioning”, could you please elaborate on what that means?

Specifically:

• Does it mean setting the scheduler state to "Retire"? If so, I have tried and it did not work as it still does not enable me to add the entity to a new schedule.

• If it means something else, could you please elaborate on how does scheduler versioning work? For example, what is the way to deactivate an existing scheduler.

Thanks again for your guidance.

[Matthew Green2]

Thanks for the feedback. Just to confirm, when u say “scheduler versioning,” this does not mean setting the scheduler state to Retired per say. Retiring the scheduler stops future runs but does not allow the entity to be added to a new schedule (I’ve tested this before).

My understanding is that versioning means the scheduler becomes immutable once its used, and the intended approach is to create a new scheduler record and associate the entity with that, leaving the old one for history.

Please let me know if that’s correct.

Thanks my friend!