Ideas

Updates to workflow behavior when manually triggered from Connection Requests

8

Login To Vote

Updates to workflow behavior when manually triggered from Connection Requests

Connection

The same workflow that is triggered from the Person Profile Action menu vs from a Connection Request will behavior differently in 2 specific scenarios.

Scenario #1: The workflow processes such that it needs to use the Workflow Entry Show HTML action to display a message to the user. When triggered from Action menu the user will see the message. But when triggered from Connection Request the user will NOT see the message.

Scenario #2: The workflow is setup to NOT auto persist, requires the passed Entity for processing, and has a user entry form to confirm or gather info based on Entity. When triggered from Action menu everything will work as expected. But when triggered from Connection Request - the workflow will FAIL because the require entity is NOT available. 

For more details on all of this - please see this github issue and this rocketchat conversation.

We would propose that Rock should be designed so that workflows should have the same basic behavior/capability for each of these 2 scenarios regardless of how they are triggered.

Photo of Stan YoderSubmitted by Stan Yoder, The Crossing  ·   ·  Connection
Remove Votes
Login to add a comment...

Submission Success Tips

Cultivate your ideas for maximum impact with these helpful submission tips that will increase the chances of your brilliant concepts becoming reality.

  • Clear Title: Craft a straightforward and descriptive title that instantly conveys the essence of your idea.
  • Concise Description: Provide an idea description that is succinct, ensuring it effectively communicates the concept without unnecessary verbosity.
  • Provide Additional Details: With a concise description complete, now provide any other details that are needed to better understand the requirements.
  • Thorough Ministry Need Review: Provide a comprehensive overview of the ministry need your idea addresses, emphasizing its significance.
  • Cover the WHY: Clearly articulate the rationale behind your idea, explaining why it's essential and how it aligns with the organization's goals and mission. Oftentimes a clear "why" sheds light into other possible options.