Skip to main content

Department FAQs

Frequently asked questions for the Department guide.

What events does the Department object support?​

The Department object includes several events under the Events tab in the Properties panel.

Each event is tied to a method that can be triggered during flow execution. To add a script to an event:

  1. Go to the Events tab.
  2. Double-click an event row.
  3. You’ll be redirected to the .cs code file where the corresponding method will be auto-generated.

From there, you can write custom code to execute when that event is fired.

What is the purpose of the Department object?​

The Department object is used to store a department value within a workflow. It can be initialized with a fixed value or dynamically set during the flow runtime.

The object serves as a data holder and does not participate in routing. No outgoing or incoming connections should be drawn to or from the Department object.

It can be used together with:

  • Assignment object to set its value,
  • Comparison object to check its value.

Is it safe to leave the Department object unconnected?​

Yes, it is safe and correct to leave the Department object unconnected.

The object is purely for holding department data and should not have any incoming or outgoing arrows in the workflow. It is not a step in the flow, but rather a variable holder.

Missing configuration will be indicated with a red warning icon on the object. Hovering over it will display the validation issue.

How do I configure the Department object?​

  1. Click on the object to open the Properties panel.
  2. Under the Value section:
    • Type: Select either:
      • Static Department: Choose from a list of predefined departments in the system.
      • Flow Starter's Department: Automatically uses the department of the user who initiated the flow.

Once selected, the chosen department value will be stored in the o