Dean-> manager -> senior faculty -> junior faculty -> students
The above structure is in hierarchical form and when I open dean form in servicenow I should be able to see record i.e. rest of the staff under him. Similarly in manager I should be able to see below him.......and so on for junior faculty I will be able to see students and for students there should be no record
Well you can create hierarchical related lists assuming you are using the List V2.
Check here:
https://docs.servicenow.com/bundle/orlando-platform-administration/page/administer/list-administration/task/t_EnableAHierarchicalList.html
I'm not sure this is 100% what you're after but it is a start. I think that in general a better idea is just to create simple Related Lists which allow the user to hop from one table to another. You don't always need to show everything in one view.
Related
I'm the QuickBase Admin for my QuickBase app. In the app, there's a dashboard report that's used by individuals with viewer access; that way, they can see their students' data, but can't edit the app, tables, structures, etc.
My app's users want to be able to edit one field with notes on that row's data (each row is a student's data, so they'd want to use that field to add notes on that individual), but viewers don't have editing/data entry access tn any column. Is there a way for users to have editing/data entry access to one field, but not the others?
I know with Tableau and other BI software, this isn't possible, but I wanted to ask since my users asked.
Thank you for reading.
Sure you can.
Actually there are more ways to implement this needs.
My opinion better if you create a new table and make a relationship between the student data and a (new) Notes table and you will be able to setup edit rights eg by record owner.
An other way, you can allow the edit right for your users and you can make a restriction on field level. In this case you have to go through on each field and at the Advanced section you will find Permission - Restrict access by role.
Hopefully you do not have a lot of fields :)
I have the below requirement -
We have an entity named Garden. A garden is owned by a person or company, and can also be leased by one or more people or companies. Each garden has a unique number.
Ideally, we would want to be able to see a single grid of all the people that own and/or lease the garden, regardless of whether they are a person or a company.
Questions -
1) Which entity to choose for person -> User or Contact
2) Which entity to choose for company?
3) How to design record ownership or leasing of garden?
This is a broad question, I’ll try my best.
Fact: We don’t have an option today to create a custom polymorphic entity - to capture/store multiple types of entities. There are some available OOB entities - Customer to store Account/Contact, Owner to store User/Team, Activity Regarding to store any Activity enabled entities.
If you look at Bookable Resource entity, even MS store the type like User or Equipment & respective lookup records separately. This is what you need exactly. Read more
1) Which entity to choose for person -> User or Contact
2) Which entity to choose for company?
User (owner) in case you need security around the ownership of the records. Then company has to be the Teams, because you mentioned Garden maybe owned by Person or Company. How many records you’re going to manage and are they going to get login in CRM?
You may have to look at PowerApps (Dynamics) portals which gives B2B, B2C options to control records ownership by Accounts/Contacts.
3) How to design record ownership or leasing of garden?
Partially answered in the above points. For leasing, you can have multiple subgrid (1:N) relationship. If required, you may need a custom component or web resource to pull the multiple type of owned/leasing records by UNION the results & render as a grid.
I want to group certain set of tables in one folder in sql developer. Please suggest me on how to do this.
For examples I have two sets of tables:
Set1:
1. Student
2. Course
3. CourseDesc
4. Faculty
5. City
Set2:
1. Person
2. Bank
3. Account
4. City
Currently I have created two separate schema users and created each set of tables in them. What I would like to do is, instead of creating new users for every set of tables, is their a way to group the tables under one folder in one schema.
Appreciate your valuable inputs.
Dex.
I think that SQL Developer doesn't offer such a feature (unlike TOAD's "Favorites", for example) - at least, I don't know how to do it. A possible workaround is to use prefix for tables that belong to the same set. For example:
STU_STUDENT, STU_COURSE, STU_FACULTY
BNK_PERSON, BNK_BANK, BNK_ACCOUNT
It it probably too late to do it for existing tables, but consider doing it in the future.
I am trying to come up with an UI design for creating a user in Account (Customer) and assigning them a to a one of the levels in hierarchy. And the hierarchy can change depending on the Account selected. I am developing this in an Ionic 2 app.
Would appreciate if you guys can suggest some best approaches in going about it. And, honestly, I am not able to come up with anything good.
Following is an example of various levels that can be setup up for different Accounts. There's going to be 10 levels but not all Accounts will use all 10 levels.
Account is the top most level. All the levels under that will have multiple values. And selecting a value at a level should show only the relevant values in the remaining levels.
Account - Store1 [A Super User having access to all features (Stores)]
|
Country - USA, Canada [User will have access to features of selected country]
|
Region - Eastern, Northern [Features only for the selected region]
|
States - CA, NY, etc.
|
City - San Francisco, San Jose, NYC, etc.
|
Store - Store1, Store2, etc.
Not all Accounts (Customers) will have all the levels. Some might have only 3 or some will have just 2 or others will have 5 and then some might have all 10 of them.
What's the best way to design the User Interface for such data.
Any ideas, suggestions, pointers will be very helpful.
Thanks.
Well , firstly i am sure you could come up with some good ideas you just need to be drinking better coffee ;) . You are a programmer .. its what we do.
Jokes aside. I have recently had to implement a similar hierarchical select structure and did it with each selection navigating to a new view. At first i didnt think this approach was the best but for my use case it actually was because each page had CRUD operations and so clearly differentiated each section.
In your case it is a bit different as they are only selects.
What i would do is show or hide a <ion-list> for each child in the selection process with the selected value at the top separated by an arrow icon.
Selection 1 -> Selection 2 -> Selection 3
Please select
item 1
item 2
item 3
item 4
So basically just show and hide with *ngIf based on the user role and where they are in the selection process with selected options at the top
I have an application where users of the application can have many contacts ( other users of the application ) related to them. I would like to maintain a relation between a single user and its set of contacts. At any given point of time, I do NOT need to know anything more than the direct set of contacts for a particular user, i.e, contacts of contact of a particular user is not of relevance in this application.
Any suggestion on how to organise this data within the database? Please note that the number of users could go up really high.
Just to add some extra info, the database I am using right now is Mongodb and language being used is Ruby.
The only model right now before thinking of building all these relations is the Users model which stores details of each user registered onto the application. Now as I mentioned above, I need to built the specified relation between the user and its set of contacts. Any help would be highly appreciated.