- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2017 10:51 AM
After upgrading to Istanbul from Helsinki, the "Approving" field (type Doument ID) on the sysapproval_approver table form is showing the sys_id of the document being approved rather than the name, which is set to true for display in the dictionary (i.e. Change). Any idea why this might be?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2017 09:47 AM
Hi Tatiana, yes I did. They confirmed the issue and have submitted it as a product bug. As a workaround, they suggested:
- Reactivate the ACL and modify its role requirement from 'maint' to 'itil'
- Create a UI policy to enforce the read only state on the sysapproval_approver.document_id field.
This did the trick for now until a permanent fix is released.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2017 11:00 AM
Hi Jeff
I'm wondering if you can click-through that reference to the target record. Two other questions that immediately come to mind are:
- Does the Change record exist? (Was it deleted since the Approval was made)
- Were there any query-based Business Rules recently created on the change_request table
Regards
Shahid
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2017 11:04 AM
Hi Shahid, yes, the record exists, and preview shows it properly, clicking opens the document. No Business Rules were created or modified after the upgrade, the behaviour just started immediately following. Funny thing is in the list view, "Approving" shows properly, just not on the form view:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2017 02:37 AM
Interesting. Some other questions to pop into my mind: does this happen for all users or a specific role? Is domain separation being used?
How about enabling some Session Debug? My usual combination is Debug Log, Debug SQL (Detailed) and Debug Business Rules. You will find these listed as modules under System Diagnostics > Session Debug.
When you reproduce the behaviour, you will want to review the information that appears below the form. I would look for any SQL statements to the task table (something like SELECT ... FROM task WHERE .... sys_class_name = 'change_request' ...) and see if there are any other statements (SQL or BR) around that for clues. Feel free to share the output here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2017 05:41 AM
Hi Jeff,
Did you find out the cause of this issue?
Regards,
Arnab