Flex Workflow Summary Page Updates
Brought to you by:
gsteimer,
tsgopensource
Menu
▾
▴
#333 Flex Workflow Summary Page Updates
A number of updates are needed on the workflow summary page in the flex module:
1) The role owner does not need to be displayed all the time. Only display the role owner as the approver name when appropriate (role tripped, but no users assigned)
2) There's no need to have the title "Roles at Priority #". We can just style this as a number that appears on the right of each priority container, similar to how the old HTML view worked.
3) When displaying the role priority, the number displayed should be sequential based on the rules evaluation, rather than the actual role priority in the admin. For example, if the following priorities are tripped: 1, 3, 7 - the roles should display as 1, 2, 3 on the workflow summary page, not 1, 3, 7. The numbers don't matter in the admin at all except for order.
4) This is a nice to have at this point, but it would be good to have this page styled a little nicer.
As of 4/4/2012, most of this has been completed, with the following updates needed:
Need to add the question mark icon to trigger help text. Right now, that text is visible when you click the activity box, but it's not apparent that it's available to the user without some sort of visual clue.
Also, another nice to have would be different styling for the different types of roles (user based / group based / automatic). Perhaps it could be just an icon that appears in the role box?
One bug related to the recent updates that Don made is that a group based role seems to always be displayed at the top of the list, even if some user roles should be triggered before it. Need to be sure that we are testing group roles with a 7 priority and a user role with a 1-6 priority to be sure that it comes first.
Re: group based roles - I tried this using the Simple Change Request form in wizard_d65 and the Regulatory Affairs group based role was appearing fine for me. Perhaps we should archive the Reinsurance Report on demos_sb on TSGDEMODCTM1 (this is the form that prompted Ben's comment below) and see if it's a configuration issue?