It is the BtName (blue)
Not possible to use a variable in that case to link the label name to a slide name. But I still don't see the purpose at all?
Will you need the same button with the same name on multiple slides? Will you use timing for the rest of the project in that case? Because you cannot reuse a name for a button, if you have two instances of that button on two different slides, they'll need each a different name. If it is the same shape button, timed for the rest of the project, it will always use the same action, doesn't even need an advanced action because it will be 'Jump to slide X'. But there is no way to use the name of the button in that action at all. Shared action is possible as well, with the X as parameter, and then you can assign this to all the buttons that need this action. But why do you want the link between the button name and the slide name? Can you explain? My Captivate intuition tells me that there is some misunderstanding, maybe due to your Lectora experiences. Captivate is really different, have presented about the differences in work flow with a Lectora expert. I'm not using Lectora anymore but the structure, and certainly the way to 'script' is totally different.