CSDM personas .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2022 07:01 AM
Are the attributes\personas in the domains particularly foundations domain OOB. Or will they need to be created. E,g process owner, data steward, product owner. I've looked in the dictionary and don't see them. Can anyone point me in the right direction pls.
- 1,307 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2023 06:04 AM
Generally, CSDM personas are just conceptual. They don't actually map to platform artifacts directly. So no, there is nothing OOB to be identified here. The closest direct tie to personas are the roles that may be granted to users who perform the actions expected for those personas, and the fields that store references to the Groups and Users who are assigned as that persona. For example, a Portfolio Manager manages portfolios. This means they need to be able to define their service portfolios by creating and modifying taxonomy nodes, adding services and offerings to their portfolio, and updating all of the above. There are a variety of roles that can be assigned to give varying degrees of access to these functions, including service_owner, service_author, service_admin. Those can be assigned to individuals or groups (groups is preferred.) In addition, each Service Portfolio has a specific references to Users who can be designated as the Portfolio Owner and Portfolio Manager.
So while there are elements in the platform and in the dictionary that represent and control the functionality associated with those personas, there is nothing in the platform that defines what a Persona actually is. It is a matter of understanding these personas and the capabilities those personas require in order to function, and then ensuring that they have the roles and designations needed for that specific area in order to perform those functions.
The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.