Agent Desktop

Get Involved. Join the Conversation.


    Jens Lundell
    Managing Complex Workflows - Dynamic Agent Desktop recipe
    Topic posted September 1, 2017 by Jens LundellSilver Crown: 22,500+ Points, last edited December 5, 2019 
    697 Views, 1 Comment
    Managing Complex Workflows - Dynamic Agent Desktop recipe


    Managing Complex Workflows

    Author: Jens Lundell
    Oracle Service Cloud
    Sr. Development Director

    Difficulty rating: (Intermediate)
    Target persona: Workspaces administrator creating workspaces and workflows for agents
    Ingredients: Desktop Workflow
    Overall description/purpose: As you create more and more complex Desktop Workflows you may notice that they become cluttered and hard to understand. Looking at a workflow created by someone else may be very confusing and even following your own workflow after your summer vacation may be hard.

    In this video, we discuss various techniques for cleaning up your workflows to make them smaller, easier to understand, and easier to maintain. Specifically, we learn:

    1. How to delete unnecessary elements
    2. How to move around elements to prevent overlapping connectors
    3. How to size certain elements to make them easier to read, and provide more space for their connectors
    4. How to reduce dead space in workflows by moving elements closer, reducing the need to scroll back and forth to see the whole workflow
    5. How to delete redundant connector labels
    6. How to edit element labels to make them easier to read
    7. How to edit connector labels to make them shorter, easier to read, and less cluttered
    8. How to move connectors’ elbows to prevent connectors from overlapping
    9. How to change connector types to suit your personal preference, and prevent connectors from overlapping
    10. How the Workflow element works
    11. How to extract elements from an existing workflow into a nested workflow. This can be done in order to reduce the complexity of the outer workflow and for allowing the nested workflow to grow without affecting the outer workflow.
    12. How to use the Return element to create different exit points for a nested workflow, which an outer workflow can use as branching points.

    Video: Click to View Video
    Attachments: Attached is a Workflow export file with the final workflow created, which contains the nested workflow. Import using the instructions here. After importing you will have to change the Category decision element to use Categories on your own site.





    • JustRhianna

      I am trying to create a workflow that creates multiple child incidents if multiple list box values are selected when a button is pushed. It has been a while but man it is giving me a headache