...
SI drafters use a number of different practices for the date in the signature block until an exact date is known. A bug (entering words rather than dates), with the signature block date function, is also creating invalid XML, which either means the users needs to delete and recreate the signature block or edit the XML (in practice this is escalated to the Service Team). The above improvement would meet both the user needs and reduce calls to the Service Desk, however it also introduces a risk that drafters would have less flexibility using the date field.
This relates to https://tsoltd.atlassian.net/browse/LEGDEV-6858 where in the Signature block of a UKDSI there is a date which is not in the SI
<Signee>
<PersonName>Name</PersonName>
<JobTitle>Title</JobTitle>
<DateSigned Date="2024-12-01">
<DateText>Date</DateText>
</DateSigned>
<Department>Department for Business and Trade</Department>
</Signee>
This happens because, currently, Lawmaker uses the AkN <date> element as a placeholder, for when a date gets added. And that element is required to have a “date” attribute containing a valid date.
...
Status | Feature logged |
---|---|
Lawmaker components affected | Signature Block, SI/SSIs |
Raised by organisation(s) | TNA |
Planned version to be included in (if any) | |
Related development ticket(s) |
...