-
1. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
rodrigo barcatNov 15, 2019 5:53 AM (in response to Miroslav Horvath)
2 of 2 people found this helpfulHi,
I have something like you want to achieve. What I did?
Create some fields to get approvals ids before sent the email,
In these fields I set approval ID, approval join id, etc.
After I set these fields, I prepare the data to send it to AR Email Messages
The magic is here! When you send all the data to email messages, you need to populate the field "Field Values", with approvals details (ID's).
-
2. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
Miroslav Horvath Nov 15, 2019 6:48 AM (in response to rodrigo barcat)hmm. The thing is, that I'm not pushing the data directly to AR System Email Messages, but I'm using OOTB workflow, which means I;m calling NotificationGenerator workflow., because I push my data into NTE:SYS-NT Process Control and then the notification is triggered.
-
3. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
rodrigo barcatNov 15, 2019 7:12 AM (in response to Miroslav Horvath)
I read that you "...have created a notification directly on SRM:Request form..." so, you have 2 ways.
1 - get logs to understand what happens when OOTB create an approval notification. (it is the best option to know the flow)
2 - create your email in SRM:Request, as you did, but instead of send data to NTE:SYS-NT Process Control, try to mount all email (body, subject, etc.) and send it directly to AR System Email Messages.
-
4. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
Miroslav Horvath Nov 15, 2019 7:19 AM (in response to rodrigo barcat)thx, but for 1) I have took the logs and tried to find it but was not able to found the point where the fields are "translated" to that they will work within the URL of the template.
2) if I want to use some Template , which is store within Remedy Email Templates, does it work with this direct push to AR S E M ?
-
5. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
Vedran Vesel Nov 15, 2019 7:38 AM (in response to Miroslav Horvath)Hi Miro,
Did you looked at filters like:
- "NTE:NTS:Email_SystemNT_with_EmailTemplateGetURLPath"
- "NTE:NTS:Email_SystemNT_with_EmailTemplateSetIncidentType"
- "NTE:NTS:Email_SystemNT_with_EmailTemplateSetTaskType"
They are used for creating and publishing url's in Email Templates.
Kind regards,
Vedran
-
6. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
Miroslav Horvath Nov 15, 2019 7:44 AM (in response to Vedran Vesel)we don't use Smart IT. When I've checked my LOGS, they were also not triggered for the notification which contain the working URL.
This is the notification "SRM-REQ-Approver_Notification" , which you can find within SYS:Notification Messages.
This notification generates an email with Approve/Reject buttons which contains working URL with Ticket ID. But cannot find the workflow, which ensures that within the URL behind the Approve/reject buttons the TicketID is present.
-
7. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
rodrigo barcatNov 15, 2019 7:54 AM (in response to Miroslav Horvath)
1 of 1 people found this helpful1 - I can help you, but I need to simulate it on my environment, or with you share yous logs. I can do it later.
2 - Yes, but you need to set the fields that use your template. Need to read logs to understand how it woks as well.
Get a full log since the request open until the email sent, then share with us.
Using your image:
Request ID: is the field $Detail-Sig-Id$ (AP:Detail-Signature join form)
It is the most important field that you need to push on Field Values.
-
8. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
Miroslav Horvath Nov 15, 2019 8:24 AM (in response to rodrigo barcat)Hi, attached is the LOG. There are 3 notifications which are sent out.
1st is the information that Request was submitted. That's SRM-REQ-Submitted-Requester
2nd is SRM-REQ-Approver_Notification which is OOTB and contains that working URL with TicketID
3rd is my custom ABS-SRM-SHOP-UsersManagerApproval which contains almost the same template as the notification in 2, but the URL within the email doesn't contain RequestID.
-
MH29.zip 253.4 K
-
-
9. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
rodrigo barcatNov 16, 2019 5:15 AM (in response to Miroslav Horvath)
Hi, Miroslav Horvath
I read your logs. Now, can you explain more how your flow works?
I will try to create the same scenario on my side. Just to be on the same line, your problem today is the approval/rejection request ID, which is not going in the email, right?
Cheers and have a good Saturday
-
10. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
Miroslav Horvath Nov 18, 2019 2:10 AM (in response to rodrigo barcat)1 of 1 people found this helpfulI really appreciate any help. For simulating this, it's very easy. Do this steps to reproduce the thing:
1. Create a new Filter on SRM:Request form. The "Run if" action can be anything, which will trigger the filter on MODIFY.
2. within the filter, set the z1d Notification Message Tag for the notification from SYS:Notification Messages. You can use also the default one SRM-REQ-Approver_Notification or create any custom. Important is, that within SYS:Notification Messages, in the field Email Template Name you specify your custom one or use the default "Approval_By_Email_Content_en", just for testing purpose.
2. within the filter, set the notification email into z1D NT Internet Email, so for example your personal email
3. and then make a Push action into NTE:SYS-NT Process Control . You can copy the Push from any similar notification.
So now, when you do any modify on SRM:Request, filter is triggered, and runs the Push into NTE:SYS-NT Process Control with predefined "Notification Message template" from SYS:Notification Messages, and the predefined Message Template should use the "html template with Aprproval buttons" where URL should be behind them, and the REQ ID should be present or will be missing. Btw, I'm talking about missing REQ ID which is #Request ID02 Ticket# , not #Details-Sig-Id# within the URL.
-
11. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
Miroslav Horvath Nov 21, 2019 1:50 AM (in response to rodrigo barcat)Hi Rodrigo, any news ?
-
12. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
Carl WilsonNov 21, 2019 5:04 AM (in response to Miroslav Horvath)
2 of 2 people found this helpfulHi,
if you want the actual Request Number, you can do a couple of things:
- Add some custom workflow to the Signature form to lookup the Service Request Number from the App Request ID - map this through the Notification Engine and populate an unused field which you can translate (update translation workflow) in the SYS:Notification message
- Add some custom workflow to the NTE:SYS-NT Process Control form to trigger when an approval email is created, and then lookup the Service Request Number from the App Request ID and populate an unused field which you can translate (update translation workflow) in the SYS:Notification message
Cheers
Carl
-
13. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
rodrigo barcatNov 21, 2019 6:25 AM (in response to Miroslav Horvath)
I just finishing a proposal to a customer and back to help you!
I believe that in 2-4 hours I will have finish my current task
-
14. Re: How to add RequestNumber to the URL link for Approve/Reject buttons within Email
Miroslav Horvath Nov 21, 2019 6:29 AM (in response to Carl Wilson)Yes, I have used such thing. Instead of having working URL coming from Email Template, I have created a HTML body within SYS:Notification Messages for that message, where I've create the buttons with URLs, and within these URL I use the "Request Number# which is a translated field within SYS:Notification Message. This solution works for me.