Calling Process Flow on click of Button or link: Is it possible to call a proces

You can do it asynchronously using the process writer plugin, but there's no way to do what you're asking and chaining through to the process

Here is the process writer plugin

forum.appian.com/.../summary

Best practice for current Appian design is to limit activity chaining and instead create screen flows in a single SAIL page..

@jaishankarj Here is the link to shared component which allows you to do so: https://forum.appian.com/suite/tempo/records/type/components/item/i8BCLGOdlMUpdGVqT-RV7oRg74uEGJO5yQeCToV_iK9c-uZFaHQndbxbAQOV2CNBg/view/summary

Additionally I would also like to suggest to go through bind() (Reference: https://forum.appian.com/suite/help/7.10/Evaluation_Functions.html#bind.28.29).

Combination of bind() and startprocesswrite() will do the required work. Additionally there are few posts in forum which have discussed this mechanism which I would like to suggest you to go through.

This allows you to trigger the process, but you won't be able to link to it, for instance you may not expect a link to task that happens as the part of process triggered using bind() and startprocesswrite() (similar to fire and forget approach)

Malcolm, would you be able to point me in the direction of the documentation for the best practice you refer to? That's a new one to me and I'd like to make sure we're following it on our project.

Here is the Appian Best Practices document..

forum.appian.com/.../Appian_Best_Practices.html

Specifically for this.. it applies to Process Modeling..

forum.appian.com/.../Creating_Memory_Efficient_Models_Best_Practices.html

To create highly performant processes it is best to limit the number of nodes in a process.. creating Activity Chained form flows adds unnecessary steps that could rather be done in a single step using a screen flow designed in SAIL instead of a chain..

Many thanks; would I be right to assume that the caveat would be that you shouldn't build (for example) a 10-step form in SAIL, and to make sure that the use of a multi-step SAIL form doesn't compromise reusability of the component forms?

Not sure I understand... Suggest checking out the design techniques employed in the Appian Case Management Framework in Shared Components..

A 10 step form in SAIL is fine.. You would use re-usable form elements to comprise that SAIL form flow..

I would only recommend Activity Chaining if you need to have a form flow that must transact across an automated process step.. for example. You capture some information, then chain over an automated transaction in process, then continue the form flow..

Ok, thanks, will do. I guess I would have expected such a large SAIL form - even when made up of 10 different reusable SAIL expressions - to evaluate rather slowly and so cause issues elsewhere.

The nature of SAIL is that the entire form is not rendered at once.. only the section that is needed.. Also with performance improvements in 7.8, 7.9, and 7.10, you Appian is focused on ensuring very large SAIL forms (300+ fields) perform very well..

meant to say "you will find Appian is focused"