The CreatorCon Call for Content is officially open! Get started here.

Lock down Variables in Task after its submitted

Tom Thompson
Tera Expert

I have catalog items that have Reference fields that create tasks and for example

 

Change Group name pulls the Name in from Servicenow

When the tasks is created it has that old name but when the name is changed and the 1st tasks

is closed out then the next tasks to a different area to correct in there area gets a tasks and the new name

is in Reference field now. 

 

How do you stop the Reference fields from updating after submitting the REQ? 

16 REPLIES 16

Community Alums
Not applicable

Hi  @Tom Thompson ,

 

Have you tried this? Pretty sure this will match your requirment.

Please try & let me know if it works.

 

Thanks & Regards,
Madhan Somesh

Maddysunil
Kilo Sage

@Tom Thompson 

You can try using Before update business rule

Condition: current.u_reference_field.nil();

Script: 

if (current.u_reference_field.changes()) {
// If the Reference field is changed, set it back to its previous value
current.u_reference_field = previous.u_reference_field;
}
Please see the screenshot.

Kindly mark helpful/accepted if it helps you.

Thanks

is this a new business rule?

Mark Manders
Mega Patron

Can you share your current flow/script that is doing this. I don't really understand what is happening.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

Mark,

 

Its just a normal workflow

Create a tasks to group they change the name of Current group 123 to Group 321 Close task and

then next group gets a tasks to update what Should be group 123 but now that Admin has updated to Group 321   it shows the new name.   so causing confusion.   

 

happens on all Reference field items that are being updated