When setting up package automation, either thru package feed or monitored directory - is there not an option to also automate the creation of an app portal catalog item & related deployments / collections?
If this isn't available in the UI, are there different APIs to have this scripted?
I know there are APIs to create a single catalog item when publishing an application, but how could this be handled as part of the automated publishing (to account for the different applications).
Finally, where are the local logs for automation stored on the server?
Thxs
‎Jul 29, 2022 02:23 PM
I understand that you are trying to configure the automatically imported app to set parameters before creating a catalog item. There are REST APIs and PowerShell Cmdlets to set parameters for an application in the AdminStudio catalog however, your requirement is to handle such changes as an action in the package automation process.
AdminStudio has the capability to automatically set default values to several app properties while importing an app. Please refer to this help topic for more details and to see if this meets your requirement:
Unfortunately, we do not have a specific automation action just to set parameters for an imported application today. I recommend you report this as an idea in our Ideas portal for us to consider this enhancement for the product - https://flexerasfdc.ideas.aha.io/ideas?project=ADM
‎Aug 02, 2022 01:36 PM
Hello @Ralph_Crowley
When AdminStudio is integrated with App Portal (via FSG), publishing an application from AdminStudio to App Portal will automatically create a catalog item for this application in App Portal, there is no need for any additional step to create a catalog item in App Portal. The same functionality works for package automation too (package feed and monitored directory).
When you subscribe an application for automation and configure the actions to meet your requirements, when a new version of the application is made available in the Package Feed Module, the configured actions will be automatically executed on the version. You have to ensure that 'Publish' is one of the configured actions for automation, so when a new version of the application is published to your desired endpoint management system, for example, ConfigMgr, a catalog item for this application will be automatically created in App Portal.
References from help document:
Integration with App Portal:
Configure Actions for Automation:
Thanks
‎Aug 01, 2022 12:49 PM
Thanks for the response - yes, i am aware of the FSG publishing option of a catalog item in AdminStudio - but how can this be included within the package automation (monitored directory or package feed). If the app initially needs to be imported (thru the automation) then it would be a manual process to then go back & change the values in AdminStudio to now create catalog item. I guess what I'm looking for is an option to 1) import an application, 2) publish the app 3) then create the catalog item - and have all three actions available thru automation. Currently it seems only items 1 + 2 are available thru package automation. Thxs!
‎Aug 01, 2022 01:35 PM - edited ‎Aug 01, 2022 01:36 PM
In your example, you mentioned the following three steps:
There is no need for Step 3. Step 2 of publishing an app to ConfigMgr automatically takes care of creating a catalog item in App Portal (Step 3).
When AdminStudio is integrated with App Portal, publishing an app to ConfigMgr (Step 2) will automatically create a catalog item in App Portal (Step 3), so as long as you have the 'Publish' action configured for package automation, there will be no need for any additional action for creating catalog item in App Portal.
However, I see that you mentioned that there is a manual process to go back to AdminStudio and makes changes to the app, and then create a catalog item. I would need more details on how do you create catalog items today (in App Portal?) after publishing apps from AdminStudio to ConfigMgr, so I can better understand your use case.
Also, please note that AdminStudio currently supports App Portal alone and does not support App Broker. If you are using App Broker, then I would encourage you to vote for this idea for AdminStudio's integration with App Broker. We are actively tracking this idea, more votes on this will help us to get this on the high priority list for implementation - https://flexerasfdc.ideas.aha.io/ideas/ADM-I-58
If it helps, I will be happy to get on a call with you to clarify/understand any further questions you might have.
‎Aug 02, 2022 04:46 AM
Yes, I would appreciate a call if possible to clarify. I understand about configuring an application to create a catalog item when published - what I am missing is during step 1 (the automated import process of the app to adminstudio) how to configure the automated import to also set parameters for creating a catalog item (for the imported app) thru the UI.
‎Aug 02, 2022 07:40 AM
I understand that you are trying to configure the automatically imported app to set parameters before creating a catalog item. There are REST APIs and PowerShell Cmdlets to set parameters for an application in the AdminStudio catalog however, your requirement is to handle such changes as an action in the package automation process.
AdminStudio has the capability to automatically set default values to several app properties while importing an app. Please refer to this help topic for more details and to see if this meets your requirement:
Unfortunately, we do not have a specific automation action just to set parameters for an imported application today. I recommend you report this as an idea in our Ideas portal for us to consider this enhancement for the product - https://flexerasfdc.ideas.aha.io/ideas?project=ADM
‎Aug 02, 2022 01:36 PM