filmov
tv
ServiceNow create custom Related List | ServiceNow Related list using relationship | Servicenow ease
Показать описание
Hi Folks ,
Welcome to another servicenow tutorial . IN this tutorial we will be looking on how we can create custom related list in servicenow with very easy steps and demo.
The custom related list are created via relationship in servicenow so you can say that the topic here is ServiceNow Related list using relationship.
LEts first try to understand what is related list in servicenow according to servicenow docs .
Related list :
Defined related lists provide a list of any records you want at the bottom of the form. For example, a simple defined related list that lists other rooms on the same floor may be placed on the Room form. This helps you quickly navigate between them.
In order to create a defined related list, we'll need to use a little JavaScript. We'll work through this in more detail in Chapter 3,Server-Side Control.
Create defined related lists
You can add default related lists to the form for all users to see when viewing records.
Before you begin
Role required: admin
About this task
For example, you may include a list of related incidents at the bottom of a problem record, or a list of members at the bottom of a group record. This functionality depends on reference fields or many-to-many table relationships. If two tables are related via the system dictionary, one can appear as a related list on the other.
Defined related lists allow relationships between arbitrary tables to be expressed as a related list. Any two tables that can have a logical relationship can appear as a parent/child pair via a related list. The following are some examples.
On an incident record, show all incidents opened by the same caller.
On a user record, show the last 20 transactions that user has made.
On an incident record, show all problems opened on the reported CI.
These relationships are beyond the relationships normally defined in the system dictionary through reference fields and many-to-many relationships.
Every related list requires a relationship record. Before creating a relationship, verify that there is not an existing relationship record that already provides the needed information. Use the following steps to create a relationship record.
Procedure
Click System Definition -- Relationships.
Click New.
Specify the relationship record fields.
Click Submit.
A related list on a form serves the purpose of providing additional information related to the form record and gives a quick overview of how the other records would be affected if something is modified in the current form record.
Also, it provides an ease of creating new records or adding existing records, based on the permissions available to user, from the child table for the parent one.
Here based on the related lists, you can easily tell that this user is an end user since there is no role associated with the user, has a single group membership and has an asset assigned.
Types of Related Lists:
At first glance, these all related lists seem similar but behind the scenes there are multiple things working to provide you with what is termed collectively as related lists.
Following are the types of related lists that are available:
Reference field association (for lack of better term)
Many to Many Definitions
Sys collections
Relationships
Relationships (sys_relationship)
This is the one which inspired me to write this all down and share. This is something that was hiding in plain sight and I only stumbled upon it because of an improvement in the current process.
We had a scenario where we had to show all the outages related to an incident alert. That would include all the outages directly associated to the source incident record, all the outages related to the child incidents of the source incident (mentioned above), any planned outage associated with the impacted configuration items.
Doing this via many to many definitions is possible but it is manual and time consuming. This is where the sys_relationship comes into play. This tables helps create a relationship between the records you want (in my case outages) and the record you’re at (incident alert in my case), even though they may not be directly connected in the system.
An example for a relationship is in below screenshot, this provides the problems related to an incident alert based on the source incident.
Please like follow suscribe to my channel Technomonk and press the bell icon to get the latest update on my new videos.
Till then stay happy and safe .
Have a nice day .
Regards,
Amit Gujarathi
Welcome to another servicenow tutorial . IN this tutorial we will be looking on how we can create custom related list in servicenow with very easy steps and demo.
The custom related list are created via relationship in servicenow so you can say that the topic here is ServiceNow Related list using relationship.
LEts first try to understand what is related list in servicenow according to servicenow docs .
Related list :
Defined related lists provide a list of any records you want at the bottom of the form. For example, a simple defined related list that lists other rooms on the same floor may be placed on the Room form. This helps you quickly navigate between them.
In order to create a defined related list, we'll need to use a little JavaScript. We'll work through this in more detail in Chapter 3,Server-Side Control.
Create defined related lists
You can add default related lists to the form for all users to see when viewing records.
Before you begin
Role required: admin
About this task
For example, you may include a list of related incidents at the bottom of a problem record, or a list of members at the bottom of a group record. This functionality depends on reference fields or many-to-many table relationships. If two tables are related via the system dictionary, one can appear as a related list on the other.
Defined related lists allow relationships between arbitrary tables to be expressed as a related list. Any two tables that can have a logical relationship can appear as a parent/child pair via a related list. The following are some examples.
On an incident record, show all incidents opened by the same caller.
On a user record, show the last 20 transactions that user has made.
On an incident record, show all problems opened on the reported CI.
These relationships are beyond the relationships normally defined in the system dictionary through reference fields and many-to-many relationships.
Every related list requires a relationship record. Before creating a relationship, verify that there is not an existing relationship record that already provides the needed information. Use the following steps to create a relationship record.
Procedure
Click System Definition -- Relationships.
Click New.
Specify the relationship record fields.
Click Submit.
A related list on a form serves the purpose of providing additional information related to the form record and gives a quick overview of how the other records would be affected if something is modified in the current form record.
Also, it provides an ease of creating new records or adding existing records, based on the permissions available to user, from the child table for the parent one.
Here based on the related lists, you can easily tell that this user is an end user since there is no role associated with the user, has a single group membership and has an asset assigned.
Types of Related Lists:
At first glance, these all related lists seem similar but behind the scenes there are multiple things working to provide you with what is termed collectively as related lists.
Following are the types of related lists that are available:
Reference field association (for lack of better term)
Many to Many Definitions
Sys collections
Relationships
Relationships (sys_relationship)
This is the one which inspired me to write this all down and share. This is something that was hiding in plain sight and I only stumbled upon it because of an improvement in the current process.
We had a scenario where we had to show all the outages related to an incident alert. That would include all the outages directly associated to the source incident record, all the outages related to the child incidents of the source incident (mentioned above), any planned outage associated with the impacted configuration items.
Doing this via many to many definitions is possible but it is manual and time consuming. This is where the sys_relationship comes into play. This tables helps create a relationship between the records you want (in my case outages) and the record you’re at (incident alert in my case), even though they may not be directly connected in the system.
An example for a relationship is in below screenshot, this provides the problems related to an incident alert based on the source incident.
Please like follow suscribe to my channel Technomonk and press the bell icon to get the latest update on my new videos.
Till then stay happy and safe .
Have a nice day .
Regards,
Amit Gujarathi
Комментарии