Difference between revisions of "Attachments on Configuration Items"
m |
|
(No difference)
| |
Revision as of 02:07, 9 January 2009
To discuss or ask questions about this article, select the discussion tab above.
Overview
This article provides instructions for adding attachment capabilities to Configuration Items.
Note: This customization is designed for r11.x versions only.
Procedures
Step 1. Modify Schema
For ALL releases make your schema change by creating a .mod file and placing it in the $NX_ROOT/site/mods/majic directory. Name the .mod anything you like, but it is recommended that it be preceded with a 'z'. Take the code you need from the examples below. <source lang="text">LREL attmnt_lrel "nr:PDM" attachments <> attmnt assets;</source>
Step 2. Publish the Schema changes
For ALL releases recycle the Service Desk service.
Step 3. Edit the detail_nr.htmpl form
Add the following code to the BODY of the form in the PDM_NOTEBOOK area: <source lang="html4strict"><PDM_TAB ID=attmnt SRC="OP=SHOW_DETAIL+HTMPL=xx_attmnt_tab.htmpl+FACTORY=nr+PERSID=$args.persistent_id" NAME="Attachments" height=300></pdm_tab></source>
Step 4. Edit the xx_attmnt_tab.htmpl form
This step will add "Edit" and "Delete" right-click options if the Inventory Functional Access is granted on the user's Access Type. If this scripting is not added then you will only have the option to view a document. Search for the following scripting:<source lang="javascript">switch ("$prop.factory") {
case "cr": attmntAccess = "${ACCESS.call_mgr:0}" - 0; break;
case "iss": attmntAccess = "${ACCESS.issue_mgr:0}" - 0; break;
case "chg": attmntAccess = "${ACCESS.change_mgr:0}" - 0; break;
}</source>... and add the following case:<source lang="javascript">
case "nr": attmntAccess = "${ACCESS.inventory:0}" - 0; break;</source>
Step 5. Clear the web cache
Publish your changes via the Web Screen Painter. The process of publishing automatically initiates a pdm_webcache.
NOTICE
Be advised that implementing this customization will result in a few ERRORS in the stdlogs, but there has been no reported degradation in functionality. <source lang="text">kt_daemon 16316 ERROR DomWrap.c 1106 cSelect: failed In method select_sd_ref_num. Error Message: Error 103 AHD03053: Bad where clause: invalid constraint. Could not recognize persistent_id. OUTER_JOIN ca_owned_resource.id = usp_owned_resource.id kt_daemon 16316 ERROR DomWrap.c 806 Failed to complete reply method: 'select_sd_ref_num' ,BOP Name:'attmnt:400063' in class:'CAttmntLinks', Error:AHD03053: Bad where clause: invalid constraint. Could not recognize persistent_id. OUTER_JOIN ca_owned_resource.id = usp_owned_resource.id domsrvr 13132 ERROR attr.c 6164 Error in ATTR_INIT trigger get_attached_name for attached_name: AHD03053: Bad where clause: invalid constraint. Could not recognize persistent_id. OUTER_JOIN ca_owned_resource.id = usp_owned_resource.id</source>