Like I thought, this was simple, and even documented (although not in an
obvious fashion - see pg. 375 of ARS 7.1 Forms and Application Objects).
Even the support guy was thrown off by it until someone who had seen it
before explained it to him.
If you add a new table field to a form like
Here's an interesting problem. Any of you using ITSM 7 (7.0.02.007)
in multi-tenancy mode might need to know this, too.
BACKGROUND: I keep running into issues where Incidents are not
accessible to groups that have worked on them, particularly where the
Ownership remains with the default
Chris,
Maybe for what you are trying to accomplish, you should setup a separate form
to track the unique listing of different groups who have been assigned to work
on an incident.
Setup workflow that when TR.Assigned Group is not null to push data to this
IncidentAssignmentGroupTracking form
That looks like it might be the best bet for the Incident permissions.
I'll have to make an enhancement project out of it since it involves
more work than a quick fix.
For HPD:WorkLog it appears that all I had to do was modify the filter
HPD:WLG:UpdateGroupList-AsgGroupINC_550 to set the Assignee
This got complicated quick - I suspect the incomprehensible behavior of
a deployable application may be at play here. I created a form like you
said, and have filters populating it with records when HPD:Help Desk
updates. I have not been able to create a hidden table field on HPD:Help
Desk that
5 matches
Mail list logo
