JJack Posted June 5 Posted June 5 Hi, I've added a branch in a capture based on a Session variable. It's not behaving as I would expect. Is there a way I can display the Session variables? In general, how do I know what type of condition I should be using? For example, for Session->Users Manager Name, how do I know what kind of value to enter? If I look at a user's details in platform configuration, there is no field labelled 'Name', and the 'handle' value didn't work, nor our id fields. I can display the Global variable, user.managerName but using that in a condition as Users Manager Name doesn't work. (Haven't found any helpful documentation, any links to that would be appreciated). The variables I seem to be able to choose from in a capture for a 'Goto If' are shown in the screenshot. The documentation on captures, Intelligent Capture Designer (hornbill.com), has a section on Global Variables, which mentions two, portal type and source. It also has a list of variables to 'personalise' the capture, so apparently not of use for branching. This capture documentation doesn't seem to describe any details about branching on the 'Session' variables, I just picking what's available from the dropdown within a capture. Thanks, Jill.
James Ainsworth Posted June 6 Posted June 6 Hi @JJack Thanks for your post. The Session->User Name is looking at the field titled Handle on a users profile. I've tested this on a branch node and has been working for me. I also tested the Session->Users Manager Name and I too was having some mixed results on the path that it takes. I will continue to test and I have also mentioned this to the development team to see if they can clarify how this should be working. 1
JJack Posted July 4 Author Posted July 4 I notice that Session->Users Manager Name is working for me today, I can specify a 'handle' in the condition. I assume this follows update Hornbill Core UI (2202), many thanks!
James Ainsworth Posted July 4 Posted July 4 Hi @JJack Thanks for the feedback and letting us know that this is now working for you. Your assumption is correct that this was fixed in that last update.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now