Hi @k.hendrickx. Which version/year of Inventor are you using? I believe it was either in the 2023 or 2024 release of Inventor Professional where they started allowing is to directly place iLogic rules into the ribbon, in the 'User Commands' panel, without needing to use a 'VBA macro'. Since a 'ButtonDefinition' is automatically being created for those 'rule buttons', we can set a shortcut (ButtonDefinition.DefaultShortcut) for executing the 'ControlDefinition' behind the button. For example, I created a simple external iLogic rule named "Show DisplayName", then placed that into the ribbon as a rule button. Then I opened the Customize dialog box, clicked on the 'Keyboard' tab, then scrolled down to where that control was listed, and selected the row it is on, to the left of its name (in the 'Keys' column), then pressed the Ctrl + Alt + D keyboard combination, and it set that as its shortcut. Then I clicked on the Apply/OK button to exit out of the Customize dialog. Then I pressed that key combination, and that rule ran, showing me the current document's DisplayName, as expected.
Before we were able to directly add external iLogic rules into the ribbon, without using VBA macros, we could still create custom button definitions and add them into the ribbon, even if only temporarily, then use an 'event handler' for its OnExecute event to run an external iLogic rule. But all that stuff had to be managed by us, so to speak, which was complicated to manage with just iLogic rules, but could more easily be done with something like an Add-In, which starts when Inventor starts.
Edit: Actually, when we do that through the Customize > Keyboard dialog, that is setting the ButtonDefinition.OverrideShortcut property's value to "Alt+Ctrl+D", and its ButtonDefinition.OverrideShortcutType would automatically get set to the "kAcceleratorShortcut" variation of the ShortcutTypeEnum. I think the DefaultShortcut property may need to be set when the control was first created, if at all, but I never used the shortcuts much for iLogic rule buttons because clicking them was convenient enough for me.
Wesley Crihfield

(Not an Autodesk Employee)