Do you specifically need to add the attachments into the same place as the incident attachments are stored? If not you might find it better to create a new task attachment object. Here is how you could go about this:
- Please try this out on your test environment to ensure that you are happy with it before you make changes on live.
- In object designer create a new object within Incident Management called Task Attachment. When asked if you want to specify a behaviour select No.
- Save the object and say yes to auto create a name attribute.
- Add a new attribute (called something like Attachment?) and change the attribute type to attachment. Save the object.
- Still within object designer drag the Task Incident object onto the new Task Attachment object. When asked if you want to be able to access all related instances select Yes.
- On the Task Incident object you will now see a collection relationship to the Task Attachment object on the list of available attributes. Click on this and then select New Action. Type in a name for the action someone will need to pick in order to add one of these attachments. An example could be Add Task Attachment.
- Go into window manager and locate your new Task Attachment object. Create a new window for this and then select to Auto Populate the window. Make any design changes that you want (you might want to task off the task incident attribute for example) and then save your window.
- Still within window manager go into your Task window and drag on the Task Attachment collection from the list of available attributes. Set the properties of this to display on the tree or the tabs as required.
- Go into Process Designer and deactivate your Task process (you may need to make another task process the default one temporarily whilst you do this).
- Click on the status value that you want and then click on Properties - Optional Action Instances. You can now add your new action onto the available actions at this status.
- Save your process, activate it and then make it the default (if it was previously).
NOTE: If you want to be able to send attachments to users you can do so by altering the Task Attachment object within object designer and on the object properties setting the behaviour Event Source on under the behaviours collection. You can then set some default text to go in the notification via the Mail Notification collection that will appear once the Event Source behaviour has been set.
Awesome, that worked.
Thanks Karen for all the help!
Glad to be of help!
Is it possible to "add an attachment" in my incident and see it inside the task and vice versa?
In case you won't see the action as available, remember to
check the privileges for you Incident Task Attachment, it should be somewhere within the Process Related Objects - Task Attachement and Task Incident - it should have Execute/Read/Create/Update privileges.