Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Consider blue path only! I used activity chain to start "Choose policy" interface immediately after the main interface. The process is started by a startProcess inside a saveinto of a buttonWidget. After clicking the button the process starts, but the interface isn't automatically loaded. The owner of the task is set as pp!initiator. What could I miss?
Discussion posts and replies are publicly visible
You cannot chain into a User Input Task with a!startProcess from a buttonWidget in another process - in this case your parent process is simply waiting for the secondary process to complete on it's own before continuing with the parent process (with a setting of "synchronous").If you are moving the user from one process to another, why not utilize a Subprocess after the parent input task completes?Ways to Start a Process
Use a!startProcessLink() instead of a!startProcess() in the button saveInto.
Unfortunately we cannot use a!startProcessLink() inside of a!buttonWidget().