Forms
sylius_add_to_cart
Errors
This form has no errors.
Default Data
| Property | Value |
|---|---|
| Model Format | same as normalized format |
| Normalized Format | Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#106783 -cart: App\Entity\Order\Order {#13331 …} -cartItem: App\Entity\Order\OrderItem {#106771 #id: null #order: null #quantity: 1 #unitPrice: 0 #originalUnitPrice: 0 #total: 0 #immutable: false #units: Doctrine\Common\Collections\ArrayCollection {#106795 …} #unitsTotal: 0 #adjustments: Doctrine\Common\Collections\ArrayCollection {#106796 …} #adjustmentsTotal: 0 #version: 1 #variant: App\Entity\Product\ProductVariant {#8100 #id: 5886 #code: "IEEE00005548PDF" #product: App\Entity\Product\Product {#7311 #id: 11079 #code: "IEEE00005548" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7311} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#200268 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751039465 {#7274 : 2025-06-27 17:51:05.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#7322 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 39325 #name: "IEEE 20000-2:2013" #slug: "ieee-20000-2-2013-ieee00005548-242731" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n \t\t\t\t<br />\n 1.1. General.<br />\n This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n 1.2 Application<br />\n The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n ISO/IEC 20000-1.<br />\n The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1370210400 {#7318 : 2013-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1537999200 {#7316 : 2018-09-27 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "20000-2" -bookCollection: "" -pageCount: 105 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } #optionValues: Doctrine\ORM\PersistentCollection {#8316 …} #position: 0 #createdAt: DateTime @1751041252 {#7283 : 2025-06-27 18:20:52.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1755611995 {#8117 : 2025-08-19 15:59:55.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#8260 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductVariantTranslation {#93192 #locale: "en_US" #translatable: App\Entity\Product\ProductVariant {#8100} #id: 5916 #name: null -shortDescription: null -description: null -notes: null -shippingInformation: "Instant download" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #version: 9 #onHold: 0 #onHand: 0 #tracked: false #weight: 0.0 #width: null #height: null #depth: null #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8132 …} #shippingCategory: null #channelPricings: Doctrine\ORM\PersistentCollection {#8294 …} #shippingRequired: true #images: Doctrine\ORM\PersistentCollection {#8291 …} -apiLastModifiedAt: DateTime @1753740000 {#8099 : 2025-07-29 00:00:00.0 Europe/Paris (+02:00) } -publishedAt: null -isbn: "978-0-7381-8430-2" -ean: "9780738184302" -numberOfUsers: 1 -physicalProduct: false -downloadableImmediately: true -downloadable: true -drmViewerUrl: "https://online-viewer.normadoc.com/QVXDyg" -sellable: true -documents: Doctrine\ORM\PersistentCollection {#8128 …} -drmTokens: Doctrine\ORM\PersistentCollection {#8120 …} -enabledForSubscribers: true -currentAreaContext: null } #productName: null #variantName: null } } |
| View Format | same as normalized format |
Submitted Data
This form was not submitted.
Passed Options
| Option | Passed Value | Resolved Value |
|---|---|---|
| data | Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#106783 -cart: App\Entity\Order\Order {#13331 …} -cartItem: App\Entity\Order\OrderItem {#106771 #id: null #order: null #quantity: 1 #unitPrice: 0 #originalUnitPrice: 0 #total: 0 #immutable: false #units: Doctrine\Common\Collections\ArrayCollection {#106795 …} #unitsTotal: 0 #adjustments: Doctrine\Common\Collections\ArrayCollection {#106796 …} #adjustmentsTotal: 0 #version: 1 #variant: App\Entity\Product\ProductVariant {#8100 #id: 5886 #code: "IEEE00005548PDF" #product: App\Entity\Product\Product {#7311 #id: 11079 #code: "IEEE00005548" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7311} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#200268 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751039465 {#7274 : 2025-06-27 17:51:05.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#7322 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 39325 #name: "IEEE 20000-2:2013" #slug: "ieee-20000-2-2013-ieee00005548-242731" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n \t\t\t\t<br />\n 1.1. General.<br />\n This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n 1.2 Application<br />\n The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n ISO/IEC 20000-1.<br />\n The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1370210400 {#7318 : 2013-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1537999200 {#7316 : 2018-09-27 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "20000-2" -bookCollection: "" -pageCount: 105 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } #optionValues: Doctrine\ORM\PersistentCollection {#8316 …} #position: 0 #createdAt: DateTime @1751041252 {#7283 : 2025-06-27 18:20:52.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1755611995 {#8117 : 2025-08-19 15:59:55.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#8260 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductVariantTranslation {#93192 #locale: "en_US" #translatable: App\Entity\Product\ProductVariant {#8100} #id: 5916 #name: null -shortDescription: null -description: null -notes: null -shippingInformation: "Instant download" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #version: 9 #onHold: 0 #onHand: 0 #tracked: false #weight: 0.0 #width: null #height: null #depth: null #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8132 …} #shippingCategory: null #channelPricings: Doctrine\ORM\PersistentCollection {#8294 …} #shippingRequired: true #images: Doctrine\ORM\PersistentCollection {#8291 …} -apiLastModifiedAt: DateTime @1753740000 {#8099 : 2025-07-29 00:00:00.0 Europe/Paris (+02:00) } -publishedAt: null -isbn: "978-0-7381-8430-2" -ean: "9780738184302" -numberOfUsers: 1 -physicalProduct: false -downloadableImmediately: true -downloadable: true -drmViewerUrl: "https://online-viewer.normadoc.com/QVXDyg" -sellable: true -documents: Doctrine\ORM\PersistentCollection {#8128 …} -drmTokens: Doctrine\ORM\PersistentCollection {#8120 …} -enabledForSubscribers: true -currentAreaContext: null } #productName: null #variantName: null } } |
same as passed value |
| product | App\Entity\Product\Product {#7311 #id: 11079 #code: "IEEE00005548" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7311} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#200268 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751039465 {#7274 : 2025-06-27 17:51:05.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#7322 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 39325 #name: "IEEE 20000-2:2013" #slug: "ieee-20000-2-2013-ieee00005548-242731" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n \t\t\t\t<br />\n 1.1. General.<br />\n This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n 1.2 Application<br />\n The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n ISO/IEC 20000-1.<br />\n The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1370210400 {#7318 : 2013-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1537999200 {#7316 : 2018-09-27 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "20000-2" -bookCollection: "" -pageCount: 105 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } |
same as passed value |
Resolved Options
| Option | Value |
|---|---|
| action | "" |
| allow_extra_fields | false |
| allow_file_upload | false |
| attr | [] |
| attr_translation_parameters | [] |
| auto_initialize | true |
| block_name | null |
| block_prefix | null |
| by_reference | true |
| compound | true |
| constraints | [] |
| csrf_field_name | "_token" |
| csrf_message | "The CSRF token is invalid. Please try to resubmit the form." |
| csrf_protection | true |
| csrf_token_id | null |
| csrf_token_manager | Symfony\Component\Security\Csrf\CsrfTokenManager {#106803 -generator: Symfony\Component\Security\Csrf\TokenGenerator\UriSafeTokenGenerator {#106804 …} -storage: Symfony\Component\Security\Csrf\TokenStorage\SessionTokenStorage {#106805 …} -namespace: Closure() {#106807 …} } |
| data | Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#106783 -cart: App\Entity\Order\Order {#13331 …} -cartItem: App\Entity\Order\OrderItem {#106771 #id: null #order: null #quantity: 1 #unitPrice: 0 #originalUnitPrice: 0 #total: 0 #immutable: false #units: Doctrine\Common\Collections\ArrayCollection {#106795 …} #unitsTotal: 0 #adjustments: Doctrine\Common\Collections\ArrayCollection {#106796 …} #adjustmentsTotal: 0 #version: 1 #variant: App\Entity\Product\ProductVariant {#8100 #id: 5886 #code: "IEEE00005548PDF" #product: App\Entity\Product\Product {#7311 #id: 11079 #code: "IEEE00005548" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7311} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#200268 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751039465 {#7274 : 2025-06-27 17:51:05.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#7322 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 39325 #name: "IEEE 20000-2:2013" #slug: "ieee-20000-2-2013-ieee00005548-242731" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n \t\t\t\t<br />\n 1.1. General.<br />\n This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n 1.2 Application<br />\n The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n ISO/IEC 20000-1.<br />\n The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1370210400 {#7318 : 2013-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1537999200 {#7316 : 2018-09-27 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "20000-2" -bookCollection: "" -pageCount: 105 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } #optionValues: Doctrine\ORM\PersistentCollection {#8316 …} #position: 0 #createdAt: DateTime @1751041252 {#7283 : 2025-06-27 18:20:52.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1755611995 {#8117 : 2025-08-19 15:59:55.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#8260 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductVariantTranslation {#93192 #locale: "en_US" #translatable: App\Entity\Product\ProductVariant {#8100} #id: 5916 #name: null -shortDescription: null -description: null -notes: null -shippingInformation: "Instant download" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #version: 9 #onHold: 0 #onHand: 0 #tracked: false #weight: 0.0 #width: null #height: null #depth: null #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8132 …} #shippingCategory: null #channelPricings: Doctrine\ORM\PersistentCollection {#8294 …} #shippingRequired: true #images: Doctrine\ORM\PersistentCollection {#8291 …} -apiLastModifiedAt: DateTime @1753740000 {#8099 : 2025-07-29 00:00:00.0 Europe/Paris (+02:00) } -publishedAt: null -isbn: "978-0-7381-8430-2" -ean: "9780738184302" -numberOfUsers: 1 -physicalProduct: false -downloadableImmediately: true -downloadable: true -drmViewerUrl: "https://online-viewer.normadoc.com/QVXDyg" -sellable: true -documents: Doctrine\ORM\PersistentCollection {#8128 …} -drmTokens: Doctrine\ORM\PersistentCollection {#8120 …} -enabledForSubscribers: true -currentAreaContext: null } #productName: null #variantName: null } } |
| data_class | "Sylius\Bundle\OrderBundle\Controller\AddToCartCommand" |
| disabled | false |
| empty_data | Closure(FormInterface $form) {#106830 : "Symfony\Component\Form\Extension\Core\Type\FormType" : { : "Sylius\Bundle\OrderBundle\Controller\AddToCartCommand" } } |
| error_bubbling | true |
| error_mapping | [] |
| extra_fields_message | "This form should not contain extra fields." |
| form_attr | false |
| getter | null |
| help | null |
| help_attr | [] |
| help_html | false |
| help_translation_parameters | [] |
| inherit_data | false |
| invalid_message | "This value is not valid." |
| invalid_message_parameters | [] |
| is_empty_callback | null |
| label | null |
| label_attr | [] |
| label_format | null |
| label_html | false |
| label_translation_parameters | [] |
| mapped | true |
| method | "POST" |
| post_max_size_message | "The uploaded file was too large. Please try to upload a smaller file." |
| priority | 0 |
| product | App\Entity\Product\Product {#7311 #id: 11079 #code: "IEEE00005548" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7311} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#200268 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751039465 {#7274 : 2025-06-27 17:51:05.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#7322 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 39325 #name: "IEEE 20000-2:2013" #slug: "ieee-20000-2-2013-ieee00005548-242731" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n \t\t\t\t<br />\n 1.1. General.<br />\n This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n 1.2 Application<br />\n The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n ISO/IEC 20000-1.<br />\n The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1370210400 {#7318 : 2013-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1537999200 {#7316 : 2018-09-27 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "20000-2" -bookCollection: "" -pageCount: 105 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } |
| property_path | null |
| required | true |
| row_attr | [] |
| setter | null |
| translation_domain | null |
| trim | true |
| upload_max_size_message | Closure() {#106832 : "Symfony\Component\Form\Extension\Validator\Type\UploadValidatorExtension" : { : Symfony\Component\Translation\DataCollectorTranslator {#2251 …} : Closure() {#106831 …} : "validators" } } |
| validation_groups | [
"sylius"
] |
View Vars
| Variable | Value |
|---|---|
| action | "" |
| attr | [] |
| attr_translation_parameters | [] |
| block_prefixes | [ "form" "sylius_add_to_cart" "_sylius_add_to_cart" ] |
| cache_key | "_sylius_add_to_cart_sylius_add_to_cart" |
| compound | true |
| data | Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#106783 -cart: App\Entity\Order\Order {#13331 …} -cartItem: App\Entity\Order\OrderItem {#106771 #id: null #order: null #quantity: 1 #unitPrice: 0 #originalUnitPrice: 0 #total: 0 #immutable: false #units: Doctrine\Common\Collections\ArrayCollection {#106795 …} #unitsTotal: 0 #adjustments: Doctrine\Common\Collections\ArrayCollection {#106796 …} #adjustmentsTotal: 0 #version: 1 #variant: App\Entity\Product\ProductVariant {#8100 #id: 5886 #code: "IEEE00005548PDF" #product: App\Entity\Product\Product {#7311 #id: 11079 #code: "IEEE00005548" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7311} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#200268 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751039465 {#7274 : 2025-06-27 17:51:05.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#7322 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 39325 #name: "IEEE 20000-2:2013" #slug: "ieee-20000-2-2013-ieee00005548-242731" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n \t\t\t\t<br />\n 1.1. General.<br />\n This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n 1.2 Application<br />\n The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n ISO/IEC 20000-1.<br />\n The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1370210400 {#7318 : 2013-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1537999200 {#7316 : 2018-09-27 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "20000-2" -bookCollection: "" -pageCount: 105 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } #optionValues: Doctrine\ORM\PersistentCollection {#8316 …} #position: 0 #createdAt: DateTime @1751041252 {#7283 : 2025-06-27 18:20:52.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1755611995 {#8117 : 2025-08-19 15:59:55.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#8260 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductVariantTranslation {#93192 #locale: "en_US" #translatable: App\Entity\Product\ProductVariant {#8100} #id: 5916 #name: null -shortDescription: null -description: null -notes: null -shippingInformation: "Instant download" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #version: 9 #onHold: 0 #onHand: 0 #tracked: false #weight: 0.0 #width: null #height: null #depth: null #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8132 …} #shippingCategory: null #channelPricings: Doctrine\ORM\PersistentCollection {#8294 …} #shippingRequired: true #images: Doctrine\ORM\PersistentCollection {#8291 …} -apiLastModifiedAt: DateTime @1753740000 {#8099 : 2025-07-29 00:00:00.0 Europe/Paris (+02:00) } -publishedAt: null -isbn: "978-0-7381-8430-2" -ean: "9780738184302" -numberOfUsers: 1 -physicalProduct: false -downloadableImmediately: true -downloadable: true -drmViewerUrl: "https://online-viewer.normadoc.com/QVXDyg" -sellable: true -documents: Doctrine\ORM\PersistentCollection {#8128 …} -drmTokens: Doctrine\ORM\PersistentCollection {#8120 …} -enabledForSubscribers: true -currentAreaContext: null } #productName: null #variantName: null } } |
| disabled | false |
| errors | Symfony\Component\Form\FormErrorIterator {#106857 -form: Symfony\Component\Form\Form {#106862 …} -errors: [] } |
| form | Symfony\Component\Form\FormView {#106833 …5} |
| full_name | "sylius_add_to_cart" |
| help | null |
| help_attr | [] |
| help_html | false |
| help_translation_parameters | [] |
| id | "sylius_add_to_cart" |
| label | null |
| label_attr | [] |
| label_format | null |
| label_html | false |
| label_translation_parameters | [] |
| method | "POST" |
| multipart | false |
| name | "sylius_add_to_cart" |
| priority | 0 |
| required | true |
| row_attr | [] |
| submitted | false |
| translation_domain | null |
| unique_block_prefix | "_sylius_add_to_cart" |
| valid | true |
| value | Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#106783 -cart: App\Entity\Order\Order {#13331 …} -cartItem: App\Entity\Order\OrderItem {#106771 #id: null #order: null #quantity: 1 #unitPrice: 0 #originalUnitPrice: 0 #total: 0 #immutable: false #units: Doctrine\Common\Collections\ArrayCollection {#106795 …} #unitsTotal: 0 #adjustments: Doctrine\Common\Collections\ArrayCollection {#106796 …} #adjustmentsTotal: 0 #version: 1 #variant: App\Entity\Product\ProductVariant {#8100 #id: 5886 #code: "IEEE00005548PDF" #product: App\Entity\Product\Product {#7311 #id: 11079 #code: "IEEE00005548" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7311} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#200268 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751039465 {#7274 : 2025-06-27 17:51:05.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#7322 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 39325 #name: "IEEE 20000-2:2013" #slug: "ieee-20000-2-2013-ieee00005548-242731" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n \t\t\t\t<br />\n 1.1. General.<br />\n This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n 1.2 Application<br />\n The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n ISO/IEC 20000-1.<br />\n The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1370210400 {#7318 : 2013-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1537999200 {#7316 : 2018-09-27 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "20000-2" -bookCollection: "" -pageCount: 105 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } #optionValues: Doctrine\ORM\PersistentCollection {#8316 …} #position: 0 #createdAt: DateTime @1751041252 {#7283 : 2025-06-27 18:20:52.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1755611995 {#8117 : 2025-08-19 15:59:55.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#8260 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductVariantTranslation {#93192 #locale: "en_US" #translatable: App\Entity\Product\ProductVariant {#8100} #id: 5916 #name: null -shortDescription: null -description: null -notes: null -shippingInformation: "Instant download" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #version: 9 #onHold: 0 #onHand: 0 #tracked: false #weight: 0.0 #width: null #height: null #depth: null #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8132 …} #shippingCategory: null #channelPricings: Doctrine\ORM\PersistentCollection {#8294 …} #shippingRequired: true #images: Doctrine\ORM\PersistentCollection {#8291 …} -apiLastModifiedAt: DateTime @1753740000 {#8099 : 2025-07-29 00:00:00.0 Europe/Paris (+02:00) } -publishedAt: null -isbn: "978-0-7381-8430-2" -ean: "9780738184302" -numberOfUsers: 1 -physicalProduct: false -downloadableImmediately: true -downloadable: true -drmViewerUrl: "https://online-viewer.normadoc.com/QVXDyg" -sellable: true -documents: Doctrine\ORM\PersistentCollection {#8128 …} -drmTokens: Doctrine\ORM\PersistentCollection {#8120 …} -enabledForSubscribers: true -currentAreaContext: null } #productName: null #variantName: null } } |