nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

AND and OR

kaalraa

I am facing a problem in workflow condition as such:

We have to generate a dynamic workflow having approvals task (CGITASKS) for different approvers. After approval task the workflow has to transitioned to the next task which happens to be the deployment on a particular date and time as provided by request manager while initiating the workflow.

If there are three approvers the tasks are to be task A, task B and task C, and all three must complete there job in order to transition the task which means and AND task is required. The next transition has to be deployement on timeout which means there is a need of a DummyTask for timeout.

Now the output for pred activation of dummy task we are getting is as follows
<or>
<and>
<task A>
<task B>
<task C>
</and>
</or>

We just dont want to be <or> tag out there as logically it has no meaning. Any suggestions are all welcome.

~ aks

Find more posts tagged with

Comments

Adam Stoller

What you didn't state - but which one might assume from your post - is that you are using Workflow Builder - yes?
The short solution is - don't use WFB.
The longer solution is to make sure your diagram correctly reflects just the AND scenario - and if so, file a bug with IWOV - and *maybe* it will get fixed in a timely manner (I personally think that WFB support will probably be going away in favor of the new system that [I believe] they will be releasing with 6.7.1)
The medium solutions is like the long solution - except it assumes your diagram was incorrect which is what caused the problem - fix the diagram and [hopefully] the generated WFT code will also get fixed.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

kaalraa

Thanks Adam... I am using WFConstructor for the generation of the workflow and that could be the only reason through which i am getting the kind of output as i mentioned earlier.

But still i will look out as how i can improve on my design for implementing the AND task in between external tasks and an dummy task.

~ aks

Adam Stoller

Okay - you're using WFconstructor (this is good - practically a "best practice")
Are you creating 'logical' tasks to use for the 'and' condition?
Can you show us the code for the declaration of the tasks and the linking of those tasks where the problem occurs?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

kaalraa

Adam,

Attached here is the snippet of the code which defines about the series of external tasks >> and task >> dummy task >> external task. I hope you help me out in order to remove the extra <OR> tag from the output of the code i am generating.

~ aks

kaalraa

Forget to put up the attachment

~ aks

Adam Stoller

You have two logical tasks defined:
- "and_CG" with name "and"
- "and_Deploy" with name "and"
You're linking all Approve_Content_For_DEV_PREPROD_* tasks to the and_CG task and all Approve_Content_For_PROD_* tasks to the and_Deploy task, and then the and_CG is linked to Dummy_Task_Content_Generation and and_Deploy is linked to Deployment_Time_Check

It *looks* right - this might be a 'bug' in WFconstructor - you may want to contact Support about it if nobody else has any ideas (don't have time to try this out right now - sorry)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

kaalraa

Thanks Adam.... but just want to know whether there would be any impact on the working of the workflow with <or> tag without any task within it?

~ aks

jbonifaci

The following should work as an and only:

<or>
<and>
<task A>
<task B>
<task C>
</and>
</or>

The and will not be treated as an or. So if that was your concern, it is not an issue.

~Jeff

kaalraa

Cheers Jeff !! It gives me a sound sleep for tonight.

~ aks