search

GSA / ITDB-schema

IT Dashboard submissions schema, documentation and example files.
19 stars 24 forks source link

Updating a Project with long activity descriptions #386

Open bill-gehrke-hhs opened 5 years ago

bill-gehrke-hhs commented 5 years ago

I am attempting to update a project with two activities with long descriptions (over 250 characters.) When this was discussed, it was indicated that completed activities would not have to conform to the new lengths as long as they were not updated. In attempting to update a single, in progress activity, I am receiving errors related to two completed activities which exceed 250 characters.

The errors I receive depend on whether or not I include those activities. If I submit XML to include those two activities as well as the in progress one, I receive the following errors:

Project Activity with agency identifier '421779': 000451-BSC: activity description cannot exceed 250 characters. Project Activity with agency identifier '421781': 000451-BSC: activity description cannot exceed 250 characters.

Note that the errors are reported based on the agency activity ID. These errors are proper since we attemped to update the activities and did not provide a compliant activity.

However, if I provide an update to include only the in progress activity, I receive the following errors:

Project Activity with id '113773': 000451-BSC: activity description cannot exceed 250 characters. Project Activity with id '113775': 000451-BSC: activity description cannot exceed 250 characters.

Note that the errors reference the OMB activity ID, not the agency ID. However, these do refer to the same activities as in the first set of errors. This indicates that there is checking being performed on activities not included in the XML update.

I will provide files via email but am concerned that the edit checks are attempting to enforce the description rule for older activities. We have not yet tested activity names, so it is possible this issue also extends to activity names exceeding 100 characters.

courtneycorwin commented 5 years ago

FAA all ran across this error about 3 seconds after Bill posted it. Thanks!

rydougherty commented 5 years ago

Hi Courtney and Bill,

We have a fix lined up for this issue that should be deployed prior to Monday. We will let you know if any scheduling adjustments occur.

Thanks, Ryan

rydougherty commented 5 years ago

Hi Courtney and Bill,

A fix for this issue has been deployed to UAT. We will go to Production over the weekend once IT Budget submissions have finished.

Thanks, Ryan

rydougherty commented 5 years ago

Hi Courtney and Bill,

This fix was indeed deployed over the weekend. If you have any further questions, please let us know.

Thanks, Ryan