Composer

RE: Composer

rohity0003 — Fri, 06 Mar 2026 14:52:07 GMT

Thanks Stefan for your experience based answer. I have come to a similar conclusion at this time:
Composer generates some of the code, but it does not specify what has been generated, and what has not, and what has been partially generated and needs to be completed. In order to use the code, programmer has to understand requirements, and then understand how the generated objects fit into the requirements, and then move forward to coding.

RE: Composer

Stefan Helzle — Fri, 06 Mar 2026 10:14:05 GMT

In my tests with composer, I think that you have to touch each and every object to make this a stable, maintainable application following your local best practices. E.g. composer does not use translation sets.

RE: Composer

Shubham Aware — Fri, 06 Mar 2026 05:12:21 GMT

After Composer generates your plan, go to the Plan tab and review the planning tabs - each tab lists the objects that need to be completed or created.
Simply work through each tab to know exactly what your team needs to build.

www.youtube.com/watch

RE: Composer

Radhamani Ramasamy — Thu, 05 Mar 2026 17:22:38 GMT

It's totally based on initial requirements you have in your hand. You have to upload a requirement/Plan document to the composer. Based on the logics you have in your document, Appian will suggest records/rules/processes/data model/personnas which you may need to build your application. You will have an ability to remove which you don't want to get created before composer creates it. For more details, check here- Generating a Plan - Appian 26.2