|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
I still don't quite understand how that use case requires a third option on the "Create New EPerson" page. If this is a checkbox/radio button on the "Create New EPerson" page, then wouldn't you want to select the "don't send an email" option if you don't want the user to be immediately notified/activated? So, the workflow for your described use case seems like it'd be:
1. Create the New EPerson (select "don't send an email")
2. Add the New EPerson account to appropriate Groups
3. Edit the EPerson, and on the "Edit EPerson" page click a button to "Send New Account Email" (or "Reset Password") to actually send the notification to the user.
So, in the end, we still only have *two* options on the "Create New EPerson" page -- (a) send email (with link to create a pwd) or (b) don't send an email
Am I still missing something here? I still don't quite understand why we'd need three options on the "Create New EPerson" page.