Hi,

We are using Opalis to automate the creation of Remedy tickets from emails. We use the "Read Exchange Email" and "Create Remedy" options and it is working, however we would like it to alert us if the Create Remedy stage fails.

When we use the link from "Create Remedy" to "Send Exchange Email" and select it to include "Create Remedy equals failed", it passes them on but we then receive multiple emails for each failure: If only one email goes through we get one email. If two emails fail we get four alerts. If three emails go through we receive nine alerts etc. It seems that we receive an email for each item, duplicated for each item in the bus.

Any idea where we're going wrong? We're really struggling to get to grips with Opalis so any advice would be gratfully received.

Many thanks,

Ian

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan Horz Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi,

well it's all as designed told me, there is even a opalis (internal) document about it called "White Paper - Multiplication Effect In Policies"
But in the short way, you can use the wait object (legacy), the junction object or within your object use the option published data behavior (option run behavior) to solve this behavior

Also take a look at the following link:
http://www.networkworld.com/community/blog/opalis-runbook-automation-fundamentals-part-1

look for the word 'FLATTEN"

• Proposed as answer by Stefan HorzMicrosoft community contributor Friday, November 08, 2013 6:37 AM

Hi Ian,

is this already solved? If not: Can you also check if you have a double link (two links) between "Create Remedy" an "Send Exchange Email" (Attach to another object or delete, "Undo check out" if not).

Regards,

Stefan