Attending: Kian, Marina, Cheryl, Eric P, Ying, Paul, Briandy, Diane, Brian, Eric T, Carmen (SN), Carman Cedola (carman.cedola@servicenow.com), Jon Crane (jon.crane@servicenow.com)
Notes:
- Discussion re: role/ACL based partitioning of UCI's SN instance for pseudo-multi-tenancy
- Select UCI business/academic units and groups handling sensitive/restricted data (incidents, projects, etc)
- SN Project/Portfolio Management
- Jon also referenced Demand Management (project demand pipeline) also "Ideation" for collecting/managing ideas
- Idea => Demand => Project
- Portfolios, Portfolio Projects and Projects
- A single Project can be related to a single Portfolio Project which can be related to multiple Portfolios
- That let's one project and it's health indicators show in multiple portfolios with only having to maintain the health indicators in one place
- Not sure whether this relationship is only in Juno or wether it's also in Eureka
- We should follow-up with John on that
- We can associate a Project with a single Configuration item, but any way to have more complex relationships across SN applications
- sys_m2m_list can be used to establish a new relationship betwteen two tables
- That will then show a Relationship with the related objects
- Can also create list fields and add them to an object - and they'll show in the UI
- Like adding a list of team members
- Could also be a way to associate a project with multiple business services
- sys_m2m_list can be used to establish a new relationship betwteen two tables
- ...
- A single Project can be related to a single Portfolio Project which can be related to multiple Portfolios
- ...