After you create anAnt Cube Card and add card resources, you must release the card so that clients can pull it. This topic describes how to create a publishing task for anAnt Cube Card in the mPaaS console.
Prerequisites
If you want to use the whitelist release model, you must create a whitelist before you release the card.
For more information about how to create a whitelist, see Whitelist management.
Procedure
Log on to the mPaaS console and select the target application from the application list.
In the navigation pane on the left, choose Mobile Delivery Service > Ant Cube Card > Card Management to open the Card Management page.
On the Card Management page, click the card that you want to release in the Card List.
Click the Create a Release button to open the Create a Release page.

On the New Release page, configure the following parameters and click Submit.
Release Type: required. Grayscale release and official release. If you select grayscale release, you can configure the release model, whitelist, and advanced rules. If you select official release, you do not need to configure these parameters.
Release Model: required. You can select the release model of the whitelist or time window.
Whitelist: Releases the card to users on a whitelist. Only users on the whitelist can pull the card.
Whitelist Configuration: If you select Whitelist as the release model, select a pre-created whitelist.
NoteIf a selected whitelist contains more than 100,000 users, only the first 100,000 users are included.
Time Window: Performs a canary release to a limited number of users within a specified time frame.
If you select the Time Window model, specify the window closing time and the number of users for the canary release.
Release Description: Optional. Add a description for the current release task.
Advanced Rules: Optional. You can release the card based on specific rules. You can configure Platform, Type, Operation Type, and Resource Value, as shown in the following figure.

Type: required. City, model, network, and device system version.
Operation Type: required. Contain or not contain. Under the equipment system version type, the operation type has additional in-range and out-of-range options.
Resource Value: required. You can enter the resource value directly. You can also configure the resource mapping relationship in the release rule in advance and call this operation here.
For more information about how to add resource values for advanced rules, see Release rule management.
You have now completed releasing the card. After releasing, the task status will be "In releasing" as shown in the image below. For tasks that are "In releasing" you can view, pause, or end the task. When a version of a card is in a "In releasing" task, you cannot create another release task. You must wait for the current release task to finish, or end the current "In releasing" task before creating a new task.
