Workflow warnings & system messages

  • Workflow warnings & system messages

    Posted by Paul Pollock on March 20, 2024 at 3:37 pm

    Scenario 1: A workflow version was created in UAT and then exported to be used in a lower tier environment for continued testing. UAT environment we were using was being utilized for 10.0.39 update testing. When importing the workflow to use for testing, a warning message was prompted on the Worflow versions pane. The workflow imports as expected, but the warning is thrown during the “Make active” validation.

    Warning message: “Project distribution for the participant token Operating expense should be filled in.”

    The workflow is using a Managerial hierarchy for assignment and is not trying to assign the work item to a Financial dimension owner and the company is not using Project distributions. When comparing the two environments side by side, the Expenditure Reviewers for “Operating Expense” were configured the same.

    Scenario 2: The same workflow was imported into another (tier 2) environment and the workflow imported and activated as expected. Made it further this time thinking maybe it’s a tier 1 vs tier 2 environment issue, but the system message came up at the time when the Worflow button on the purchase requisition was selected.

    System message: The system cannot determine which workflow to run. Review the conditions in the “Set condition for use” area for each workflow that is based on the Purchase requisition reivew type.

    However, the workflow imported and was “activated” so there shouldn’t be any confusion on what the system should be using. I even went as far as deleting any other versions in the environment and the system message still popped up so the system only had the one version to use.

    Zvika Rimalt replied 2 months ago 2 Members · 7 Replies
  • 7 Replies
  • Zvika Rimalt

    Member
    March 20, 2024 at 9:34 pm
    Up
    0
    Down Accepted answer
    ::

    for scenario 1, first troubleshooting step I would do is try to import the workflow back into the environment from which you exported it, to try and rule out the workflow itself is corrupt somehow and this is not a particular environment specific issue.

  • Zvika Rimalt

    Member
    March 20, 2024 at 9:37 pm
    Up
    0
    Down
    ::

    For troubleshooting scenario 2, if you delete all other workflows of the same type, do you still get the error message?

    If not, check the activation condition you have on the workflow configuration. (it’s on the “basic setup” section when you open the configuration using the editor)

  • Paul Pollock

    Member
    March 21, 2024 at 8:04 am
    Up
    0
    Down
    ::

    Importing the workflow into environment where it was created was also attempted and the workflow and purchase requisition process worked as expected

  • Paul Pollock

    Member
    March 21, 2024 at 8:04 am
    Up
    0
    Down
    ::

    All parts of the workflow were reviewed and confirmed to be configured correctly.

  • Paul Pollock

    Member
    March 21, 2024 at 8:05 am
    Up
    0
    Down
    ::

    Yes, all other workflows were deleted and still get the error message.

  • Paul Pollock

    Member
    March 21, 2024 at 8:08 am
    Up
    0
    Down
    ::

    Also manually recreated the workflow in each environment after the import process produced the error message.

  • Zvika Rimalt

    Member
    March 21, 2024 at 8:54 pm
    Up
    0
    Down
    ::

    It sounds like there is something corrupted in the environment where you are trying to create the workflow… try to call in the technical heavy weights…

    Obviously the easy step is to refresh the environment with new copy of data…

Log in to reply.

Welcome to our new site!

Here you will find a wealth of information created for people  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!