Jump to content

Line Manager only partially adding as a Connection (i.e. cannot be used in workflow)


Berto2002
 Share

Recommended Posts

Hi,

In a Business Process, I have a flow to Get Customer information and then add the Line Manager as a Connection:

image.png.11b426271f8e59d68738bbc6f1d8173f.png

It uses this configuration:

image.thumb.png.43e6f2b9571c5a4d2884560b67bef70a.png

The variable is: "&[global["flowcoderefs"]["getCustomerInformation"]["managerName"]]"

The user has a Line Manager set in their User Details:

image.thumb.png.4f31c8fd6699fb151a8efd734fcd6ce8.png

 

And yet, repeatedly and consistently (for all users), we get this result in a Request ticket after logging (a partial but disabled Connection):

image.thumb.png.2008546c4e4bacd59587c4a3079bdc5d.png

 

The system has clearly attempted to put a Line Manager there because the Actions drop-down gives the option to Remove. But our process breaks when trying to use that connection and treats it as if it is missing.

Our subsequent flow requires the Line Manager Connection to seek approvals. We are currently having to ask all our agents (where approval is required) to remove this 'orphan' Line Manager connection and to manually add it back in whereafter it then appears as this; which then works on our ongoing process:

image.thumb.png.3b7b76ad1be4a5492894a4c55ffc0aef.png 

Could you please help with why this is not working and what to do next? Is this a Premier Support issue I need to log?

Thanks,

Berto

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...