Custom applications (Sideloading) - Multi-developer workflow without legacy design

0
Hello everyone,I have a question regarding the recommended workflow for a team of developers using the latest Industrial Edge App Publisher (v1.25.7) connected to IEM Virtual 3.0 (IEM v2.3.2).Background:In IE App Publisher 1.25.7, the Return to Previous Design button is no longer available (as documented in the - release notes) w/ IEM V2. Consequently, it is no longer possible to browse and load our existing applications directly from IEM under App Projects / Authorized Application.The documentation states (notable changes):"To manage an existing application in an IE Management App Project, create a new application in the Publisher with the same app name, app ID, and repository name as the original application in IE Management. Ensure that these three fields exactly match the existing application's details in IE Management."My Question:In a scenario where multiple developers collaborate on an application and more than one developer needs to upload/publish versions to IEM:Does every developer have to manually recreate the app entry in the Device Applications (standalone) section on their local machine using the exact matching App Name, App ID, and Repository Name?Does this imply that each developer’s local App Publisher will only display the versions they personally built on their local machine, rather than reflecting the complete version history uploaded to IEM?Is this the intended workflow for teams, or is there a recommended best practice (e.g., sharing a workspace/configuration file, or relying entirely on CI/CD with the IE App Publisher CLI) to keep developer environments aligned?Just to clarify, I know that allowing custom applications is required - as mentioned here in the Notice box.Thank you in advance for your insights!Best regards,Petr
asked
0 answers