For certain workflows there is a need to have dates required as a part of a transition as opposed to in a status.
As an example, there
Desired workflow for an Inspection Request:
Planning
User fills inspection details
All mandatory fields can be set as a part of the status
Schedule review
User submits the form (from Planning) to generate a line in the inspection schedule.
This has planned inspection activities caught in the date property Planned Inspection.
User can revisit the form at this state and change the Planned Inspection date for whatever reasons: Delayed delivery, change of supplier, staff on strike, general delay
Once close to complete works and minimum 3 days in advance the user fills the Inspection notification details that contain Requestor (user list), Organisation (text property – DD or cascade), Actual Inspection Date (Date) and few other text properties
Inspection request
User then submits Inspection request with the above properties mandated in transition.
The limitation here is on step 2d, where the Actual Inspection Date can only be mandated in the status and not the transition. This means that Actual Inspection Date needs to be updated on every delay, even though that date is not clear until the inspection is performed.
This feature is now in QA and will be included in the next release.
This feature is being reviewed in the current dev cycle.