..the following line should go in the big blank space above. Mentally add the brackets yourself ;-)
variable name="manuf_part_number" access="read"
correct, we currently see this as a ui issue. Since we do not want do start developing a new ui framework. Maybe in the future we will extend the editor to define this but not necessarily in the processdefinition.xml. One thing that would add functionality to the default ui is the variable type. If it is not used in the process, the default is string, so the ui renders all fields the same. I'm trying to persuade Tom to at least at the varialble type
Did you guys integrate the code from the previous link?
It seems that he added code to that data types other than String could be displayed properly. Not sure if he also added the capability to enter data types other than String or if that form would then validate user input before submitting.
For me it would be a perfectly adequete solution if his suggestion was implemented and workflow developers could add the data for radio buttons and pop-out menus something like how kgalligan suggested which is...
startDate = new java.util.Date();
quantity = new Double(3.456);
Perhaps a data type of an array of strings could be created which listed options for menus. I suppose that would also work for radio buttons or perhaps something boolean would be adequete for those.
I also found this forum posting helpful but didn't quite get me to the finish line.
I'm now trying to figure out how to implement a custom TaskController as a way of creating a custom form (with the same goal of creating pop-out menus.)
This issue is very frustrating. I can't believe its this difficult to get a pop-out menu in this thing. Free form text entry just doesn't cut it.
Don't get me wrong, I'm starting to really like this platform but I really need a solution to this issue.
I noticed that a VariableInstance only has a label and a value in the database. At least the value can be any java object.
I did see some hope since the TaskBean.taskformParameters has room for not only the label and value but a description, isReadable, isWritable and isRequired. All of those values could be used to change how the user enters data. In JSF HTML there is a nice tag h:selectOneMenu. If passed a list object, that could be used to populate a pop-out menu.
You guys mention customizing the TaskController.java or something like that but I don't understand how that would help since the variable type only has name and value in the database. I'd like to perhaps use an action class to change some of the TaskBean.formparameter values but I'm thinking the Action class on the entry-node event would run before the TaskBean is populated. Not sure how to affect a change there.
I think I can get some customers excited if they can at least see pop-out menus used for data entry. Then I could show them how what choice is made affect which task is assigned next. (My next plan is to input files and then export data from the database into an excel readable format) I should be able to get some customer and hopefully purchase a subscription to your Support Services. I'd love to just work with you guys and jBPM to deliver custom workflows to whoever wants 'em.
Okay, enough rambling. I actually am not a total computer geek and its Saturday night so I'm out to get a beer and ...?
If you could help explain how I can get a pop-out menu, I'd be ecstatic :-)
David.... If you realy need a custom ui NOW you have to build it yourself. Otherwise be a little patient. In other threads I've mentioned that enhancements will be checked in comming week and guess what? it will include a pop-out date entry field.
Okay. Sorry. I'll be patient. I do appreciate your guys hard work. I'm trying to actually create a business with this stuff. I have a friend at Cisco who says they are all over the concept of collaborative work tools. I'm trying to get him a proof of concept for a particular business problem he is facing. From there hopefully a project.