Recall order in EAM

[Mamidi]

hi all,

there are so many recall flows triggered when recall order is created so in one base flow as follows

Enterprise Recall flow:

    1.It triggers whenever a recall task is created by a user.

    2.First it will get the impacted assets by taking the record sys id 

    3.for each item in that record like for each asset in get impacted asset it will create a recall asset record and task record

4.when stage is closed or cancelled it will update recall order record to completed or cancelled(it will give error)

so within this flow i tried to test this so that i create a recall order but in recall order it is showing that to select a model and there is no asset to select and another thing is that when i created by selecting a model also it was creating a recall task but not creating a recall asset record as we can't select assert how it will run can you correct me if i am wrong and explain this thing .

[Matthew_13]

Hi Buddy,

Yeah, you’re not wrong. What’s happening is your flow is built around “impacted assets,” but the data you’re creating in the UI doesn’t actually give it any assets to work with.

Here’s the simple way to think about it:

1. Your Enterprise Recall flow starts when a Recall Task is created, not when the Recall Order is created.
   So creating a Recall Order is only a partial test unless the system also creates the Recall Task and links everything correctly.

2. The flow then does “Get impacted assets” using the record sys_id.
   But impacted assets only exist if your Recall Order already has assets linked to it somehow (usually via a related list / relationship table), or if your “Get impacted assets” step is written to pull assets by the selected model.

3. In your case, the Recall Order form is forcing you to pick a model, and you said there is no asset selection.
   That means one of two things is true:

   • The process expects you to attach assets after creating the order (related list, import, etc.)
     or

   • The flow is supposed to find assets automatically based on the model, but that part isn’t working / the query is too strict and returns 0.

4. That’s why you’re seeing this behavior:

   • Recall Task gets created (because that can happen even with no assets)

   • Recall Asset records do NOT get created (because the “for each impacted asset” loop has nothing to loop through)

So the flow is basically doing:
“Create task → look for impacted assets → none found → skip creating recall asset records.”

The error you’re seeing when closing/cancelling is a separate issue and usually happens because the flow is trying to update the Recall Order to a state that the system won’t allow (invalid state value, read-only field, business rule, or ACL).

If you want to confirm this quickly, add a log step right after “Get impacted assets” and print the count. If it’s 0, that’s exactly why the recall asset records aren’t being created.

@Mamidi - Please mark Accepted Solution and Thumbs Up if you find Helpful 🙂

[Matthew_13]

@Mamidi _ Hope you are doing well, if answered can you mark as Accepted solution. Thanks Kindly