Learn by example

This page provides some of the ideas we had for Core Workflows. Of course you can build much more complex workflows.

Hinweis

If they don’t make sense to you, don’t worry—just skip ahead to How do they work? to learn about all the options in detail, then come back here to see them in action.

All following workflows have the same base configurations. The workflow may not use them all.

  • Groups
    • Sales

    • Support

    • 2nd Level

  • Attributes
    • Category (Tree-Select, not mandatory, agents only)

    • Approved (Boolean, not mandatory, not shown, false as default)

    • Operating System (Text, not mandatory, not shown)

    • Software used (Select, not mandatory, not shown)

  1. Group specific values and fields

    This workflow set depends on the category field. It reduces the available set of values based on the group selected.

    This reduces the category options to 2nd Level/*, Internal/* and Others. It also sets further required fields to mandatory and visible.

    Sample workflow that shows specific values and fields for 2nd level
    The Result

    This is what the agent would experience with the above workflows in place.

    Workflow shows objects and limits options based on selections on the group
  2. Approval process

    In this case approved is visible to agents by default. For this workflow, an additional role Approval person is required (no further permissions).

    Sample workflow that restricts an approval attribute to specific roles

    Tipp

    This workflow may work best in combination with a trigger but technically, this is not required.

    Select fields may be a better approach because they allow more values than just a simple true or false.

    The result
    Workflow fixes possible values of "Approved ?" to a specific selection depending on the users role
  3. State dependent mandatory fields

    This workflow sets Category to mandatory if the agent wants to set the states closed or pending close to enforce categorization.

    Sample workflow that sets fields to mandatory on specific states
    The result
    Workflow sets category field to mandatory upon choosing closed or pending close as state