Project structure for app deployment is unclear

We are trying to create a new app for the Freshdesk marketplace, in this app we need to set up a configuration page as well as a main product page (amongst other things) which will both be using the location key of “full_page_app” according to the sample apps we found. It seems that creating one app with two/duplicate “full_page_app” location keys is not an option.

This app needs a configuration screen where the user can change settings of the app, as well as a main app screen listed in the global sidebar. In that case, do we need to deploy two apps separately or is there an existing
sample app that that would work for this use case?

We kindly ask for a rundown of how this app’s structure will need to function in order for us to deploy to Marketplace in the future.

Kind Regards,

Jonathan Taljaard.

Hi @Jonathan_Taljaard ,

Welcome to the community :tada:

This app needs a configuration screen where the user can change settings of the app, as well as a main app screen listed in the global sidebar.

Did you happen to check Installation Parameters for this use-case?

With iparams users would be able to set up initially on installation of app & also edit under settings whenever required.

If you’re looking for sample app to play with, please check - GitHub - freshworks-developers/configuration-page-samples: Configuration pages allow developers to invite Admin users to preconfigure the app before the app is installed and ready to be used. Samples of these features can be found on this repository.

Let me know if this solves, thanks

1 Like

This Installation Parameters was the solution thank you, the confusion was caused by the configuration-page-samples having two apps listed - One with iparams.html and one with the iparams.json with the iparams.html being the one requiring the “full-page-app” location key.

Thank you so much!

2 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.