After receiving feedback concerning one of the most well known User Experience (User XP) features, labels management, we are now facing a difficult choice.
We believe that the best solution is the one that best fits the need of the community, so we are requesting your input.
This is about how users like to organize their list of tasks in Bonita User XP.
We are currently using a label approach:
- Bonita User XP offers 6 predefined labels: Inbox, Starred, Unread, My Cases, Archive and All.
- The definition of these labels is shared by all User XP users, for instance “My Cases” always means “cases started by me”.
- Some of these are automatically attached to cases by the system, i.e., Inbox, Unread and My Cases.
User XP also allows all users to define their own custom labels.
A custom label is a means for each user to organize their tasks accordingly to their own logic.
The list of custom labels is user specific and is private.
That is to say, that if user “John”
- creates a label “todoBeforeHolidays”
- assigns this label to the case “review Jack’s report”
then neither the label nor the association between the label and the case will be visible by anyone other than “John”.
The feedback we have received is that some people would prefer to see all labels assigned automatically to cases by the server instead of having users doing it manually.
We are considering the possibility to replace the current feature with a new one, not only because of this feedback but also because this powerful feature has a cost: heavy queries are executed against the database and impact the reaction time of the User XP.
An alternative to the label approach is the tag approach:
- Only authorized users can create new tags.
- Tags are automatically attached to cases by the server according to predefined criteria, e.g., instances of “Vacation_Request” are assigned tags “HR” and “Vacation”.
- The case-tag association is visible by ALL the users involved in the case.
- Consequently all the users will have the same predefined tags to sort and search with. (The logic is centralized)
This approach seems less flexible from a simple user point point of view, as they cannot organize their tasks with their own system (cannot create new tags or change the tag-case associations).
The advantages of this approach seem to be:
- standardize the organization of tasks among all the users
- guarantee that users will not “lose” a task by attaching a wrong label
- reduce the impact on the User XP reaction time (less data stored in the database and lighter queries)
| Advantages | Disadvantages | |
| Label approach | user logic | performance affected |
| Others? | Others? | |
| Tag approach | central logic | user cannot customize |
| performance maintained | user acceptance (in case of migration) | |
| Others? | Others? | |
Which approach do you prefer?
What other advantages and disadvantages do you see?
#1 by Giri R on June 3rd, 2010
Quote
I think it is the same user experience debate like Google vs Outlook..
In my opinion, i think the Tag approach seems to be good because it is automatic (provided we create the necessary rules).. So i prefer the tag approach.
#2 by Marc Lesur on June 3rd, 2010
Quote
I would prefer the tag approach if the following functions are available :
- tags can be assigned automatically according to the variables of the case (they can then change automatically during the process)
- multi tags can be applied to one case
- only the tags related to the user’s cases will be visible (the others will not be visible)
In that way it will help users to find the appropriate cases without having to open them.
I prefer also the centralized approach which allows to define standard way of managing the cases.
#3 by Wesley Fraser on June 4th, 2010
Quote
I would agree that the tags would be one of the better choices. If tags can be possibly created when the step gets created.
#4 by Bladimir Rondon on June 8th, 2010
Quote
I Agree.
#5 by Kereszt on June 11th, 2010
Quote
Why deny users to create tags for themself?
User tags would be non-auto-assignable
, invisible to others and serve only personal task management (eg. beforeHoliday). Users would be able to manage their own set and those tags would be indexed only in the context of the user.
In contrast, system wide tags can be auto-assigned and non-modifiable by simple users.
This way we can have “labels” but still working with tags, maintained performance and no tasks lost under the horizon.. can’t we?
#6 by Hendy Irawan on June 13th, 2010
Quote
+1 for tags.
Agree with Kereszt, there should be system-wide tags and user-specific tags.
System-wide should be a priority.
In addition, after doing “Mark as read”, the selection should still be selected, don’t clear. (So it’s easy to do: Mark as read -> Archive)
#7 by Hodjat on June 13th, 2010
Quote
I think the Tag approach is better for BPM, because of central logic.
#8 by Nicolas Chabanoles on September 14th, 2010
Quote
Hi and thank’s to all of you.
This short comment to let you know that BOS 5.3 is going to take benefits from Tags and Labels. So both system-wide and user-specific assignation will be possible.
Nicolas