SC task closed incompletd

[Nigonda]

In the ServiceNow brownfield instance their is one catalog name as staff departure request when the RITM is raised for that catalog item their is 11 SC task is going to create at a same time. Suppose for one SC task no 1 I updated state as closed incomplete that time remaining 10 task state also update as closed incomplete. and in the activity for task 1 showing as updated the user name and remaining also show as same name as who updated. In brownfield for this catalog using as workflow and instance is Zurich version.
This same functionality we replicate in our greenfield instance with same catalog item and In greenfield we used the flow designer.
In the greenfield the RITM is raised for that catalog item their is 11 SC task is going to create at a same time. Suppose for one SC task no 1 I updated state as closed incomplete that time remaining 10 task state also update as closed incomplete. and in the activity for task 1 showing as updated the user name and remaining is showing as in activity system. here the instance is Australia version.
But the client want's the sc task state same brownfield  Suppose for one SC task no 1 I updated state as closed incomplete that time remaining 10 task state also update as closed incomplete. and in the activity for task 1 showing as updated the user name and remaining also show as same name as who updated.
Please help on this to fix an Issue in Greenfield instance?

[Suryansh Verma]

@Nigonda 

In the greenfield instance, the remaining Catalog Tasks show “System” because they are being updated by a Flow Designer execution running as the System User.

Create a separate record-triggered flow on sc_task that starts when the State changes to Closed Incomplete for the Staff Departure catalog item. Configure the flow to run as User who initiates the session, look up the other active tasks belonging to the same Requested Item, and update them to Closed Incomplete.

Add a Boolean field such as u_cascade_closed and set it to true on the automatically closed tasks so that those updates do not trigger another cascade. Also populate Close notes with the source SCTASK and initiating user.

Do not simply change the existing long-running fulfilment flow to run as the initiating user, because its initiating user may be the original requester rather than the fulfiller who closed the SCTASK.

If it is helpful, please mark it as helpful and accept the correct solution by referring to this solution in the future, it will be helpful to them.

[Tejas Adhalrao]

hi @Nigonda ,

What you're describing is expected behavior in many cases when using Flow Designer.

I'd check a few things:

Is the Flow configured to Run As System User or Run As User?

Are the remaining SC Tasks being updated directly by the Flow, or is a Business Rule/Script Action performing the updates?

If the client specifically wants the activity history to show the logged-in user's name for all task updates, you'll need to review how those updates are executed.

If this helped, please mark it as Helpful. If it resolved your issue, please mark it as the Accepted Solution.

[Nigonda]

Hi @Tejas Adhalrao In the flow designer properties I updated Run as a -User who initiates the session. But I am getting as same in SC task activity as updated by system