Jack, I've been doing this for years, as I had an old MCF Gantt app before the integration to QB last year.
l'm utilizing my Gantt App from several 'source' apps.
In each source app, I have the following fields
Logic is relatively straightforward, if they need a gantt, they check the [Use MCF Gantt Flag]. This displays the section containing all the other stuff.
[Create MCF Gantt Project] -> sets [MCF Gantt Project Created Flag]=true -> fires pipeline to add a record containing, as you say, all the pertinent info plus a 'hardcoded type' to a new MCF Gantt record. Once Created, pipeline echoes back the new Gantt.[record ID#] to [MCF Gantt Record].
Once [MCF Gantt Record] is populated, I show:
[Launch MCF Gantt Button] &
[MCF Tasks] : just gives a list of the gantt tasks in the source app for easy viewing/reference.
In MCF Gantt: The following fields
The create Gantt Pipeline populates the [Source Record ID] and sets the [Source App Flag] - Admittedly mine is poor for scalability, could use these 3 fields better instead of replicating them for every app linked to this Gantt app.
[Go Back to Source App] : When Gantt chart UI closes, is drops you in that Gantt app, so for the relatively seamless feel you want, in the main page of Gantt, where I land when closing the UI, I have 2 buttons, reopen the Gantt, or go back to the source.
Mine works well for what I'm doing, let me know if you have any questions!
Good Luck!
