Bug 118019
| Summary: | simplesurvey application (1.0) : wrong constraint in Response.pdl with CMS 6 | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Enterprise CMS | Reporter: | durnez <vdurnez> |
| Component: | other | Assignee: | ccm-bugs-list |
| Status: | CLOSED WONTFIX | QA Contact: | Jon Orris <jorris> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-09-05 17:49:12 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Closing old tickets |
Description of problem: I use simplesurvey version 1.0 with CMS 6.0.1. in Response.pdl : object type Response extends ACSObject { ...... component Answer[1..n] answers = join ss_responses.response_id to ss_answers.response_id; ...... constraint 1..n is wrong because answers can all be optional. Did this issue not appear with CMS 5.2 because of constraints not rigorously enforced in 5.2 ? The solution is to change [1..n] by [0..n] Version-Release number of selected component (if applicable): simplesurvey 1.0 CMS 6.0.1 (must be the same issue with 6.0.0)