Can a file be attached to a task on creation - using a script?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2014 08:58 AM
Hello,
I have a requirement where a file needs to be attached to a catalog task(created using a workflow) all the time of its creation.
I tried attaching the file to one of the incident and pulling it from there, as this is not a feasible idea because the incidents can be archived when the count increases at some point of time and ultimately loosing the attachment too...is there any better way of achieving this?
Any ideas would greatly be appreciated....!
Thanks in Advance,
Abilash
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2014 01:59 AM
Hi Abhilash,
Cant you just create a test incident and just attach your template on that. This test incident can be in any state, so you can cancel/close it.
Thanks,
Anurag
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2014 02:58 AM
I did the same anurag, only worried on some point of time the older incidents will be archived with an automatic script which runs on regular intervals....so there are ample chances of loosing the incident....!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2014 03:39 AM
The user defined table you mentioned, how were you limiting access on that table only to admins?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2014 03:54 AM
Initially I tried attaching the file on "sc_cat_item" table on the item record, though the table as read only access to ITIL and ESS users, the BR is unable to fetch the attachment from it....I did not create any additional access permissions to restrict....
However this works perfect on if the attachment is on any incident record....
Thanks,
Abilash
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2014 04:05 AM
Create an actual user defined table. Benefits will be that since nobody will know the table name and it will not show up on the left hand menu also , so chances on a non roled user accessing that table will be minimal. Moreover you can implement you own defined access controls on that.
I would still prefer using the incident table only. To avoid the archival issue you can use properties to get the source source table and sys_id. And you can extend this functionality or write a simple job to update this property with a fresh ticket once every month or so.