We need to make "optional" course requirements behave the way they should.

For example
Item 1 (Optional)
Item 2 (Optional)
Item 3 (Required)
Item 4 (Optional)

Item 1, 2, and 3 should be accessible directly, but Item 4 should not be accessible until Item 3 is completed.

Comments

scottrigby’s picture

scottrigby
he/him
Primary language English
Location Brooklyn, NY
commented

Or should this only be the case when a (configurable) sequential (as opposed to arbitrary) workflow is enforced?

djdevin’s picture

djdevin
he/him
Primary language English
Location Philadelphia
commented

If we had a sequential/arbitrary option, yes :)

djdevin’s picture

djdevin
he/him
Primary language English
Location Philadelphia
commented
Status: Active » Needs review

Committed: http://drupalcode.org/project/course.git/commit/60368ba

Users should be able to jump all the way to the next required object if the objects before it are optional.

djdevin’s picture

djdevin
he/him
Primary language English
Location Philadelphia
commented
Status: Needs review » Fixed

There's a test for this too.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

  • Commit 60368ba on 6.x-1.x, 7.x-1.x, 7.x-1.x-fieldable-entities, course-object-entity-view by djdevin: 
    Issue #1700612: advanced workflow behavior (allow bypass of optional...