User assignment and Ending a cycle

Taryn

The Functionality looks really great and seems almost there.

 

I do feel like the following is required for this to be usable practically:

 

1)Ability to end a cycle and stop the running tasks/emails to users. 

 

2)If a member in a list doesn't have an assignment, it should default to no one being assigned that member not the process owner in case you are using long hierarchies for your base lists like product demand approvals

 

 

Taryn

Hi Will,

 

Yes, exactly. If unassigned, they didn't trigger a task. We ended up with a couple situations where the user properties are placed on an extensive hierarchy and since we cant select a subset as the Anaplan list in the task builder, some of the intersections end up not having a person assigned at the time a cycle is created. Since we can't opt them out, it just sends a bunch of tasks to the process owner. Rather than trying to maintain duplicate hierarchies just for a workflow opt in, it would be nice to be able to exclude intersections

WillSippl

Thanks again for the feedback, Taryn. This aligns with what we've heard from others and we'll work on adding it into the product & roadmap.