SoftEXIT Micro-Workflows™ — Video Transcript

0:09
SoftEXIT Micro-Workflows™ are a simple way to make your business applications respond intelligently to the information your users enter. Instead of showing every field or requiring information before it makes sense, Micro-Workflows let your forms adapt to the business process as it happens.

0:27
Let’s look at this customer service case and compare a traditional required field with a SoftEXIT Micro-Workflow.

0:34
We’ll start with Contact. This is a traditional required field. Every customer service case needs a contact, so there’s no reason to make this conditional. The user simply has to provide a contact before the record can be completed.

0:49
But real business processes aren’t always that simple. Sometimes information is only required under a particular condition. Making those fields permanently required could actually prevent users from creating a record when the information doesn’t exist yet.

That’s where SoftEXIT Micro-Workflows become especially useful.

1:09
Here, Category normally gives the user several predefined choices. When one of those choices applies, no additional explanation is necessary.

1:19
Now watch what happens when I select Other. The form immediately reveals an additional Description field. That’s a SoftEXIT Micro-Workflow.

The form responds to the data being entered and only asks for more information when that information is relevant.

1:35
Choose another category and the additional question disappears. We aren’t forcing every user through fields that don’t apply to them.

1:43
The Status field gives us an even better example of why Micro-Workflows matter.

1:48
When a case is New, Open, or In Progress, there is no resolution yet. We can’t require a Resolution or Resolved Date when the case is first created because that information simply doesn’t exist.

2:02
But when I change the Status to Resolved, the Resolution Details section immediately appears. Now the Resolved Date and Resolution become required because we’ve reached the point in the business process where that information should exist.

2:16
The user can’t complete the resolution without providing the information the business requires. But those same requirements never prevented us from creating or working with the case earlier.

2:27
Move the case back to an Open status and the section disappears. Set it to Resolved or Closed and it becomes relevant again.
The form follows the business process instead of forcing the business process to fit the form.

2:42
So, how complicated was it to build those SoftEXIT Micro-Workflows? Let’s switch to the editor and take a look.

2:49
Here is the entire Category Micro-Workflow. I select the row, enable Conditional Visibility, and tell Studio to show it when Category equals Other.

That’s it.

2:58
The Resolution Micro-Workflow works the same way. This entire section becomes visible when Status equals Resolved or Closed. The required fields inside the section then enforce the information we need at that stage of the process.

3:14
In many application platforms, even small behaviors like these can lead to separate workflow designers, flowcharts, automation rules, formulas, scripting, or custom code.

SoftEXIT Studio keeps these small business rules directly on the form elements they control.

3:32
That’s the idea behind SoftEXIT Micro-Workflows™.
Small, focused rules that let your application respond intelligently to the business process without turning every requirement into a development project.

3:46
Build the application around the way your business actually works with SoftEXIT Studio.