Unfortunately it's tno possible (natively) to display the history in the end-users portal.
This only you could do this is by creating a rather complex iTop extension.
Take care,
Guillaume
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This method can only be used in the backoffice part of iTop, not the portal. For instance, the $oPage parameter does not exist in the portal, only in the backoffice.
Cheers,
Guillaume
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello! Hopefully you are fine!
I want to display the History Tab on the Edit Form in Portal. To be precise, something to be put inside this:
I want to know both options:
1: To display the whole tab.
2: To display specific entries.
Any help would be appreciated!
Regards
Mushrraf Baig Ashraf
Hello Mushrraf,
Unfortunately it's tno possible (natively) to display the history in the end-users portal.
This only you could do this is by creating a rather complex iTop extension.
Take care,
Guillaume
Infact, I have noticed a function DisplayBareHistory with the following code:
$oHistoryFilter = new DBObjectSearch('CMDBChangeOp');
$oHistoryFilter->AddCondition('objkey', $this->GetKey(), '=');
$oHistoryFilter->AddCondition('objclass', get_class($this), '=');
$oBlock = new HistoryBlock($oHistoryFilter, 'table', false);
$oBlock->SetLimit($iLimitCount, $iLimitStart);
$oBlock->Display($oPage, 'history');
So, hopefully I can use it.
As for what you said, I am already working in an extension. So, I can tread this complex path, God willing.
I am not getting the exact Interface funtion which would let me to change the HTML of "Editing Request" form
I tried the following code but it gets called on the form creation, not on the edition:
So, I hope that if you only refer to the function which gets called on RequestEdit (objectform-ticket-edit), then I am hopeful to get it to work.
Regards
Mushrraf Baig Ashraf
This method can only be used in the backoffice part of iTop, not the portal. For instance, the $oPage parameter does not exist in the portal, only in the backoffice.
Cheers,
Guillaume