I’ve been updating several flows that process service catalog items, and I’ve run into an issue with a list collector variable. Our catalog has several items that allow for users to create tickets for other users, collecting those users in a list collector variable. The work I’ve been doing is updating the flows behind these items to link the REQ, RITM, and SCTASK tickets back to the cost center of the actual impacted users, not to the person creating the ticket in the portal for time accounting and so forth.
So, I’ve been going from flow to flow, putting in a few actions at the beginning that look up the first user’s record (note, not “records,” since everyone on the list most likely are the same) in the list collector variable, based naturally on the sys_id of the user to as the condition. These edits worked fine for the first six flows, but suddenly, I couldn’t dot-walk to the sys_id from the variable anymore. Moreover, when I went back to the first edits, which did work and trying recreating the same update, it also won’t show the option to dot-walk the list. See screenshots below for clarity.
I’ve read a few posts about similar issues either in an older release, such as New York, or in more complex logic, using in-line code or subflows. I’ve also confirmed this works as expected on my San Diego PDI but again, will not work in our test environment, which is on Rome (we upgrade at the end of the month). Finally, I’ve tried different browsers and reset the instance cache for Test to confirm that it’s not local or a cache problem.
I could work on doing through by processing variable as a list of sys_ids, but I’m mostly curious why it stopped working and if there’s a fix.
Missing Dot-Walk Link, In Look Up Record Action
Previous sys_id → sys_id Example
Working in San Diego PDI
Has anyone else run into this?
Thanks!
