Hi
When adding in back-office an attachment in a checklist, which name is longer than 30 char, we have the following error message :
When an attchment is added from mobility, no error because it seems that the classification field is not fulfilled.
Is there a way to prevent this error in BO ? How can we let this classification field empty ?
Thank you
Laurence
Alliance V15.1.0.12
Best answer by Phil Seifert
Hi,
I did more investigation, the classification is populated with the checklist name value, nothing to do with the actual filename being populated. It does seem to be standard functionality to populate the checklist name as the classification.
Retesting this with this in mind, I created a long checklist name and this also populated in our QAC 15.4 SU3. However, again this was with the web employee portal, not the Astea Browser which we are not using much in 15.4 SU3.
Please log a ticket if this is happening for you with exact details such as the name of your checklist, filename, and backend portal being used.
Otherwise, if you don't want to populate the classification via the backend… again this is a customization.
+24Hi Laurence,
The description you provided is not entirely clear. Is it a photo attachment? Also were you doing the from the Web Employee Portal backend end or were you using the Astea Browser (which I believe your company refers to as the smart browser most of the time?
In any case, assuming it was a photo with a very long name, I created a checklist with a photo and was able to upload it in QA running on 15.4 SU3+.
When I then looked at the attachment, the classification 1 had nothing to do with the name of the file so I am not sure what it long in your case? My test showed the classification was the name of the checklist itself:
I believe you have an issue that needs to be fixed and should log a ticket for this situation along with clear steps how to reproduce the problem.
Hope this helps.
p.s. to avoid populating the classification will also require a code change customization to prevent.
+15Hi Laurence,
When you click on the Lookup on the Classification Level field does that window show entries with MORE THAN 30 characters? If so, that may be the problem, I think the ap_attachments table at the database level has this field defined as varchar(30) so it may be exceeding the maximum length there. If so, try shortening the Classification Level data a bit to see if it solves the issue.
Thanks,
Reid
+24Hi,
I did more investigation, the classification is populated with the checklist name value, nothing to do with the actual filename being populated. It does seem to be standard functionality to populate the checklist name as the classification.
Retesting this with this in mind, I created a long checklist name and this also populated in our QAC 15.4 SU3. However, again this was with the web employee portal, not the Astea Browser which we are not using much in 15.4 SU3.
Please log a ticket if this is happening for you with exact details such as the name of your checklist, filename, and backend portal being used.
Otherwise, if you don't want to populate the classification via the backend… again this is a customization.
Hi Reid,
Thank you. Yes as you’ve found, this field is populated with the checklist name, when we add a photo from the smart client (backend astea app). Our customer’s followed our advice and shorten the checklisty name.
But do you know why, when adding a photo to the checklist from mobile, this field stays empty ?
Laurence
+15Hi Laurence,
We don’t have logic on the mobile side that copies the checklist name over, that would need to be logged as a RFE or customization request.
Thanks,
Reid
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
