[Building Sakai] Sakai 2.6.x Site Info Add Participants, change in work flow if add existing participant

[Walters, Cynthia (cmw6s)]

Hello:

Our recent upgrade to 2.6.2 has uncovered another change in Site Info - Add Participants from 2.5.x, and we prefer the 2.5.x work flow.  We wonder if this is a work flow design change, or perhaps an oversight in the 2.6.x migration to RSF code?

Description:
If adding new users to a site and some of the users are already participants in the site, the UI correctly alerts that existing users are present, but forces you to remove them before proceeding to choose the role for the valid new users -- In 2.5.3 the existing users were noted in the Alert and work flow was allowed to continue. 

2.5.x behavior:
    -- Add participant who is already a site member (add official username), and add email address of non-official participant...
        -- choose 'same role' and Continue
            -- tool changes to next page: "Choose a Role for Participants", and displays "Alert" about not able to add already-existing participant, and does allow user to continue to add other participants not already members of the site

        The same work flow is true if choose 'individual role' choice.

        Comments: 
            1) The tool correctly alerts the user if there are any participants listed who are already members of the site.
            2) The tool user is allowed to continue and the tool omits the invalid entries.


2.6.x behavior:
    -- Add participant who is already a site member (add official username), and add email address of non-official participant...
        -- choose 'same role' and Continue
            -- at this point the user is stopped on this "Add Participants" page and two alerts appear:
                !  The following participants are already members of this site and can not be re-added: 'cmw6s'
                !  You may continue adding the other participants by following the directions below.

        The same work flow is true if choose 'individual role' choice.

        Comments: 
            1)  the 2.5.x behavior is more useful and preferred
            2)  this second alert message is not valid for the page
            3)  this behavior forces the user to delete the invalid entry and select 'Continue' again, rather than the tool omitting it and allowing the work flow to continue (as was the case in 2.5.x)

Thank you for any insight on this issue.
Cynthia Walters
University of Virginia