Anyone know how to: 1) Provide a form user with zoom and font size function

1. Configure your own browser's zoom and font size maybe, not directly supported by Appian itself.

2. The only alternate row colors out of the box are gray and lighter gray. You might be able to cobble something together with boxlayouts arranged in such a way as to appear like a grid for getting pink and green.

3. You can create a menu in SAIL that end users can select values on, then based on their selections hide or show columns or components of another screen.

4. You'll have to play around with the report builder and perhaps look at some of the reports tutorials under the training tab. Appian SOP is to display the graph first, with ability to drill down into data.

5. You'll have to be far more specific in order to get any clear ideas about implementation, but it should no doubt be possible.

6. If by "autofill" you mean carry over values and automatically display them in inputs if the system has already collected them? Yes. Not only is that possible, it's recommended. You do it by passing process variables as rule inputs into your forms, then saving the outputs back to process variables, then doing the same on the next form. The only thing that could be recommended more is questioning with each one why you even display the input again. Ask yourself, "Did we already collect this information?" "Do we even need to display it?" "Is it possible the user might need to change this?" "Is there any other input that should conditionally prevent users from changing this?" Now you know whether you want it editable, disabled, read - only, or not even there at all.

If you mean gathering who it is, then pulling info from database and preloading the form data, you would do that in a script task before you load the form or as a query in a load variable at the top of the form. Very standard Appian stuff. You'll see loads of examples in function recipies for grids and query entities.

7. Only with the newest versions. There's not too much that you can do out of the box, but you should be able to allow users to customize the colors of some things like Rich Text and Buttons and Card Layouts. Others, such as Section headers, can only be set at the system level in the Admin console. This requirement will force you to use various Appian components for perhaps other than intended use for the sake of color coordination.

8. 3rd Party User management and authentication is a very hairy, sticky subject that will require experts to answer fully. But if we could do it with Shibboleth then theoretically anything would be possible. Especially now that there's an SDK. You get it working for .Net and you might want to consider selling that on the AppMarket if it's not there already.

1. Configure your own browser's zoom and font size maybe, not directly supported by Appian itself.

2. The only alternate row colors out of the box are gray and lighter gray. You might be able to cobble something together with boxlayouts arranged in such a way as to appear like a grid for getting pink and green.

3. You can create a menu in SAIL that end users can select values on, then based on their selections hide or show columns or components of another screen.

4. You'll have to play around with the report builder and perhaps look at some of the reports tutorials under the training tab. Appian SOP is to display the graph first, with ability to drill down into data.

5. You'll have to be far more specific in order to get any clear ideas about implementation, but it should no doubt be possible.

6. If by "autofill" you mean carry over values and automatically display them in inputs if the system has already collected them? Yes. Not only is that possible, it's recommended. You do it by passing process variables as rule inputs into your forms, then saving the outputs back to process variables, then doing the same on the next form. The only thing that could be recommended more is questioning with each one why you even display the input again. Ask yourself, "Did we already collect this information?" "Do we even need to display it?" "Is it possible the user might need to change this?" "Is there any other input that should conditionally prevent users from changing this?" Now you know whether you want it editable, disabled, read - only, or not even there at all.

If you mean gathering who it is, then pulling info from database and preloading the form data, you would do that in a script task before you load the form or as a query in a load variable at the top of the form. Very standard Appian stuff. You'll see loads of examples in function recipies for grids and query entities.

7. Only with the newest versions. There's not too much that you can do out of the box, but you should be able to allow users to customize the colors of some things like Rich Text and Buttons and Card Layouts. Others, such as Section headers, can only be set at the system level in the Admin console. This requirement will force you to use various Appian components for perhaps other than intended use for the sake of color coordination.

8. 3rd Party User management and authentication is a very hairy, sticky subject that will require experts to answer fully. But if we could do it with Shibboleth then theoretically anything would be possible. Especially now that there's an SDK. You get it working for .Net and you might want to consider selling that on the AppMarket if it's not there already.