Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

We at SaaSJet know how important it is to have a flexible business process.
The critical thing about the effective Process workflow is that it should adapt to its current conditions .
The whole concept of the BPM add-on is based on forms users can build and assign to required people in the organization. Those forms will be added to the Jira issues once the Process Startsbe flexible.

The problem is that all forms (Jira issues) have been created in sequential order.
In other words, if the Process has Step A, Step B, and Step C, the system could not avoid assigning Step B if it’s unnecessary.We’ve solved this drawback with the Conditional Step functionality.
The Conditional Step is a typical BPM Step, but it Conditional Step functionality solves the problem with sequential order of issues creation and can be triggered as an action of Form logic only.For instance, if the user has the “App access request“ Step and form element “Select your role“ and options like Admin, Contractor, Partner.
If the Process requires additional actions from partners to obtain access to some app, then the Conditional Step can be set here as extra work for those who need the partner access.

To do it, create the simple Step with the “Select your role“ element.

...

Then create the Conditional step with the additional form, the partner should complete.

...

As an assignee select the dynamic option - Assignee from triggered issue.

It includes almost the same settings as the Steps: 

  • Form elements. Build the form using typical form elements on the Form workspace. E.g: Text field, area, dropdown, and multi-selector. Every element has its own settings. Read more

  • Project and issue type. So use it to include the form in a specific project.

  • Assignee. Select the exact person or group of users the form will be assigned to. Read more
    Also, in the Conditional Step, in addition to the simple Assignee list, you can set the Assignee from the triggered issue. So, when the option of Step Form element after submission will run the Conditional step it will set Assignee from the main Step that selects this option.

    Image Added
  • Form Logic. Build really flexible Templates with when/then logic. Read more

  • Submission action. Automatically moves issues through the workflow. Read more

    Image Added

Instruction on how to work with Conditional Step

  1. Create Process and then Step and Conditional Step in it.

  2. For the Conditional Step add the Forms element and set Project, and Assignee - Assignee from the triggered issue. It will assign the same person who has submitted the

...

  1. Step form.

...

Back to previous step and Set the logic that will Start assign a form from Conditional step only to those who has selected the Partner option.

...

That’s it.

Make your process flexible with the Conditional step functionality.

Read more about BPM facilities:

How does BPM work

Conditional logic of Form

How does the Approver step work?

...

  1. Image Added
  2. For Step add the Forms element and set Project and Assignee. And don’t forget to add one of the multi-choice elements (dropdown, multi-choice, checkbox, radio button) then set Form logic.

    Image Added
  3. Save the Template, so all new Processes started will support the recently added settings.

  4. Once the option in the multi-choice element is selected and the form is submitted the Conditional Step will start and be assigned to the user who submits the form in Step.

Info

Questions? Just email us to get an answer support@saasjet.com.

...