Right click actions set up in the Workshop Scheduling Gantt Chart Widget don’t follow the Workshop’s theme. See screenshot above (light mode action modal; dark mode Workshop theme). I am not using embedded Workshop Modules in this instance.
I have noticed a few things about the Gantt chart actions that could use some attention.
-
The actions can’t be customized with colors and icons like right-click actions in an object table can (small issue, but it is nice to have for consistency)
-
There is a place to add a custom action form title, but it doesn’t seem to work. When I enter the custom title, it still shows the default action form title.
-
Sometimes an object set variable used for setting a form-field value does not register. It just shows ‘Object set is not defined’ (I think this could be an issue on my side - but the same action works for a right-click on an object table)
Hey @ShieldAnvil and @SeawardDread !
- @seawardDread Re: light mode vs dark mode: We saw your issue and this should now be resolved in the Gantt! Thank you for reporting.
- Re: Actions matching object table configurations: This is a good flag. We had originally created right click actions before they were available in Object Table. I have recorded this as a feature request.
- Re: Custom Action Form Title: This, along with “hide action form” do not work properly in the Gantt. We are tracking this!
- Re: Object set variable not being defined: Do you mind sharing specifically how you are setting up this object set variable and where it is being used throughout the config? I have a hunch of what may be happening, but it depends on your setup.
Thank you both for sharing!
-Molly
1 Like
Hi @MollyCarmody thanks for the quick response.
I believe I have figured out what the issue is on your #4. My action form (and function) are expecting a true Object Set. The Gantt chart widget is returning an Object Reference Set. This would explain why it is working for variables coming from object tables and not the Gantt widget.
My plan is to change the function and form to work on an object reference set (array of objects) instead of requiring an object set and build the object set in the function where it is needed.
Open to other ideas if there is something easier? I was thinking about trying to trigger a selection event and use ‘set variable’ with ‘materialize on copy’ but I don’t know if that would fix it.
Hi @ShieldAnvil !
Hmm - can you send me a screenshot of your Action Type configuration in the Scheduling Gantt Chart? (Remember to block out any sensitive references / names 
)
Sure thing! Here is the action config on the Gantt chart:
These are the Rules and Parameter config on the form:
I have tried a different action that has the top right “Type” property on the last image set to “Object reference” and it does accept the variable.
Hi @ShieldAnvil, thanks for the additional info. I have a couple of follow ups here: how exactly is that [emp] Selected Object - Emploee(s) or FI(s) variable being set? Is that the same as the output object set variable output from the Scheduling Gantt config? Is this also for a right-click action? or a different usage
If the intention is to feed in the object you’re interacting with, you might be able to use the default widget-provided variable “Schedule Object” in the parameter config dropdown.
Hi @asun ,
That variable is the same as the object set output of the widget. Specifically the “Selected Objects” in the “Output” section:
Yes, it is a right-click Action, specifically on the right-click of a puck and not a row (although I see the same behavior on right-click Actions on the row as well).
I do not see the Resource or Schedule Object options in the parameter selection dropdown currently on any of my Actions (on this Gantt chart). I see them on another chart where I have interactions enabled. I do not have interactions enabled on the current chart in question.
I have confirmed that switching the function input parameter to accept an object array instead of an object set does work (with the rest of the setup staying the same)
Nice one, thank you!