Automate

 View Only

  • 1.  How do you add a step in an Evolve Workflow to route a Data Posting with Errors Message

    Posted 10-03-2024 13:55

    I am trying to use the Status field to add a decision to my workflow that if a Data Posting with Errors message is received after the Automate Update plugin that it will send to a person for review otherwise close the request. I am not having any luck. I have also tried to use the script log field within my form to accomplish the same thing when the log field begins with "Err:".

    How can this be accomplished in Evovle?



    ------------------------------
    Ann Davis
    Technical Data Analyst
    ------------------------------


  • 2.  RE: How do you add a step in an Evolve Workflow to route a Data Posting with Errors Message

    Employee
    Posted 10-03-2024 14:12

    Hi Ann Davis,

    you can make use of the match function in the workflow. Refer screenshot attached below :

    For testing I am setting the field with a value setter, in your case it will be coming from 'Automate Update' plugin.

    I have attached a copy of the solution over link : https://nowtransfer.de/4e142bff46b1

    Hope this helps.

    Regards



    ------------------------------
    Hammad Naeem
    Precisely Software Inc.
    ------------------------------

    Original Message


  • 3.  RE: How do you add a step in an Evolve Workflow to route a Data Posting with Errors Message

    Posted 10-03-2024 15:04

    Thanks for the pointer. It worked.



    ------------------------------
    Ann Davis
    Technical Data Analyst
    ------------------------------

    Original Message


  • 4.  RE: How do you add a step in an Evolve Workflow to route a Data Posting with Errors Message

    Posted 09-23-2025 16:46
    Edited by Ann Davis 09-23-2025 16:46

    Hammad

    I have been using this method successfully for fields since you brought it to my attention. I now have a repeating table and unless the error is in the first line it is not triggering the error approval. Is there a way to make this work in a repeating table scenario also?



    ------------------------------
    Ann Davis
    Technical Data Analyst
    ------------------------------

    Original Message


  • 5.  RE: How do you add a step in an Evolve Workflow to route a Data Posting with Errors Message

    Posted 09-24-2025 08:59

    Co-Pilot found the Promote Logfield with Merge Functionality and it worked

    1. Promote the Logfield with Merge Functionality
      • In your form design, promote the repeating logfield to a solution field.
      • Set the "Promote to SharePoint (Function)" property to "merge". This will concatenate all logfield values from the repeating table into a single string.
    2. Use the Match() Function in Workflow Conditions
      • In your workflow decision node, apply the Match() function to the merged field.
      • Example formula:
      • This checks if any row contains the substring "Err", which is commonly used to indicate an error in log output.
    3. Trigger Notifications or Routing Based on Match Result
      • If the match returns true, route the workflow to notify the originator or take corrective action.
      • If false, proceed with normal completion.


    ------------------------------
    Ann Davis
    Technical Data Analyst
    ------------------------------

    Original Message


  • 6.  RE: How do you add a step in an Evolve Workflow to route a Data Posting with Errors Message

    Employee
    Posted 09-24-2025 12:50
    Edited by Sigrid Kok 09-24-2025 12:50

    Hi Ann

    Hammad's suggestion could work.  I have also used counts for tables - # rows, # posted and # errors. It uses the count function - noting the field name - not field value - for the log message and optionally the regex to search for something in the log field to find a match, and it's optional.

    Here's an example of how you can use part of the post success message to count those posted - you would want to adjust the search string like 'saved' to whatever success means:

    • count('/my:myFields/my:BPCustSales/my:BPCustSales_Input/my:Repeating_Content/my:LogField_CustSales','saved')

    Here's an example of catching error counts

    • count('/my:myFields/my:BPCustSales/my:BPCustSales_Input/my:Repeating_Content/my:LogField_CustSales','Err')

    And total row counts without a string to search for

    • count('/my:myFields/my:BPCustSales/my:BPCustSales_Input/my:Repeating_Content/my:LogField_CustSales')

    I have the rule that sets the counts to run on form load.

    You can then use the counts to route the workflow or stop a user from progressing depending on whether it's interactive or not.  

    Hope this gives you another idea,

    Sigrid



    ------------------------------
    Sigrid Kok
    *Precisely Software Inc.
    ------------------------------

    Original Message