We are migrating to 7.3 and I just want to check if Appian recommends using the

Tempo allows you to integrate work automation with mobile and social capabilities with all the data, all the processes, all the documents, and all the collaborations in one environment on any device. With the enhancements made to the Tempo Interface as of Appian 6.7.0, the Portal Interface should now only serve as a way to update profile information, modify account settings, and view portal pages. Tasks and actions should be completed through the Tempo Interface when possible.

thanks patty, so if we have a use case which can only be done using javascript and tempo forms dont support javascript, how I do expose that to the user?

forum.appian.com/.../Component_Configuration_Properties
Please keep in mind that by using javascript, your forms will no longer be Tempo enabled.

So if I have a use case for activity chained forms and one of them has a need for some javascript logic, I guess the chain will break. In such cases(where we cannot avoid using javascript), what is the pattern people follow. Just launch the action from tempo in a popup window?

What is the javascript logic?

Its a simple logic to check if all the components(checkboxes) in a grid are selected or not? Irrespective of the complexity of the logic, the activity chain will break if I use javascript in one of the forms right?

Can you use an expression rule to determine if the number of checked values = the number of values. You can then use a gateway to route whether to user can continue with the chained task.

I would suggest you work on ways to get around javascript logic on forms where possible (chaining will be broken on any non-tempo-enabled forms, and you won't be allowed to tempo-enable forms when they contain javascript, so yes). But the use case you describe could probably be handled by post-form validation...

thanks.