I recieving an error while updating few tickets but not all the tickets.
Indexing into a STRING2 type datum which is not a compound data type (apm.save.problem,start).
Also i see for these tickets when i searched and include Application in modify column i can see menu.manager , please can you let me know how come menu.manager is called for these tickets/
Also i can see in log
3196( 5964) 11/14/2013 20:19:25 RTE W @ Received type@ 2 @ Expected type@ 9 @ File@ problem @ Field@ parts @ Record ID@ header,number="IMxxxxx" and header,page=14 @ Field Value@ 11/14/2013 19:58:26 (falcon): 3196( 5964) 11/14/2013 20:19:25 RTE W @ Received type@ 2 @ Expected type@ 9 @ File@ problem @ Field@ parts @ Record ID@ header,number="IMxxxxx" and header,page=14 @ Field Value@ WAITING USER TO CLEARIFY 3196( 5964) 11/14/2013 20:19:25 RTE W @ Received type@ 2 @ Expected type@ 9 @ File@ problem @ Field@ parts @ Record ID@ header,number="IMxxxxx" and header,page=14 @ Field Value@ 11/14/2013 19:58:16 (falcon): 3196( 5964) 11/14/2013 20:19:25 RTE W @ Received type@ 2 @ Expected type@ 9 @ File@ problem @ Field@ parts @ Record ID@ header,number="IMxxxxx" and header,page=14 @ Field Value@ WAITING USER TO CLEARIFY
-- Say " Cheers! " by clicking Kudos Star on the left .
Alerts fail to release parent locks when parent locking is configured for Incident Management DETAILED DESCRIPTION: When the probsummary object record is configured to use parent locking, alerts fail to release parent locks. The schedule record of Update IM10001 Affected Services (sm.update.affected.services RAD workflow) is also affected. Specifically, the apm.alert RAD application calls se.lock.object to lock the probsummary record. When parent locking has been configured for Incident Management, the se.lock.object RAD app also generates a lock against the parent record. On the attemp.lock panel of apm.alert, no variable is used to obtain a reference for the parent locks returned by se.lock.object. As a result, later during the call to se.unlock.object, no variable is referenced by apm.alert for the parent locks here as well, the se.unlock.object code does not release the parent locks. The sm.update.affected.services also does not pass in a parent lock variable to calls to se.lock.object and se.unlock.object. STEPS TO REPRODUCE: Issue is reproducible in SM 7.0x Apps and SM7.10 STRS verified in SM7.0 Configure the object records: 1. System Navigator: Menu Navigation->Tailoring->Document Engine->Objects 2. Enter File Name:incidents 3. Click Search 4. On the Locking tab, Set Lock on display: true 5. Click Save->Ok 6. Change the File name to: probsummary 7. Click Search 8. On the Locking tab, Set: Lock on display:true Lock parent record: true Parent ID Field:incident.id Parent Filename: incidents 9. Click Save->Ok ... 10. Open a new Interaction using a category of "client system" as this has no category alerting set OOB (IIA use "request for information") 11. Select "Create Incident" (IIA use escalate) 12. Save and exit the Incident 13. Check the schedule queue (command line: sch) - There should be a schedule record named "Update IMxxxxx Affected Services" 14. Wait until the schedule record named "Update IMxxxxx Affected Services" processes 15. Access the status display (command line:status) 16. Select "Show Locks" ***** RESULT: The Interaction locks were not released. **** Schedule record created for alerts such as DEADLINE alerts also encounter this issue. Affected apps: apm.alert and sm.update.affected.services 17. Issue with apm.alert can be reproduced in a non IIA system following the steps above using a category of business applications. Requested By: Development Language: all Scope: 4.0
"HP Support If you find that this post or any post resolves your issue, please make sure to mark it as an accepted solution."
Ok, from the looks of it, the issue is with the 'parts' structured array field.
My guess is that on your format, instead of putting the parts and labor field into an array of structures, you've just exposed them as regular text (hence the 'recieved type 2, expected type 9' errors).
Can you give a screenshot of your form at the spot where you have the parts field?
Your screenshot shows me the Pending Reason section of the form... Do you have the Parts and/or Labor field exposed as well?
If that _is_ the field you're exposing in the Pending Reason and Pending Reason Details, then that's your problem. You're trying to treat a field within the structured array as an array field - and it isn't.