SaaS custom delivery public template flow
This topic describes the operation flow for the SaaS custom delivery template.
Delivery template: SaaS custom delivery public template.
This template is used for custom delivery and consists of five nodes. After you place an order, you must complete the process in the Delivery Center.
Log on to the Alibaba Cloud Marketplace console, click Purchased Services, and find the corresponding order.
Go to the Delivery Center.
Steps 1 and 2 are automated system processes.
Step 3: Submit requirements. Click Submit Requirements, fill in the fields, and then submit.
In the Submit Requirements dialog box, fill in the following required fields:
Company Name
Contact Name
Contact Phone
Contact Email
After you fill in the fields, click Submit.
Step 4: This step is performed by the service provider. A user with the delivery administrator role performs this operation. First, create a RAM user for the delivery administrator.
To create a RAM user, log on to the service provider portal - Account Management. For more information, see RAM user settings.
After you create the RAM user, log on as the RAM user.
After you log on, go to the service provider portal and click Delivery Center - Provider Entrance.
Go to the Delivery Center and click Confirm.
Step 5: Click Upload Content. Upload the administrator account, administrator password, administrator address, and single sign-on (SSO) address if available. You can also upload other files to confirm that the delivery is complete, such as a delivery checklist or a customer acceptance form. Upload these files as attachments.
Step 6: Wait for a user action.
6.1 Log on to the Alibaba Cloud Marketplace console, go to Purchased Services, and click Delivery Center to confirm the delivery.
6.2 After you confirm the delivery, the entire delivery flow is complete.
Note: For custom delivery, the platform determines the service activation status based on the payment time. After a successful payment, the service status changes to "Activated", and the instance epoch starts from the payment time.
Therefore, the actual delivery time and the time the customer starts using the service may differ from the time recorded by the platform. In this case, the actual delivery time prevails.