Fieldcode Manual

Tip: You can use filters for better results

On the left side of the Workflows designer, there are the Workflow Parameters tab and the Validations tab. In the Workflow Parameters tab, you can view the various workflow parameters of the currently selected workflow. In the Validations tab, you can check the functionality of your currently selected workflow.

In the Workflow Parameters tab, you can view the individual properties of the currently selected workflow. Below, we will go through each of the fields and learn more about their individual meanings.

The name of the currently selected workflow.

Click on image to expand/minimize

The version of the currently selected workflow.

Click on image to expand/minimize

The object used in this workflow.

Click on image to expand/minimize

The trigger used in this workflow.

Click on image to expand/minimize

The projects that should use this workflow.

Click on image to expand/minimize

The short/long description for this workflow.

Click on image to expand/minimize

The option to clone this workflow (and insert this clone into the workflow table).

Click on image to expand/minimize

In the Validations tab, you can fix your workflow errors/warnings by, for example, adding more objects, following the object path to fix your error/warning, and you can refresh the view anytime to check if previously detected errors have been fixed.

The Validations tab lists all workflow errors and warnings and also gives you the option to fix/understand the problem for individual objects.

The refresh button right next to the general errors/warning section re-checks for general errors/warnings.

On the lower Errors/Success section you can as well re-check for problematic objects, and, you can additionally add other objects directly with the Plus button.

Click on image to expand/minimize

You can expand the general error/warnings section by clicking on the expand arrow to check error/warnings in general and/or expand the Errors/Success section to rather check individual objects.

Click on image to expand/minimize

Let's take a closer look on a general error. In this case, we got a button condition invalid error. You can check individual error explanations here to be better able to troubleshoot.

With the Open this node button on the upper right you could now directly switch the Middle Pane and Right Pane view to switch to the affected node to be able to directly troubleshoot the affected node.

Click on image to expand/minimize

Let's take a closer look at an object error. In this case we got an unexpected error. You can check individual error explanations here to be better able to troubleshoot.

With the Open path button on the upper right you could now directly move over over to the path for the affected object.

Click on image to expand/minimize

The path view displays you all the paths the object went through until now. You can check the other paths to troubleshoot by clicking on the Open this node button of an individual item.

In this view, you can also check the current test coverage for All nodes and New nodes in particular. Your goal, of course, should be, to have them all green to be confident about the integrity of your workflow.

Click on image to expand/minimize
ErrorExplanationTroubleshooting
Invalid destinationThe destination path behind a button, automation, or guide does not exist in this version of the workflow.Replace the invalid target path with a valid one or delete the button, automation, or guide if it is obsolete anyway.
Quick launch formThe button is displayed to open a Quick Launch form, but the target path does not have a form configuredSet the Quick Launch configuration to false or add a form to the target path.
Autodestination loopThe configuration of autodestinations can lead to an endless loop.
Condition loopThe configuration of conditional destinations can lead to an endless loop.
Invalid pathThe path is invalid or no longer exists in this workflow version. Open the node and remove or update the wrong path.
ButtonThe condition to show or not show a button is invalid.Please correct the condition.
Jump node configurationDepending on the message several reasons can apply:

- a jump node is not allowed to have any buttons, auto destinations or conditions
- a jump node is not allowed to have child nodes
- a jump node needs to be placed in a jump node context .../jumpNodes/
- a jump node is not allowed to be used beside of buttons (no conditions, no autoDestinations)
Automation conditionPredicate/Filter condition is missing.Please add or remove a filter condition.
Invalid action configurationMandatory field validation:
- Missing automated action reference
- Missing outbound mapping reference
- Missing snapshot parameter
- Missing fields to get
Please select or add the missing parameter from the list or remove the action.
Missing button destination pathMandatory destination path is missing.Please add a destination path from the list or remove the button.
Was this topic helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
How can we further improve this topic?
Please provide the reason for your vote. This will help us improve this topic.
Navigation