- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-26-2019 06:01 AM
Hi to everyone...just a little doubt about SLA, workflow and dot-walking: I have a SLA with his workflow with notification at 50% and 75%, for the notification at 100% I have a "If" condition which "yes" brings to a notification and "n"o brings to another one. My "If" condition is setted to the value in a custom field on incident table, so the dot-walking I used is like:
task.ref_incident.u_field (where u_field is my custom field)...
workflow seems work with this dot-walking but the question is: how I've reached my custom field in incident from task table (actually from task_sla)? is the dot-walking correct?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-26-2019 06:06 AM
Hi there,
Looks oke. You could add a .getValue(), though looks oke.
What is it you're after? Just confirmation 🙂 or is still something not working?
If my answer helped you in any way, please then mark it as helpful.
Kind regards,
Mark
---
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-01-2019 05:11 AM
Hi Antonio,
It is correct. If the current table contains a reference to another table, any field on the referenced table can be accessed using dot-walking.
The recommended limit for chain length is three levels. Because more the dot walking, more the joins internally and will create performance issues.
Mark the comment as a correct answer and also helpful if it answers your question.