Question

Photo of Frank Grand

0

Help with "External Inquiry" type of Workflow

We are playing around with a "follow up" workflow for care visits.  What we want to happen is capture info and then filter the workflow by Campus and assign to the appropriate worker.

We basically copied the External Inquiry Workflow and modified some of the attributes we capture in the form.  Our problem is that our actions that test for which campus is selected aren't working, when I look at the log, the message I get is "Criteria test failed.  Action was not processed. Processing continued"

Here is the attribute:

So since the attribute is linked to a campus, the person filling out the form gets a dropdown of our campuses.  Here is the action where we test for one campus:

I'm assuming that maybe typing in the Text Value: Anderson is where the problem is, but I can't figure out how to get it to work.

 

Anyone seen anything like this before?

  • Photo of David Turner

    1

    Yes, since the action filter currently only gives you the option of entering a text value, rather than displaying an appropriate control based on the attribute's field type, you need to have some knowledge about how the selected attribute stores it's value. A campus attribute stores it's value as the campus guid.  So you'll actually have to enter the guid for the campus you're testing for. To get that, you can run the following SQL query:

    SELECT [Name], [Guid] FROM CAMPUS
    • Frank Grand

      David, I changed "Anderson" to "6246DDEF-8AC9-4C25-B011-430CEE590F0F" in the action (I looked up the guid) and it still fails, is there some kind of formatting I'm missing? Should I be using Equal To?

  • Photo of David Turner

    0

    You should use 'Equal To', and the compare should be case-insensitive. You could always add an action right before this one that writes the current 'raw' value of the selected campus (to verify what is being stored in that attribute value. Here's an example...

    2015-03-25_141438.png

  • Photo of Frank Grand

    0

    David,

    We are revisiting this issue and are still seeing issues.  After writing the guid to the log, I've confirmed that we are testing for the right value and it still fails.  Any other suggestions?