Grouper Users - Open Discussion List

["Black, Carey M." <>]

Chris,

 

Thank you. Generally I think I see it a bit better now.

 

 

About this late bit….

>>

>> On completion of the eform/workflow

>> . Can where the user is returned be controlled

>> from inside the workflow?

>> 

> 

>What do you mean “user returned”?  The user will be in the group and get an email that says they now have access or whatever.

 

 

I was trying to build a mental picture of the User’s UI experience.

                This part was about the end of the process. :)

                They do “X to complete the workflow” ( approve, deny, vote=Meh, etc…).

 

What UI screen/page do they “land at” after?

                Can there be an “eform” with a “Thank you for …” type message (with no buttons, they need to navigate way with the rest of the UI.) ?

                Will they be routed back to the group/folder where the workflow started? ( Maybe with an “alert message” saying “workflow complete”.)

                Back to the “Home page” of the UI? ( with no message?)

                Will it be configurable based on the workflow?

 

Which also had to do with this part too:

>> Maybe Hooks could be given a way to kick off a workflow?

>Yes, assigning the right attributes will start a workflow, so you will be able to do that

 

Will a hook be able to navigate the UI user to an eform after starting a workflow?

                Thinking of a condition like this.

                                UI User adds a Subject to a Group. ( add Member )

                                                Add Member hook looks at the UI User and decides that an approval is needed ( maybe some other users don’t need approvals, or different approvals, etc…).

                                                The hook sets some attributes. Then “redirects the user” to the eform to collect a few values (“Why are you asking for this?”) before the request is sent to the approvers.

 

--

Carey Matthew

 

From: Hyzer, Chris <>
Sent: Friday, May 17, 2019 11:39 AM
To: Black, Carey M. <>; Mailing List <>
Subject: RE: electronic forms in grouper

 

> It sounds like the “starting point” for all most all of these workflows are:

>                 A user goes to a group and goes to the ‘ more actions,

>                 should be "Electronic forms" ‘ menu option.

>                 Or

>

>                 "Join" a group could kick off a workflow too. ( A special

>                 “opt-in” type condition.)

>

>

> I think it would be generally more useful if workflows could be started

> from other “Events” too.

>                 Folder create, group create, membership add , membership

>                 remove , attribute values add/change/remove, etc

>

 

Yes, I added that to the wiki to do later

 

>

>

> Maybe Hooks could be given a way to kick off a workflow?

 

Yes, assigning the right attributes will start a workflow, so you will be able to do that

 

>                 Maybe even start a workflow from a workflow?

>                                 To allow chaining when the state of the

>                                 first workflow should start a “response/sub

>                                 workflow”( maybe to another set of people?)

>                                 Which could allow branching between workflows

>                                 that would return a “value”[ID of sub workflow] 

>                                 to the calling workflow?

 

Hmm, I guess, but we do want to keep it simple

>

>                                 Which might also allow the “10 params/input”

>                                 limit to be “10 at a time/stage”. :)

 

If there is another instance then you get 10 more

 

>

> It is not clear to me how actions/tasks would be implemented. ( AKA:

> Decide to

> “allow something” or “block it” and end the workflow. )

>                 How someone would be able to “Send an email when “X” happens

>                 in

>                 the workflow”. ( or add/remove a membership, etc

> )

 

I clarified that in the “states” config

 

>                 Again, maybe a new kind of Workflowhook fires on: State change?

>                 On params change?

 

Yes, we will have hooks in the workflow

>

>

> For the simple case of a “one page form” could an “eform” just call to an “eforms

> class” ( or gsh/jexl script?) for processing?

>                 Think “html form post action target” when the user is done

>                 supplying values.

>                 Maybe via a “message listener”?

 

Hmmm, not planning on that in the first pass, but maybe a hook could help there

 

>

> On completion of the eform/workflow

> . Can where the user is returned be controlled

> from inside the workflow?

> 

 

What do you mean “user returned”?  The user will be in the group and get an email that says they now have access or whatever.

 

Thanks

Chris

 

 

From: Black, Carey M. <>
Sent: Friday, May 17, 2019 1:57 AM
To: Hyzer, Chris <>; Mailing List <>
Subject: RE: electronic forms in grouper

 

It sounds like the “starting point” for all most all of these workflows are:

                A user goes to a group and goes to the ‘ more actions, should be "Electronic forms" ‘ menu option.

                Or…

                "Join" a group could kick off a workflow too. ( A special “opt-in” type condition.)

 

 

I think it would be generally more useful if workflows could be started from other “Events” too.

                Folder create, group create, membership add , membership remove , attribute values add/change/remove, etc…

 

 

Maybe Hooks could be given a way to kick off a workflow?

                Maybe even start a workflow from a workflow?

                                To allow chaining when the state of the first workflow should start a “response/sub workflow”( maybe to another set of people?)

                                Which could allow branching between workflows that would return a “value”[ID of sub workflow]  to the calling workflow?

 

                                Which might also allow the “10 params/input” limit to be “10 at a time/stage”. :)

 

 

 

It is not clear to me how actions/tasks would be implemented. ( AKA: Decide to “allow something” or “block it” and end the workflow. )

                How someone would be able to “Send an email when “X” happens in the workflow”. ( or add/remove a membership, etc…)

                Again, maybe a new kind of Workflowhook fires on: State change? On params change?

 

 

For the simple case of a “one page form” could an “eform” just call to an “eforms class” ( or gsh/jexl script?) for processing?

                Think “html form post action target” when the user is done supplying values.

                Maybe via a “message listener”?

 

On completion of the eform/workflow…. Can where the user is returned be controlled from inside the workflow?

 

--

Carey Matthew

 

From: <> On Behalf Of Hyzer, Chris
Sent: Friday, May 17, 2019 12:45 AM
To: Mailing List <>
Subject: [grouper-users] electronic forms in grouper

 

This is something we have had a lot of requests for and that we would like to start on soon (eforms / workflow / approvals)

 

https://spaces.at.internet2.edu/display/Grouper/Grouper+forms%2C+workflow+and+approvals

 

We discussed this briefly in the last dev call.  This is the current design (not completely fleshed out yet).

 

Please let me know your thoughts

 

Thanks

Chris