Improve guidance on use of ACTIVITY.timing
Raise CR
Analysis
Execution
Raise CR
Analysis
Execution
Description
CR fixes the problem in
relates to
Activity
Show:

Erik Sundvall December 17, 2018 at 8:19 PM
Good that timing is made optional.
Thomas Beale November 30, 2018 at 9:00 AM
Both typos corrected - they will flow through in the next upload.

Sebastian Garde November 30, 2018 at 7:43 AM
Looks reasonable to me - you could correct two typos:
For example, 5 repititions of the period '10 days' starting on 01 march 2008 is `"R5/2008-03-01T13:00:00Z/P10D"`.
The Action_archteype_id_valid invariant

Diego Bosca May 31, 2018 at 7:56 AM
+1

Former user May 31, 2018 at 7:50 AM
I agree - let's make timing optional for 1.0.4.
Done
Details
Details
Reporter
Raised By

Original estimate
Components
Affects versions
Created April 19, 2018 at 2:44 PM
Updated December 18, 2018 at 8:53 AM
Resolved December 18, 2018 at 8:50 AM
See
For when populating some cases, ISO8601 'R' notation could be used. E.g. "R5/2008-03-01T13:00:00Z/P1Y2M10DT2H30M".
See https://en.wikipedia.org/wiki/ISO_8601#Repeating_intervals
Update documentation re complex and simple cases.
Could even use cron expressions or similar.