Active
Project:
Workflow Fields
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
28 Nov 2010 at 05:53 UTC
Updated:
30 Nov 2010 at 13:34 UTC
Jump to comment: Most recent file
Comments
Comment #1
bakr commentedIt is going to resolve a Major Usablility Issue.
For me, as a site builder, it would help me to look easiliy anticipate the location of grouped fields, the same way and same sorting as in the Manage Fields Section under CCK.
Comment #2
infojunkieThanks for the suggestion, it is a good one. I hope I can get to implement it in the near future.
Comment #3
bakr commentedKeep up the good work
And Big Thanks
Comment #4
bakr commentedAttached herein is a sample imagined interface
Comment #5
bakr commentedGood day Karim,
I have another enhancement Idea to share:
Why not deal directly with Groups(optionally, and where available), and any sub-field to that group to automatically inherit the role mapping to that group in that state screen.
This would significantly accelerate the handling session in the fields mappings screen for that state of workflow X
Best Regards
Comment #6
bakr commentedAs a follow up,
I have created a script in Lasso middleware version 8.5.6 (lassosoft.com). and sharing the source code with everyone.
That script connects to drupal database, to analyze and visualize the situation
It is a kind of "Reverse Engineering"
The concept works as follows:
- It is Node a Centric Perspective about Workflow Fields, so you select the node in question
- It shall realize the association with the workflow through the proper mapping.
- It shall list the available states under that workflow
- It shall present the Node Fields (with Grouped Display) for each WF State sequentially in the same page.
- It does not touch drupal tables, rather reads what is their for visualization purpose
- It helps site developer debug and have print-out documentation of the field mappings, thus saving it work man hours.
Finally, I believe this is a more natural perspective to tackle the workflow domain.
Comment #7
bakr commentedHere is a snapshot of the output of the script for those who cannot open .mht files.