How to copy data from a field into a variable in the Service Portal?

MGD_1
Tera Contributor

Hello all,

 

I have performed an exhaustive search on how to copy a field value from a backend record to a service portal variable when the form is accessed and I cannot find anything exactly like this.  I've seen info about widgets and such, but that's not what I need.  Please help if you can.

 

What I'm trying to do:

A Scrum Task automatically gets created when a Story is created.  When someone fills out the Assigned To or Assigned Group on the Scrum Task, it automatically sends out an email notification to that user or users with a link in the email notification to advise them they have a sign-off waiting in the service portal.

 

I need to be able to have the customer click on the link in the email, where it will open that specific Scrum Task in the service portal and fill in certain variables, so the customer does not have to enter anything and knows the exact task they are looking at.  I cannot seem to find a way to copy the proper fields over to the service portal variables and have them show up.  I have tried client scripts, business rules, UI Actions, etc. and I can't seem to find a way to copy over the data to the variables for display.  I'll make them read-only as well.

 

I would greatly appreciate it if anyone can help.  Thank you.

1 ACCEPTED SOLUTION

I wouldn't recommend going that way. Not only will you invest significant effort and accumulate technical debt, but you will also be building an alternative Approval functionality that would bypass the licensing requirements. If ServiceNow folks find it out, they will charge you for those users as for Approvers in the same way as if you used the standard Approval functionality.

View solution in original post

7 REPLIES 7

Slava Savitsky
Giga Sage

What is the reason for trying to use variables? Why cannot you display the Scrum Task form to the user in the Service Portal and let them fill in the Scrum Task fields?

@Slava Savitsky  - Unfortunately, the customers won't normally just go into the Portal and fill out the stuff themselves.  They don't know enough about it.  It is, in a sense, a "sign off sheet" that I've created.  They want me to have their name (logged in user), the Scrum Task number, the Story Number, the Short Description (from the Story) and the Acceptance Criteria (again, from the Story) filled out.

 

This way the customer just has to select Pass or Fail and put any comments they want and click submit.  That's why they want me to have the top part filled out.  They won't know what to put in there.  

 

I tried doing it where they would enter in the Scrum Task (SCSK) and it would populate the info.  That works fine, but they want it all working off of the URL link in the email so they do not have to enter in any information.  That is why I need to find out how to copy the fields from the Scrum Task and autopopulate them on the Service Portal Page that comes up with the URL link in the email  🙂

 

Thanks!

Why make it so complicated? Attach an Approval to the Scrum Task and assign it to whoever needs to approve. In the Portal, the user will see that an approval has been requested from them and will be able to either approve or reject in the same way as they would do it for a RITM or a CHG, without the need to fill in any data. They will also see a summary of the record they are approving (i.e. Scrum Task).

@Slava Savitsky 

 

You have a very good point.  However, don't you need to be a ServiceNow licensed user to perform approvals?  Reason I ask this is not to be difficult, but my organization is trying to find a way that they don't need to subscribe to a trillion licenses just to have people approve the Stories/Scrum Tasks.  

 

That is why they wanted me to have the sign-off (or approval) done in the Portal so it can be a non-licensed user/customer that can perform the sign-off (or approval).

 

If it does not take a licensed user to perform the approval in the Portal, then I'll definitely go that route as you are correct that it is not as complicated.  🙂  I appreciate the idea/thought.