[JBoss JIRA] Created: (JBPM-778) form generation improvements
by Tom Baeyens (JIRA)
form generation improvements
----------------------------
Key: JBPM-778
URL: http://jira.jboss.com/jira/browse/JBPM-778
Project: JBoss jBPM
Issue Type: Feature Request
Components: Graphical Process Designer
Reporter: Tom Baeyens
Assigned To: Koen Aers
Fix For: jBPM 3.2 alpha 3
Here are some updates for the form generation:
1) Column reordering and renaming
* The first column should be named 'Label' and this should be the currently last column with name 'Mapped name'
* The second column should be named 'Variable name' and this should be the currently first column named 'Name'
The rest of the columns should follow after those.
2) A comment inputfield checkbox should be added. This should result in a textarea input field that corresponds to generating a comment associated with the token and taskInstance.
3) A comments display checkbox should be added. This checkbox indicates wether this taskform should display all the comments that have been made before on this token.
4) For each transition button that will be generated, the user should be able to see the transition name, change the label and make it unavailble (through a checkbox that is checked by default)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 7 months
[JBoss JIRA] Created: (JBPORTAL-1043) introduce UserProfile and user metadata (storage mechanism agnostic)
by Boleslaw Dawidowicz (JIRA)
introduce UserProfile and user metadata (storage mechanism agnostic)
--------------------------------------------------------------------
Key: JBPORTAL-1043
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1043
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal Identity
Affects Versions: 2.6.Alpha1
Reporter: Boleslaw Dawidowicz
Assigned To: Boleslaw Dawidowicz
Fix For: 2.6.Alpha1
- Each user entry (ldap or database table) can bring different set of user personal information. This makes the user profile
- In portal we have property names like: user.name, user.surname, user.email, user.phone and etc.
- Each UserModule implementation provide a mapping of properties to coresponding values in underlaying database or directory
(table columns or ldat entry attributes for eg.)
- Profile informations are accessed using API like:
user.getMetaData().getProfileMetaData().getProperty(User.NAME_PROPERTY);
.getAllProperties().iterator()
- Currently this is handled by PropertyMap - keept as separate table in DB
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 7 months