Closed deb761 closed 1 year ago
I pushed this to the same org i did the other 2 PR's in. Let me know if that is an issue and if i should do a fresh deploy. I didn't get an error.
I opened a contact "Robyn Bean" and went to the related tab. I clicked on Files to upload but i am unable to get anything to show under category or type. This test data had Staff as a position. I added volunteer just in case it was based on position.. but no change.. There are no errors, it just doesn't let me see any options.
Testing results- think the only
So, assuming the refresh is to be expected, which we can just document as known behavior, then it's just fixing dog. super close!!
Dog is fixed. :)
So I just realized in testing dog that we should show different things when you are in the Team view to upload dog or client files than in Contact or Dog. This will help avoid people uploading them to the wrong place, which is a big part of the point of this change. it's less of an issue if they get added to team as they can be seen in client/dog; it's the otherway around that is more of a problem. Here is how they'd be split out (same as the page layout)
Team.Dog-> Vet Health Form, Vet Xray Report Dog.Dog-> Vaccinations and Exams
Team.Client->Pre-Application, Application, LOMI, Veteran Paperwork, Application Video, CGC Contact.Client->Contact Form
One question on this, though. right now one of the fixes we had in 1.4 was we could support adhoc types as long as we didn't have dates associated w them. how will that play into this? The place it is going to come up the most is on Contact. Can we have it be that these types are explicitly filtered to only show as above and anything else will show per the Category/Type mapping under ContentType?
This is a rather large change. It required adding an object to define how the context would work, and a controller that would provide the desired list of categories for a given object. Note that because a new object type is added, you will want to load_dataset in the org you are testing this in, which is run as part of the dev_org flow.
Critical Changes
Changes
Issues Closed
139