- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-03-2016 01:53 PM
My task is to create a Catalog Task form, which is modified from the original out of the box catalog task form, from a Catalog Item, which will allow an employee of the company to submit a request to unlock their account or submit a password reset request to the Help Desk. I have tried working in my Developer environment to test this, but am not having much luck with it thus far.
The fields on the form so far are as follows:
Left Column | Right Column |
---|---|
Number | Approval |
Requester Name | Priority |
Requester E-mail | Priority |
Requester Phone Number | Status |
Assignment Group | Request Item |
Assigned To | Opened By |
Due Date | |
Short Description | |
Description |
I have renamed the State field to Status and Requested for to Requester Name.
I have created a Catalog Item called Account unlock/Password reset for this and am thinking I need to do this via Workflow. But need some assistance with this. If anyone can provide some help, it would be most appreciated. If you need further details, please let me know. We are attempting to create a portal where users can submit requests via a more automated approach.
Thank you,
Kevin
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-08-2016 11:43 AM
Thank you, Kevin, for the update.
The customization of the catalog task form can be done with combination of view rule and ACL.
View Management - ServiceNow Wiki
Using Access Control Rules - ServiceNow Wiki
But if the form has to be exposed to ESS users then I think record producer or catalog item will be best.
http://wiki.servicenow.com/index.php?title=Record_Producer#gsc.tab=0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-16-2016 05:35 AM
Hello pradeepksharma,
I should have asked around about this to see if it could be done, prior to wasting time.
I did find a post, Catalog Item vs Record Producer , in which this is discussed. It just needs to be made global in order for it to be accessed and I would think using ACL's to not allow certain areas access to the data.
Do you have any thoughts on this? I think this will be my last question for this and we can come to a close on this issue.
Thank you again for all of your help

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-16-2016 11:10 PM
Hi Kevin,
Thanks for the update. I have gone through the thread you have mentioned and it has the same info I mentioned earlier.
I am not sure on what you refer to " It just needs to be made global in order for it to be accessed and I would think using ACL's to not allow certain areas access to the data.". Can you please give more details.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-17-2016 05:59 AM
Pardon me for my brief response. I should have provided more details in the response. I meant that based on the information which was read, it should have a Global scope. Then, use ACL's to allow or disallow read, write, create, execute, delete permissions depending upon the role assigned to the user or group.
I hope my definition is more clear this time. If not, please let me know.
Thank you,
Kevin