Event Triggers and Process Arguments - arguments disappear

Based on the Event Arguments section in the documentation below, I created an Argument UiPathEvent. The instant I created the argument it disappeared from the Arguments panel and I cannot see it in Data Manager either. If I try to create it again, it says it already exists. I am able to use it in expressions etc.

I confirmed that the arguments do not exist in some hidden way, you do have to create them.

I tried creating the argument in Data Manager and it also disappears immediately.

Is this normal behavior? Seems odd to have arguments that exist but you can’t see, kind of a black box.

If you want to know the actual connector, event, record type, or record that triggered the process in your workflow, define the following input arguments of type String in your process. Integration Service populates them automatically when it starts the job:

  • UiPathEventConnector - Determines which connector started the automation.
  • UiPathEvent - Determines the type of event that occurred.
  • UiPathEventObjectType - Defines the specific record type resulting from the event.
  • UiPathEventObjectId - Provides the unique identifier for the object involved in the event.

@postwick

this is normal behaviour and it is mentioned in same doc as well

cheers

Seems like poor design to me. They should be visible but locked so they can’t be edited.

You dont actually need to add them in that much anymore. If you drag the trigger activity, like email received, or queue item add, into the workflow, it adds those arguments for you silently and automatically.

I agree they should be visible though and raised as such in the past. Especially since you can see them if you try to invoke that workflow (which doesnt really make sense architecturally I think unless you are mocking, but still.)