Process Model Lane Assignments

Background:  We do not use tempo or user tasks in our application.  All our objects are deployed to higher environments under a service profile.

We are having a discussion on best practice for swim lane assignments, here are the two thoughts:

1. All swimlanes should be set to run as designer.

2. All swimlanes should be set to run as initiator unless elevated privileges are needed.

I'm in camp #2.  I don't believe process models should be set to run as designer.  Our service profile has Appian Admin access and therefore should only be used on a limited basis.

While I'd like to hear opinions on this, if anyone has links to Appian recommendations, that would be even better.  Seems like "best practice" is thrown around too freely without official documentation and based more on personal preference.

Thanks

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    I don't use swim lanes at all until and unless I have a specific reason to use them.  Usually this is involving task assignments which would need to remain consistent in a lane, and sometimes it's more about visual flow organization (though that can turn into too much of a pain in the butt very quickly).  In the latter case, which sounds like it applies to you, I don't see any particular reason to set any lane-specific permissions.

  • I'll use swim lanes regularly, but not often for node assignments.  Mostly just for a visual in /design.  Especially with Tempo/SAIL, it's much less common these days that I have to chain tasks for the same assignee or route a process back to a different task for the same assignee (multiple nodes in a lane with the same assignment).

    The only lanes I might use for assignment are System lanes with chunks of unattended nodes, for which I do assign these to the process designer, mainly for the case AJ notes with process initiator accounts becoming deactivated.  This has caused us a lot of support in the past, for which each process instance is just edited and changed to run the node as designer anyway..

    My security is always controlled outside of the node assignment settings.

Reply
  • I'll use swim lanes regularly, but not often for node assignments.  Mostly just for a visual in /design.  Especially with Tempo/SAIL, it's much less common these days that I have to chain tasks for the same assignee or route a process back to a different task for the same assignee (multiple nodes in a lane with the same assignment).

    The only lanes I might use for assignment are System lanes with chunks of unattended nodes, for which I do assign these to the process designer, mainly for the case AJ notes with process initiator accounts becoming deactivated.  This has caused us a lot of support in the past, for which each process instance is just edited and changed to run the node as designer anyway..

    My security is always controlled outside of the node assignment settings.

Children
No Data