More flexibility when configuring behavior for assignment-based features

This idea builds on another great enhancement request (LC-I-61) for using Hire Date as the basis for time-releasing courses in a learning path.

• Add permanent, "optional" user Profile Fields for:

  • Hire Date

  • Transfer Date (Can be used to enter the user's last transfer date to a new Role, location, etc.)

• For assignment-based features, create destinction between "initial assign date" and "latest assign date" (instead of generically having "Assigned Date").

• Make all data points (related to this enhanced functionality) easily discoverable throughout reporting.

These enhancements would add more flexibility to assignment-based features (e.g., 'Timed Release based on Hire Date' or 'Compliance based on Transfer Date,' or 'Compliance based on Initial Assign Date,' etc.).

ALSO WORTH NOTING...

Weaving this kind of thinking throughout the platform doesn't just add flexibility and control when configuring assignment-based features, it also improves real-world usability overall; because now administrators would have more stable parameters to configure assignment-based behavior around, AND they'd no longer be constrained by the current--somewhat "fragile"--system-dependent definition of Assignment Date (that being the latest "instance" of assignment).

• What makes the current, system-based definition of Assignment Date so fragile (and why is this a pain point for administrators)? There are several places where the limitations of Assignment Date can be experienced as a pain point. Here are a couple examples:

  • The administrator needs to change the assignment logic for some training FROM direct LP/course assignments TO team-based assignments. Currently, the fallout inherent to this kind of transition involves losing the original Assignment Dates (of the transitioned LP/courses for their users).

  • OR an administrator needs to correct a user's membership from one team to another (where Team A and Team B share a common training requirement). Again, a "fallout" has to be endured for this kind of correction, because the user's change in membership also changes their 'Assignment Date' for that common requirement.