Time-Varying Date Constraints on Custom Attributes Don't Work As Expected
Article ID: 102955
Updated On:
Products
CLARITY PPM FOR ITG
CLARITY PPM FEDERAL
Clarity PPM SaaS
Clarity PPM On Premise
Issue/Introduction
When we want to edit a custom attribute on the time scale for the month of the project start date, we are unable to . The only way we've been able to edit it is if we set the project start date earlier than the actual start. So if starting February 1st, it won't allow hours for February unless the start date field is a month in advance (January 1st).
Steps to Reproduce:
Scenario 1:
1. Create an attribute on the Team object with the following properties:
3. Add a team member
4. Go to the Team - Detail page
5. Configure the view to show ONLY the attribute from Step1 on the Time Scale in Months
6. Attempt to enter a value for the custom field on the first month, March since the project start date is 3/1/2018
Expected Results: The user is able to edit the custom field for the month of March 2018 as it meets the date constraint on the attribute
Actual Results: The user is not able to edit the custom field for the month of March 2018
Scenario 2:
1. Create an attribute on the Team object with the following properties:
3. Add a team member
4. Go to the Team - Detail page
5. Configure the view to show the attribute from Step1 on the Time Scale in Months, ALONG WITH any other out of the box attribute, such as Allocation
6. Attempt to enter a value for the custom field on a month outside the project duration
Expected Results: The custom field cannot be edited prior to March 2018 or after July 2018
Actual Results: The custom field can be edited in any month, including months outside of the project duration
Steps to Reproduce:
Scenario 1:
1. Create an attribute on the Team object with the following properties:
Data Type: Time-varying
Time-varying Type: Calendared
Time-varying Data Units: Number
Time-varying unit conversion: Seconds
Time-varying Date Constraints:
Start On: Investment Start Date
Finish On: Investment Finish Date
2. Create a project with dates of 3/1/2018- 7/31/2018 Time-varying Type: Calendared
Time-varying Data Units: Number
Time-varying unit conversion: Seconds
Time-varying Date Constraints:
Start On: Investment Start Date
Finish On: Investment Finish Date
3. Add a team member
4. Go to the Team - Detail page
5. Configure the view to show ONLY the attribute from Step1 on the Time Scale in Months
6. Attempt to enter a value for the custom field on the first month, March since the project start date is 3/1/2018
Expected Results: The user is able to edit the custom field for the month of March 2018 as it meets the date constraint on the attribute
Actual Results: The user is not able to edit the custom field for the month of March 2018
Scenario 2:
1. Create an attribute on the Team object with the following properties:
Data Type: Time-varying
Time-varying Type: Calendared
Time-varying Data Units: Number
Time-varying unit conversion: Seconds
Time-varying Date Constraints:
Start On: Investment Start Date
Finish On: Investment Finish Date
2. Create a project with dates of 3/1/2018- 7/31/2018 Time-varying Type: Calendared
Time-varying Data Units: Number
Time-varying unit conversion: Seconds
Time-varying Date Constraints:
Start On: Investment Start Date
Finish On: Investment Finish Date
3. Add a team member
4. Go to the Team - Detail page
5. Configure the view to show the attribute from Step1 on the Time Scale in Months, ALONG WITH any other out of the box attribute, such as Allocation
6. Attempt to enter a value for the custom field on a month outside the project duration
Expected Results: The custom field cannot be edited prior to March 2018 or after July 2018
Actual Results: The custom field can be edited in any month, including months outside of the project duration
Cause
Caused by DE39869
Environment
Release: CODFSS99000-15.3-PPM SAAS FedRAMP-Sandbox-Small Environment
Component:
Component:
Resolution
This issue is expected to be fixed in our upcoming PPM 15.5 release.
For affected releases, please continue using the workaround of setting the project start date to a month earlier than it should be. This will make it to where the attribute value will be editable on the time scale for the month of the project start date.
For affected releases, please continue using the workaround of setting the project start date to a month earlier than it should be. This will make it to where the attribute value will be editable on the time scale for the month of the project start date.
Feedback
Yes
No
Powered by
