Inside Activate
Services
Service Flags
10 min
this section outlines the available service flags in activate and how they influence ordering, provisioning and lifecycle behaviour orderonly the service is treated as order only and is not stored as a persistent service instance it does not appear in user or computer services this flag is suitable when lifecycle management (create, update, delete) is not required examples print toner, consumables allowduplicates by default, users can hold only one instance of a service for computer based services, they can hold one instance per computer this flag allows users to have multiple instances as required supportsresetpassword indicates the service supports password reset and can appear in the reset service password task services must implement a resetpassword function in the service script example sap accounts using independent passwords supportsupdate indicates the service supports the update service task example sap roles that vary by user function supportsupdateuser enables automatic updates to the service when user details change services must implement an updateuser function example sap storing first/last names in its own database disableexpiry prevents the service from being ordered for a defined period disables the how long does the user need this service? control example order only services where lifecycle management is not required disableeffective prevents deferred start dates for orders disables the when does the user need this service? control example internet access policy, where changes must apply immediately disabledecidelater forces selection of a computer when one is required disables the decide later option example services requiring a device to be provisioned disablequickadd (8 1 4+) prevents the service from being added through quick add other quick add rules still apply (e g , use of web forms, expiry options, computer requirements) example services with important additional details users must review before ordering autoexpire automatically expires the service instead of initiating renewal if expiry is set, the background renewal script will delete the service instance immediately example time limited services that must be re ordered each time validlicenseonly requires a valid licence to be available before the service can be provisioned prevents service instance creation until a suitable licence asset is allocated example autocad or other high cost licensed software viewonly makes the service visible but not orderable via the web portal example informational items where ordering occurs outside activate hidden hides the service from the web portal example automatically deployed items such as printer drivers grouped indicates that the service is part of a grouped collection of related sub services example financial systems with multiple requestable components category the service is displayed as a category with a specialised form and a list of sub items useful when providing additional context or multiple related choices example remote access options bundle defines the service as a bundle of multiple services allows users to order a predefined set of services quickly example a new‑starter bundle containing all required initial services