Asset Nodes (Add customer Assets)

[Jim]

I use this in my leaver process and use the 'user ID' option - as the customer is often the manager - to link the leavers owned by assets, unfortunately it doesn't seem to do what it says and returns the used by assets where the user is also not the owner. I have 5 Assets in my name currently and for 4 of them I am the used by and owned by user, when I run this it only returns the 1 assets I am not the owner of? 

 

[Jim]

Any advice would be appreciated

[Steve Giller]

Used By = False would suggest to me "Do not include Used By"

Which is what the results would confirm.

 

[Jim]

I would expect it to return the 3 opposed to the one?

[Jim]

The 4 even, but if the owned by is also that user, I would expect them to be returned

[Jim]

at least in my mind,

 

If I was to do a query where device owner = {user id} I would expect all devices to be returned, it feels like this node when setting used by false, is adding an 'And' and saying where device owner = {user id} and used by is not equal to {user id} The problem is we use owned by as our manual tracking of assets and used by is automated via the import and update scripts so when querying for leaver devices I only want to see the devices owned by the user and not used by for this reason

[Berto2002]

The way this is coded also weirds me out; it's not intuitive but you can get to what you want with the right config. Testing and trial and error...

I had this scenario: when the "User ID" was set to AUTO and "Used By" was set to TRUE, the system picked-up the Line Manager's Assets! That feels completely wrong to me because this node is about adding the Customer's assets so an Auto response collecting anyone but the Customer's assets can't be right?... HB Support: "User ID set to auto is not a valid option, so it's the same as User ID not set. They need to specify an ID as there is nothing that automatically populates this value.

[Steve Giller]

1 hour ago, Berto2002 said:

I had this scenario: when the "User ID" was set to AUTO

What do you imagine Auto would do here?
If you are not specifying the User Id leave the parameter set to the default of Ignore. If you set it to Auto you're telling the Workflow to set the value to something without specifying what - and as the point of that value is to not use the Request Customer using Auto for that setting can be nothing but unpredictable.

[Berto2002]

In my mind AUTO is obvious, though. Just as AUTO on the Request ID picks up the current Request ID, AUTO on a User ID field that is named "Add Customer Assets" should pick-up the Customer's User ID; and at the very least it should pick-up nothing (not a connection with the line manager)

... but as I said to Nanette on a support resolution, if it works, making things work the way I want them to is not your job and there are more important things of you to be doing