Servicecatalogus inrichten
Catalog audience · Catalog form · Catalog answer mapping · Catalog routing · Catalog approvals · Catalog tasks · Catalog publish review
Voor wie
Beheerders, medewerkers en IT-teams die ITLedger gebruiken voor dienstverlening, assets, compliance en rapportages.
Taken
Kies je taak. De volledige werkwijze, voorwaarden en aandachtspunten staan hieronder in het Engels.
Catalog audience
Catalog audience.
Who can do this: Tenant administrator, Operator
Before you start
- The service requests and service catalog features must be enabled.
- The account must have catalog-management permission; operators need explicit permission for catalog items, categories and rules.
Safeguards
- Do not tell requesters about draft, inactive, archived, or hidden catalog items.
- Keep the offering in draft until its questions, defaults, visibility, routing and approval path are consistent.
- Composed ITSM workflows can be saved as drafts but cannot currently be activated; their publisher requires an available executor. Ordinary catalog items have separate publication checks.
- Open Configuration → Workflows with a role permitted to manage catalog content.
- Create or select a draft and choose its request or change type.
- Set a clear requester-facing name, description and category.
- Review visibility for the intended users, roles, groups or departments.
- Check that intended requesters can discover the item before publishing.
Expected outcome: The user has reviewed the result of catalog audience in the application.
Catalog form
Catalog form.
Who can do this: Tenant administrator, Operator
Before you start
- The service requests and service catalog features must be enabled.
- The account must have catalog-management permission; operators need explicit permission for catalog items, categories and rules.
Safeguards
- Do not let requester-provided answers define approvers, tenant ownership, status, or privileged fulfillment metadata.
- Keep the offering in draft until its questions, defaults, visibility, routing and approval path are consistent.
- Composed ITSM workflows can be saved as drafts but cannot currently be activated; their publisher requires an available executor. Ordinary catalog items have separate publication checks.
- Open Configuration → Workflows with a role permitted to manage catalog content.
- Open a draft and define only questions needed for fulfillment, routing, approval or audit.
- Use sections, clear labels and help text. Choose text, longer text, number, date, single choice, multiple choice or checkbox answers.
- Make questions required only when necessary; define choices and validation limits.
- Preview the requester form and check every required answer and validation message.
Expected outcome: The user has reviewed the result of catalog form in the application.
Catalog answer mapping
Catalog answer mapping.
Who can do this: Tenant administrator, Operator
Before you start
- The service requests and service catalog features must be enabled.
- The account must have catalog-management permission; operators need explicit permission for catalog items, categories and rules.
Safeguards
- Do not let requester-provided answers define approvers, tenant ownership, status, or privileged fulfillment metadata.
- Never allow a requester answer to control approvers, ownership, status or privileged fulfillment settings.
- Keep the offering in draft until its questions, defaults, visibility, routing and approval path are consistent.
- Composed ITSM workflows can be saved as drafts but cannot currently be activated; their publisher requires an available executor. Ordinary catalog items have separate publication checks.
- Open Configuration → Workflows with a role permitted to manage catalog content.
- Open the draft’s answer mappings.
- Review where each question’s answer will be saved: a permitted request field or structured request information.
- Set deliberate safe defaults for category, priority, impact, urgency and assignment.
- Review mappings alongside routing, approvals and fulfillment tasks to ensure each receives the intended answers.
Expected outcome: The user has reviewed the result of catalog answer mapping in the application.
Catalog routing
Catalog routing.
Who can do this: Tenant administrator, Operator
Before you start
- The service requests and service catalog features must be enabled.
- The account must have catalog-management permission; operators need explicit permission for catalog items, categories and rules.
Safeguards
- Do not let requester-provided answers define approvers, tenant ownership, status, or privileged fulfillment metadata.
- Keep the offering in draft until its questions, defaults, visibility, routing and approval path are consistent.
- Composed ITSM workflows can be saved as drafts but cannot currently be activated; their publisher requires an available executor. Ordinary catalog items have separate publication checks.
- Open Configuration → Workflows with a role permitted to manage catalog content.
- Open the draft’s routing and fulfillment settings.
- Choose the resolver team and deliberate defaults for the request type.
- Review the main-asset policy and any resolver instructions.
- Check how mapped category and request-type answers affect routing.
Expected outcome: The user has reviewed the result of catalog routing in the application.
Catalog approvals
Catalog approvals.
Who can do this: Tenant administrator, Operator
Before you start
- The service requests and service catalog features must be enabled.
- The account must have catalog-management permission; operators need explicit permission for catalog items, categories and rules.
Safeguards
- Do not let requester-provided answers define approvers, tenant ownership, status, or privileged fulfillment metadata.
- Approval-required submissions create canonical approval tasks. Rules use a fallback when no matching target resolves, exclude self-approval, and snapshot their decision policy for running requests.
- An approval-required request cannot be submitted without a resolvable approval path. Self-approval is excluded. Running requests retain their recorded decision policy.
- Keep the offering in draft until its questions, defaults, visibility, routing and approval path are consistent.
- Composed ITSM workflows can be saved as drafts but cannot currently be activated; their publisher requires an available executor. Ordinary catalog items have separate publication checks.
- Open Configuration → Workflows with a role permitted to manage catalog content.
- Choose no approval, fixed approvers or approval rules.
- For rules, define narrow named conditions on requester answers, context or permitted defaults; review matching priority.
- Choose supported approvers and whether any or all must decide.
- Configure fallback approvers and review what happens on rejection or when no approver resolves.
- Review the resulting approval tasks before activating the item.
Expected outcome: The user has reviewed the result of catalog approvals in the application.
Catalog tasks
Catalog tasks.
Who can do this: Tenant administrator, Operator
Before you start
- The service requests and service catalog features must be enabled.
- The account must have catalog-management permission; operators need explicit permission for catalog items, categories and rules.
Safeguards
- Do not let requester-provided answers define approvers, tenant ownership, status, or privileged fulfillment metadata.
- Authoring tasks in a composed workflow does not establish that its publication or execution is supported.
- Keep the offering in draft until its questions, defaults, visibility, routing and approval path are consistent.
- Composed ITSM workflows can be saved as drafts but cannot currently be activated; their publisher requires an available executor. Ordinary catalog items have separate publication checks.
- Open Configuration → Workflows with a role permitted to manage catalog content.
- Open the draft’s fulfillment tasks.
- Describe the required work and its owner, required inputs and expected result.
- Review where form answers and approved defaults reach the resolver.
- Review task dependencies and the consequences of completion or rejection in the workflow preview.
Expected outcome: The user has reviewed the result of catalog tasks in the application.
Catalog publish review
Catalog publish review.
Who can do this: Tenant administrator, Operator
Before you start
- The service requests and service catalog features must be enabled.
- The account must have catalog-management permission; operators need explicit permission for catalog items, categories and rules.
Safeguards
- Do not tell requesters about draft, inactive, archived, or hidden catalog items.
- Do not create service_requests directly for catalog items; requester submissions must use submit_service_catalog_request.
- Do not let requester-provided answers define approvers, tenant ownership, status, or privileged fulfillment metadata.
- Approval-required submissions create canonical approval tasks. Rules use a fallback when no matching target resolves, exclude self-approval, and snapshot their decision policy for running requests.
- Do not publish with missing labels, invalid form structure, inconsistent request type or an unresolved required approval path.
- Keep the offering in draft until its questions, defaults, visibility, routing and approval path are consistent.
- Composed ITSM workflows can be saved as drafts but cannot currently be activated; their publisher requires an available executor. Ordinary catalog items have separate publication checks.
- Open Configuration → Workflows with a role permitted to manage catalog content.
- Review the requester name, description, category, form and validation.
- Check each answer destination, safe defaults, assignment, approval path and fulfillment task.
- Confirm the intended audience can see the item.
- Resolve all publication blockers. Ordinary items may be activated only when validation permits it; composed workflows remain drafts.
Expected outcome: The user has reviewed the result of catalog publish review in the application.
Aanbevolen werkwijze
- Maak eigenaarschap duidelijk.
- Gebruik statussen en prioriteiten consequent.
Gerelateerde handleidingen
Lees verder in Tickets en aanvragen
Dagelijkse support: tickets, e-mailbeoordeling, taken, uren en goedkeuringen.