Finally I did it the wrong way, but working way :^P
Here's my solution for the moment:
Create a profile with visibility for read/write on incidents and all other objects that can be filled in a Incident (Or global read).
Via $_SESSION['auth_user'] you know which user is logged in. You need to modify directly on the env-production/module/model.module.php files. At the end of each file the menu creation is done. Just add an if (In my case I made a function which reads a file with the users who shall see those menus), if the user needs to see it, lets go, if not, then do nothing (Or show what u need).
Ps.: If I came up with another way to do it, i'll post it here :)
Its a bit brute, but it works :P
Last edit: Pau GC 2014-02-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes is it possible.............i have done this.......
you have to follow same method or function which used for UserRequest........When you will success then hide above two or three line of user request..........
Hello,
a little advice , change just the DataModel as if there will be an update you will have some difficult to update your version .
I do not think it is difficult for the incidents, in my portal I added the creation and modification changes while incidents are already scheduled .
I made changes to the level of a variable, eg
<constant id="user-content-PORTAL_EMERGENCYCHANGE_DETAILS_ZLIST" xsi:type="string" _delta="define"><![CDATA[{"col:left":["ref","caller_id","status","title","description","tto_escalation_flag","sla_tto_over","ttr1_escalation_flag","ttr2_escalation_flag","sla_ttr2_over"],"col:right":["start_date","end_date","implemented_date","last_update","tto_escalation_deadline","team_id","priority","parent_incident_id","resolve","resolve_comment"]}]]></constant>
after you must edit the portal and add a menu to create the ticket eg
$oP->AddMenuButton('mytickets', 'Portal:MyTickets', '../portal/index.php?operation=my_tickets');
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Guys,
Is it possible to get the portal to work with incidents only and not help desk requests?
Many thanks,
Dave.
Any thoughts on this one please?
I've reached the same point as you... I'm interested on having a portal interface for incidents only.
As far as I looked into the code, that cannot happen without recoding the portal or making a new one.
I think the only way is to make a profile for a user that only can read/write incidents. That part is quite easy.
The problem comes with the left panel. Even with only right to work with incidents, the full menu still in one piece.
So, after that, can the left menu be tweaked to only display certain entries within the profile ?
Finally I did it the wrong way, but working way :^P
Here's my solution for the moment:
Create a profile with visibility for read/write on incidents and all other objects that can be filled in a Incident (Or global read).
Via $_SESSION['auth_user'] you know which user is logged in. You need to modify directly on the env-production/module/model.module.php files. At the end of each file the menu creation is done. Just add an if (In my case I made a function which reads a file with the users who shall see those menus), if the user needs to see it, lets go, if not, then do nothing (Or show what u need).
Ps.: If I came up with another way to do it, i'll post it here :)
Its a bit brute, but it works :P
Last edit: Pau GC 2014-02-07
Last edit: Pau GC 2014-02-10
Hi guys, have you got any solutions to make woking incident though the user portal, i mean the entire solution ?
Best regards
Hello ......
Yes is it possible.............i have done this.......
you have to follow same method or function which used for UserRequest........When you will success then hide above two or three line of user request..........
https://sourceforge.net/p/itop/discussion/922360/thread/cae6a117/?limit=100#cee0
Regards
Pankaj khuran
Last edit: Pankaj khurana 2014-03-27
Hello,
a little advice , change just the DataModel as if there will be an update you will have some difficult to update your version .
I do not think it is difficult for the incidents, in my portal I added the creation and modification changes while incidents are already scheduled .
I made changes to the level of a variable, eg
<constant id="user-content-PORTAL_EMERGENCYCHANGE_DETAILS_ZLIST" xsi:type="string" _delta="define"><![CDATA[{"col:left":["ref","caller_id","status","title","description","tto_escalation_flag","sla_tto_over","ttr1_escalation_flag","ttr2_escalation_flag","sla_ttr2_over"],"col:right":["start_date","end_date","implemented_date","last_update","tto_escalation_deadline","team_id","priority","parent_incident_id","resolve","resolve_comment"]}]]></constant>
after you must edit the portal and add a menu to create the ticket eg
$oP->AddMenuButton('mytickets', 'Portal:MyTickets', '../portal/index.php?operation=my_tickets');