Bug 32495: Mis-matched required fields in UI and api
The "description" field is marked as required in the UI when creating a new Agreement. This flag has been removed to match the API where it is not a required field. Is Perpetual has not been marked as required as it is a checkbox with a default selection so will always provide a value.
Test plan:
1) In the ERM module, add a new agreement and observe that the Description field is required
2) Apply patch
3) Repeat step 1 but this time the Required flag will not be visible.
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
(cherry picked from commit e1b7591eff)
Signed-off-by: Matt Blenkinsop <matt.blenkinsop@ptfs-europe.com>
This commit is contained in:
parent
37d8fbcea1
commit
1968b51ed8
|
|
@ -48,9 +48,6 @@
|
|||
cols="50"
|
||||
required
|
||||
/>
|
||||
<span class="required">{{
|
||||
$__("Required")
|
||||
}}</span>
|
||||
</li>
|
||||
<li>
|
||||
<label for="agreement_status" class="required"
|
||||
|
|
|
|||
Loading…
Reference in New Issue