Trigger Workflow in Campaign V6 | Community
Skip to main content
alicep47308254
alicep47308254
Level 3
November 6, 2017
Solved

Trigger Workflow in Campaign V6

  • November 6, 2017
  • 8 replies
  • 4530 views

Hello team,

I am working with some Trigger Workflows.

After I chose Trigger Campaign I want to exclude from a workflow all the Receipients who have received other Triggers Campaigns.

There is the possibility to do that?

I can't find a Folder with all the Triggers Campaigns.

Regards

Alice

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by christophec3473

Hi,

The goal is to design a workflow with a main target and the target to exclude. This target corresponds to recipient from delivery whose the typology is Trigger. In my example, it will be defaultTypology

We need to parameter our query (nom interne de diffusions égal...).

Open it and clic on the button (red square)

Select BroadlogRcp

This table content all recipients having received previously a message

Clic on delivery (red square)

In the delivery schema, open typology and select your criteria (@label...@name)

You obtain your query

Now you can finish your workflow.

It's ok?

Christophe

8 replies

florentlb
florentlb
Level 10
November 13, 2017

Hi Alice,

I'm not sure where this information is stored in the database. I'll check that (should be somewhere related to some deliveries or campaigns' table).

Florent

alicep47308254
alicep47308254Author
Level 3
November 13, 2017

Hello Florent,

It will be great If you could check this. I want to exclude all the triggers campaigns from a workflow and I need something quick without excluding every campaign or every workflow.

Thanks

Alice

    christophec3473
    christophec3473
    Level 2
    December 15, 2017

    Hi,

    You can add a filter rule where broadlogRcp/delivery such as typology.@name = "Trigger".

    It's an idea.

    Or you give always the same beginining of name to your campaign with Trigger "Trigger_XXXXX", "Trigger_YYYYY" and after you can design a rule easier to build and using this field delivery.@label.

    Christophe

      alicep47308254
      alicep47308254Author
      Level 3
      January 2, 2018

      Hi Christophe,

      I have the English version of V6 put I can't find in broadlogRcp/delivery che field Name or Typology Name.

      I have Internal Name but I have already checked is the OPXXX that I find when I create a new Campaign.

      Let me know If you have any other suggestion for me to find the Trigger Deliveries. It will be very helpful for me to exclude all of them with only a simple Query

      Alice

      christophec3473
      christophec3473Accepted solution
      Level 2
      January 3, 2018

      Hi,

      The goal is to design a workflow with a main target and the target to exclude. This target corresponds to recipient from delivery whose the typology is Trigger. In my example, it will be defaultTypology

      We need to parameter our query (nom interne de diffusions égal...).

      Open it and clic on the button (red square)

      Select BroadlogRcp

      This table content all recipients having received previously a message

      Clic on delivery (red square)

      In the delivery schema, open typology and select your criteria (@label...@name)

      You obtain your query

      Now you can finish your workflow.

      It's ok?

      Christophe

        alicep47308254
        alicep47308254Author
        Level 3
        January 3, 2018

        Hello Christophe,

        thank you for help. I finally find the field @name .

        Just a last question. In the Value you put defaultTipology because you named the Triggers like that? Or you are using this just as an example?

        Alice

        christophec3473
        christophec3473
        Level 2
        January 3, 2018

        It's just the default name of the default Typology. So it's just an example.

        Christophe

          alicep47308254
          alicep47308254Author
          Level 3
          January 3, 2018

          Thank you Christophe for your help

          Alice

          Terms & ConditionsAccessibility statement

          Loading footer...