Hi Ben. We've been on Resilient since prior to Workflows introduction and are on V43.1.49 now as a SaaS userbase. Once WF were added we started using them this way.
See below for an example of what we previously used in Workflows and what I'm trying to replicate. Default conditions aren't required.
1) Exclusive gateway with two options. Within the first task is an Incident Object field.
2) The condition emanating from each branch has 3 total options but I only want 2 valid ones. Yes or No. "-" is not applicable.
3) If the task is attempted closed before the field is populated as needed, the "Error during Workflow" comes up. This is what we use to turn an optional field to a conditional requirement within a Workflow.
A version of this is what we need in Playbooks. Otherwise I'd be forced to have blank options as a valid option. This is not applicable to many use cases. Rather than rewrite those to accommodate the application, the Playbooks should allow for that modification. A use case requiring an answer prior to movement is a common occurrence.
If I can't do this by inherently created functionality, I'd like to know why and what I can do about it.
------------------------------
Patrick Conroy
------------------------------
Original Message:
Sent: Mon February 14, 2022 09:03 AM
From: Ben Lurie
Subject: Using Else Condition Points in Playbooks
I wanted to see what happens with a workflow with no default flow out of a condition point. I went back to v36 (which is the oldest I can access) and still that version requires a default flow out of the workflow. What version are you using?
I still believe that workflow/playbook with a default condition can meet the use case. Unfortunately I don't have a system to test the old behavior on.
What is the behavior on your system when the task is closed but none of the conditions match?
You can export the settings and send them to me or post them and I can try that.
Ben
------------------------------
Ben Lurie
Original Message:
Sent: Wed February 09, 2022 08:51 AM
From: Patrick Conroy
Subject: Using Else Condition Points in Playbooks
Hi Leonardo yes that's right. Conditional Required Fields. I've had an RFE open for that for a few years, but it was a bit moot since Workflows give you a de facto way to resolve my concern. With Playbooks I'm trying to figure out how to do that as well.
------------------------------
Patrick Conroy
Original Message:
Sent: Wed February 09, 2022 07:03 AM
From: Leonardo Kenji Shikida
Subject: Using Else Condition Points in Playbooks
Hi Patrick
Just as Ben, I also think an example would help us to understand your demand.
If i've got it right, the key here is
"The field is optional but in this playbook it is not"
It seems that you want to control if a task field is mandatory or not based on some logic.
And then, you can make it work using a workflow, but not using a playbook.
Is that correct?
------------------------------
[]
Leonardo Kenji Shikida
Original Message:
Sent: Mon February 07, 2022 03:20 PM
From: Patrick Conroy
Subject: Using Else Condition Points in Playbooks
Hi Ben,
This issue isn't the usage of Else as a condition, but my need to not use it. I want to force a user down a path in a task. That task will have a incident object field that needs a value input. I'd prefer a conditional requirement that makes the user perform an input. Without that however I create a condition that states Field "Example" Needs Value "A," or "B." The field is optional but in this playbook it is not. I have done the same with gateways in Workflows previously. However if my condition is A or B, that's all I want to put down. It appears I am forced as well to add an out clause for Else as a default, which I don't want to do. How would that instance be resolved?
------------------------------
Patrick Conroy
Original Message:
Sent: Mon February 07, 2022 08:18 AM
From: Ben Lurie
Subject: Using Else Condition Points in Playbooks
This is definitely possible with playbooks. Here is an example:
Ben
------------------------------
Ben Lurie
Original Message:
Sent: Fri February 04, 2022 11:50 AM
From: Patrick Conroy
Subject: Using Else Condition Points in Playbooks
My team is on V43.1.49 and attempting to utilize Playbook Designer's Condition Points. My goal is to create a condition point that includes an object select field or multiselect field, and if the value of that field is null when the task is closed, the playbook will refuses to move forward without a value. This was an option in Workflows, but I am unable to replicate so far due to the lack of an "Else" default option. Does anyone have the documentation source that can assist me in addressing this issue?
------------------------------
Patrick Conroy
------------------------------