+2
How do people interact with workflows in the real world. Do they make custom aspx pages and make calls to the k2 api to get and set things in the workflow, or do "most" people use the forms generation wizzard.
I know that you may have to Style a custom forms page when the workflow is updated, but it seems easier to style the page than to write custom web pages for every new workflow? Any suggestions are greatly welcome.
+11
There is no one answer for this question. It depends: what is the development style at your location? What technology do your developers know best? How much do you want to customize the form? How complicated are your data validation rules? How much do you have invested in an existing UI technology that you want to integrate with?
You have many options for client events: custom ASPX pages, forms generation, InfoPath, and SharePoint. Any one of these might be a good choice depending on circumstances.
Tip: If you use ASPX pages, you don't always have to write new pages for each workflow. It is very common to design a generic page to handle simple approval steps that is not specific to any one workflow. There are several blackmarket projects to help you create web pages.
+9
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.