Manual Provisioning - Order Process

once a service is approved, it is provisioned for the user provisioning a service has two components automatic and manual provisioning each is optional and a service can can one or the other, or both manual provisioning / order process the order process controls any manual provisioning the standard order processes that can be used are stored as tasks in //tasks/services/order/ true 330,331left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type service order flags in certain cases you may wish to pass responsibility to the orderprocess to create/update/delete a service instance you can override this behaviour by setting service order flags on the order process to " manageserviceinstance " for example you have an order process that calls an intergration/webapi in the case of a api or web error you do not want a service instance to be provisioned until you receive a success from the webapi this flag effectively stops the service instance from being created by the order services task the responsibility for creating the service instance is then passed to the order process this would also mean that groups, etc are not provisioned on the user until the provisioning step has been approved "service order flags" is a v7+ feature